I tried disk to disk and disk to image. In both ways a error occurs:
"can't read /stdin.001" with 2 buttons OK and CANCEL.
There is no more keyboard or mouse input possible.
The only possibility is ctrl+alt+del
1. Disk 40 GB with partitions from SUSE Linux 9.1
2. Disk 80 GB blank
By disk to image an image on a windows disk is possible.
jws01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you using Clonezilla live or Clonezilla SE ?
Which version ?
What's your steps ? How can we reproduce the problem ?
Please give us more info so it's easier to do something for you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I use Clonezilla live-1.2.1-23.iso burned with nero burning rom 5.5.10.54
My latest try
/opt/drbl/sbin/ocs-sr -q2 -c -nogui -gm -z0 -i 0 -p true savedisk "name_of_img" "sdb"
stopped with
partclone fail: see /var/log/partclone.log
But I didn't found the log after the run of Clonezilla live
thank you, for the hint. But it's a little bit dangerous for me to change the data on the source hdd.
I tried to clone with another source-PC (same kind of disk, same partitions, the PC's are all clients of the same system).
The failure was the same: "can't read /stdin.001"
The clients are working properly about 4 years. Maybe they are all cloned from the same source.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I need a way to clone first and then to correct the file-system on the clone!!!
Here the output of the command
fsck.ext3 -nv /dev/sdc3
(/dev/sdc3 is the source-partition I mentioned above as /dev/sdb3).
/dev/sdc3 enthaelt ein fehlerhaftes Dateisystem, Pruefung erzwungen.
Durchgang 1: Pruefe Inodes, Blocks, und Groessen
Durchgang 2: Pruefe Verzeichnis Struktur
Durchgang 3: Pruefe Verzeichnis Verknuepfungen (links)
Durchgang 4: ueberpruefe die Referenzzaehler
Durchgang 5: ueberpruefe Gruppe Zusammenfassung
Freie Blocks Anzahl ist falsch Gruppe #2 (151, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #10 (1, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #11 (128, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #12 (1, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #26 (12, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #28 (8, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #29 (6, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #30 (7545, counted=7539).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #32 (34612, counted=31761).
Repariere? nein
Freie Blocks Anzahl ist falsch (549433, counted=546269).
Repariere? nein
/dev/sdc3: ********** WARNUNG: Noch Fehler im Dateisystem **********
224179 inodes used (14%)
244 non-contiguous inodes (0.1%)
# von Inodes mit ind/dind/tind Bl”cken: 9474/55/0
1024937 blocks used (65%)
0 bad blocks
0 large files
First I used Drive Image 2002 to clone.
Then the command "fsck.ext3 -pfv -C 0 /dev/sdb3" has solved the file system problems on the cloned disk.
To check clonezilla again I used clonezilla to save an image from the cloned disk:
/opt/drbl/sbin/ocs-sr -q -c -gm -z1 -i 0 -p true savedisk "name-of-img" "sdb"
Now, it works fine!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
jws01,
Thanks for telling us about this. I think in the future we'd better to have a mechanism to check the file system before saving it. Actually this mechanism is done in partclone IIRC, so in the future when we switch to use partclone instead of partimage (actually partimage also has an option to check file system before saving, but sometimes it will give false alarm so we turn it off), this problem won't happen again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I tried disk to disk and disk to image. In both ways a error occurs:
"can't read /stdin.001" with 2 buttons OK and CANCEL.
There is no more keyboard or mouse input possible.
The only possibility is ctrl+alt+del
1. Disk 40 GB with partitions from SUSE Linux 9.1
2. Disk 80 GB blank
By disk to image an image on a windows disk is possible.
jws01
Are you using Clonezilla live or Clonezilla SE ?
Which version ?
What's your steps ? How can we reproduce the problem ?
Please give us more info so it's easier to do something for you.
Thank you for responding!
I use Clonezilla live-1.2.1-23.iso burned with nero burning rom 5.5.10.54
My latest try
/opt/drbl/sbin/ocs-sr -q2 -c -nogui -gm -z0 -i 0 -p true savedisk "name_of_img" "sdb"
stopped with
partclone fail: see /var/log/partclone.log
But I didn't found the log after the run of Clonezilla live
sdb has 5 partitions:
1 ext2 99MB
3 ext3 5.9GB
5 ext3 5.9GB
6 ext3 5.9GB
7 ext3 19GB
I think the problem is sdb3 there is also a failure message by using drive image 2002
For now I stopped.
More in a few days.
In two days I try with 2 other PC (same hdd-partitions).
Try to use tool, e.g. fsck, to fix the filesystem of sdb3 before you save an image.
Hi,
thank you, for the hint. But it's a little bit dangerous for me to change the data on the source hdd.
I tried to clone with another source-PC (same kind of disk, same partitions, the PC's are all clients of the same system).
The failure was the same: "can't read /stdin.001"
The clients are working properly about 4 years. Maybe they are all cloned from the same source.
I need a way to clone first and then to correct the file-system on the clone!!!
Here the output of the command
fsck.ext3 -nv /dev/sdc3
(/dev/sdc3 is the source-partition I mentioned above as /dev/sdb3).
/dev/sdc3 enthaelt ein fehlerhaftes Dateisystem, Pruefung erzwungen.
Durchgang 1: Pruefe Inodes, Blocks, und Groessen
Durchgang 2: Pruefe Verzeichnis Struktur
Durchgang 3: Pruefe Verzeichnis Verknuepfungen (links)
Durchgang 4: ueberpruefe die Referenzzaehler
Durchgang 5: ueberpruefe Gruppe Zusammenfassung
Freie Blocks Anzahl ist falsch Gruppe #2 (151, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #10 (1, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #11 (128, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #12 (1, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #26 (12, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #28 (8, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #29 (6, counted=0).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #30 (7545, counted=7539).
Repariere? nein
Freie Blocks Anzahl ist falsch Gruppe #32 (34612, counted=31761).
Repariere? nein
Freie Blocks Anzahl ist falsch (549433, counted=546269).
Repariere? nein
/dev/sdc3: ********** WARNUNG: Noch Fehler im Dateisystem **********
224179 inodes used (14%)
244 non-contiguous inodes (0.1%)
# von Inodes mit ind/dind/tind Bl”cken: 9474/55/0
1024937 blocks used (65%)
0 bad blocks
0 large files
189752 regular files
14051 directories
2090 character device files
12551 block device files
7 fifos
2862 links
5695 symbolic links (5694 fast symbolic links)
24 sockets
--------
227032 files
First I used Drive Image 2002 to clone.
Then the command "fsck.ext3 -pfv -C 0 /dev/sdb3" has solved the file system problems on the cloned disk.
To check clonezilla again I used clonezilla to save an image from the cloned disk:
/opt/drbl/sbin/ocs-sr -q -c -gm -z1 -i 0 -p true savedisk "name-of-img" "sdb"
Now, it works fine!
jws01,
Thanks for telling us about this. I think in the future we'd better to have a mechanism to check the file system before saving it. Actually this mechanism is done in partclone IIRC, so in the future when we switch to use partclone instead of partimage (actually partimage also has an option to check file system before saving, but sometimes it will give false alarm so we turn it off), this problem won't happen again.