Problem with the following is that I am not sure that it is a Clonezilla 1.2.12-37 issue or mine. My best guess is that it is yours, so here goes. Something on your CD does not like 1tb hard drives, maybe!
I am encountering PartClone image failure messages almost 100% of the time when no protection (fsck) is applied. Each is reproducible, consistently. I power down my box normally and insert the Clonezilla 1.2.12-37 disk and boot up. I begin a partition backup from my 40gb Intel SSD to either of my 1tb WD hard drives at any stage of filling. The image is prepared and saved. The verification fails with (from the /var/log/partclone.log):
Partclone v0.2.45 http://partclone.org
Starting to check image (-)
Calculating bitmap... Please wait... done!
File system: EXTFS
Device size: 15.7 GB
Space in use: 6.2 GB
Free Space: 9.5 GB
Block size: 4096 Byte
Used block : 1518420
CRC error again at 0...
This error is consistent across all failures. This is 100% reproducible.
I have learned through lots of trial, errors and practice that fsck on the destination 1tb WD EXT4 hard drive 'helps'. I use fsck on my storage devces regularly during the week but this still helps. My routine is to boot Clonezilla to the command prompt and "sudo fsck -f /dev/sdb1" on the destination drive, reboot and backup. I have not started a Clonezilla backup in recent memory without a fsck cleaning. This works 90% of the time.
About 10% of the time the first cycle of fsck doesn't work so I have to cleanse the 1tb WD EXT4 hard drive a second time. I have never had a failure after a second cleaning.
100% of the time I backup a partition to a 110gb ADATA SSD and the image verification is good, each and every time.
I use one 1tb WD EXT4 hard drive at a time to save my work. With daily and hourly incremental backups a drive lasts me a little over a month. With all the activity I can see why fsck may help. I cannot use fsck in a script - too much interactivity. When a drive reaches 90% filled, I go to the other 1tb WD EXT4 hard drive. I use gparted to format the drive to reiserfs. This removes all(?) traces of EXT4. I then reformat the drive as EXT4 and move all my backup scripts over to the new drive. I save a Clonezilla OS partition backup to 3 separate drives at least twice a week.
The 110gb SSD has never had a failure. My earlier reiserfs on the 1tb WD EXT4 hard drives was also hit by this. PartImage and fsarchiver on the SystemRescueCD had no problems. The reason I primarily use your CD is the verificiation. Of my successfully saved Clonezilla backups, not one has failed to restore. Thank You.
This problem has existed with all my versions of Clonezilla. It may be a verification failure bug. I am about to invest in two 3gb hard drives and I need some input as to whether my problems are a result of large drives, ergo the bug report. Short of a low level format (do they do that anymore?) I do not know what else I can do to diagnose the issue.
Sorry for the rambling. Any input is appreciated.
Log in to post a comment.