I use Clonezilla on almost daily basis. Always use lzop compression and never had a problem until now (there has to be the first time). Partition saving process completed in a timely and fashionable manner, nice and clean. Restoring the partition fails at 1.77% with: lzop: compressed data violation. The image was split at 2000Mb, ntfs drive was chkdsk'ed and defragged before saving. I have tested the HDD and MEM and also tried restoration on another workstation to no avail. Testing the archive with lzop -t fails with the same err msg. Looks that the compression failed... dud! is there a way to force decompression to get at least some data?
Any help greatly appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oops...
That's why we use gzip as the default one and give warning about lzop.
As for how to force it to do, I am not sure. If any one in this forum knows this, please tell us.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No such issue about gzip. Actually at least no one reported.
But for lzop, yes, we encountered and someone ever reported. The chance is very low, but still it does exist.
The warning about lzop when you choose -z* option:
Choose the compression option. If you have no idea, keep the default value, i.e. do NOT change anything. ///NOTE/// -z3 (lzop) is fastest for compressing image and the image size is good enough (slight larger than that of gzip). However, it is not recommended when saving the image in (1) a network-based directory (2) a machine with bad quality of memory (RAM). Its algorithm requires good quality network and RAM. If the network quality or RAM is not good enough, your saved image will be broken!
Sorry, man.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I use Clonezilla on almost daily basis. Always use lzop compression and never had a problem until now (there has to be the first time). Partition saving process completed in a timely and fashionable manner, nice and clean. Restoring the partition fails at 1.77% with: lzop: compressed data violation. The image was split at 2000Mb, ntfs drive was chkdsk'ed and defragged before saving. I have tested the HDD and MEM and also tried restoration on another workstation to no avail. Testing the archive with lzop -t fails with the same err msg. Looks that the compression failed... dud! is there a way to force decompression to get at least some data?
Any help greatly appreciated.
Oops...
That's why we use gzip as the default one and give warning about lzop.
As for how to force it to do, I am not sure. If any one in this forum knows this, please tell us.
Yaah... I actually didn't know about lzop warning. Did you ever have any problems with gzip? Or should I just avoid compression at all?
No such issue about gzip. Actually at least no one reported.
But for lzop, yes, we encountered and someone ever reported. The chance is very low, but still it does exist.
The warning about lzop when you choose -z* option:
Choose the compression option. If you have no idea, keep the default value, i.e. do NOT change anything. ///NOTE/// -z3 (lzop) is fastest for compressing image and the image size is good enough (slight larger than that of gzip). However, it is not recommended when saving the image in (1) a network-based directory (2) a machine with bad quality of memory (RAM). Its algorithm requires good quality network and RAM. If the network quality or RAM is not good enough, your saved image will be broken!
Sorry, man.