HI, I tried to use Rescuezilla 2.2 to backup 3 PCs, 2 Linux and one Windows. The USB booted up fine, the app ran until I got to the point where you choose the destination drive. On all three systems an error appears and will not continue. The error says there is a problem with the drive but no error number or explanation. The Linux PCs can read and write to the destination drive from within Linux. Windows did want to fix the drive but couldn't. Finally got latest Clonezilla and all went well with the same destination drive.
Would very much like to use Rescuezilla but Clonezilla worked where Rescuezilla didn't.
Any ideas on what the issue could be?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the report. Sorry to hear the issues. There's a number of possibilities, all of which should be resolved with Rescuezilla v2.3.
Some users of Rescuezilla v2.2 have reported issues with hibernation of Windows' NTFS partitions. In my testing I haven't seen this, though if I recall correctly Rescuezilla v2.2's implementation and use of the ntfsfix command differs from Clonezilla. As per that thread, disabling hibernation is/was a (bad) workaround, and shouldn't be required because Clonezilla can backup a NTFS filesystem if Windows was cleanly shutdown and told not to hibernate temporarily (using Shift->Shutdown, or a Restart). I will improve the error message and try to make sure that the logic completely matches Clonezilla's latest release.
Also, as of Rescuezilla v2.2, the project continues to use Ubuntu's version of partclone rather than compiling the absolute latest version from source like Clonezilla does. Ensuring the package environment is even closer will certainly help match Clonezilla's industry-leading compatibility.
Rescuezilla v2.0-v2.2 needs improvement to handling of drives with bad sectors (task #237). For Rescuezilla v2.3, I will have an option to enable partclone's --force (and --rescue) to skip common filesystem-inconsistencies and ignore disk read-errors. Clonezilla doesn't enable the potentially dangerous --force by default and neither does Rescuezilla. But having the option available will allow more flexibility, especially when Clonezilla+partclone is unable to backup an otherwise valid well-formed filesystem.
I hope that helped! Sorry for any inconvenience around the failure to backup those drives! Rescuezilla v2.3 will address the three points above and that should resolve all issues. Rescuezilla v2.3 will be out on November 20 2021 (less than 3 weeks from now).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2021-11-02
Thanks for the info. I saw the other posts about drive issues but didn't think it applied to my situation. Looking forward to the next iteration of Rescuezilla. Really appreciate your efforts on this software.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh, sorry it sounds like the issue is happening for you when you SELECT the destination drive rather than the error happening during a backup.
What exactly does the error message say? Your destination disk may need a filesystem check (on Linux). The log file may also be insightful, but it's a bit difficult to obtain.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
HI, I tried to use Rescuezilla 2.2 to backup 3 PCs, 2 Linux and one Windows. The USB booted up fine, the app ran until I got to the point where you choose the destination drive. On all three systems an error appears and will not continue. The error says there is a problem with the drive but no error number or explanation. The Linux PCs can read and write to the destination drive from within Linux. Windows did want to fix the drive but couldn't. Finally got latest Clonezilla and all went well with the same destination drive.
Would very much like to use Rescuezilla but Clonezilla worked where Rescuezilla didn't.
Any ideas on what the issue could be?
Hi Anonymous,
Thanks for the report. Sorry to hear the issues. There's a number of possibilities, all of which should be resolved with Rescuezilla v2.3.
Some users of Rescuezilla v2.2 have reported issues with hibernation of Windows' NTFS partitions. In my testing I haven't seen this, though if I recall correctly Rescuezilla v2.2's implementation and use of the
ntfsfixcommand differs from Clonezilla. As per that thread, disabling hibernation is/was a (bad) workaround, and shouldn't be required because Clonezilla can backup a NTFS filesystem if Windows was cleanly shutdown and told not to hibernate temporarily (using Shift->Shutdown, or a Restart). I will improve the error message and try to make sure that the logic completely matches Clonezilla's latest release.Also, as of Rescuezilla v2.2, the project continues to use Ubuntu's version of partclone rather than compiling the absolute latest version from source like Clonezilla does. Ensuring the package environment is even closer will certainly help match Clonezilla's industry-leading compatibility.
Rescuezilla v2.0-v2.2 needs improvement to handling of drives with bad sectors (task #237). For Rescuezilla v2.3, I will have an option to enable partclone's
--force(and--rescue) to skip common filesystem-inconsistencies and ignore disk read-errors. Clonezilla doesn't enable the potentially dangerous--forceby default and neither does Rescuezilla. But having the option available will allow more flexibility, especially when Clonezilla+partclone is unable to backup an otherwise valid well-formed filesystem.I hope that helped! Sorry for any inconvenience around the failure to backup those drives! Rescuezilla v2.3 will address the three points above and that should resolve all issues. Rescuezilla v2.3 will be out on November 20 2021 (less than 3 weeks from now).
Thanks for the info. I saw the other posts about drive issues but didn't think it applied to my situation. Looking forward to the next iteration of Rescuezilla. Really appreciate your efforts on this software.
Oh, sorry it sounds like the issue is happening for you when you SELECT the destination drive rather than the error happening during a backup.
What exactly does the error message say? Your destination disk may need a filesystem check (on Linux). The log file may also be insightful, but it's a bit difficult to obtain.