Keep getting failed checks on created image
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
Hi all,
I’ve been trying to create an image of a Dell PC running Ubuntu Server
18.04. It’s mostly a fresh install with several packages added. I’m booting
from a Clonezilla live USB stick, and am trying to clone the disk to
another USB stick. The image creation process runs smoothly, but when it’s
time to check the resulting image I keep getting errors. With the default
(“beginner”) settings, which use pigz for compressing the image, the error
reads “pigz: skipping: <stdin>: corrupted – invalid deflate data (invalid
block type)”.
What I have tried:
1) Checking the source disk with fsck – all appears good, searching
for bad blocks – none that I can tell;
2) Checking the destination USB stick, formatting it to both FAT32 and
NTFS;
3) Changing the compression algorithm used (gzip, lzip) – I keep
getting errors, which look different in the lzip case, but the essence is
the same – the image can be written, but not checked;
4) Doing this process with both Clonezilla 2.5.5-38 x64 and Clonezilla
alternative 20180329 x64 – results are identical.
The output from /var/log/clonezilla.log appears to indicate that the
creation of image went fine, then it finds both partition tables, the MBR,
and then informs that “The image of this partition is broken” for both sda1
and sda2.
The output from /var/log/partclone.log reports the checksum to be 0 bytes
(huh?), then calculates bitmap (done!) and finally ends in “read
ERROR:Success”.
I’ll try to attach screenshots, not sure if this is going to work.
If anyone has suggestions on what else I should try, this would be greatly
appreciated.
Kind regards,
Dmitrij
After a lot of trial and error, I found the solution. It was to switch the boot mode to Legacy both when creating the image and when restoring it. I have no idea why it didn't work with UEFI - if someone has any ideas, would be nice to hear!
This is weird. No idea why it's related to boot mechanism.
Did you do a memtest or some hardware checking? Sometimes this kind of weird issue is related to hardware.
Steven