I have cloned a drive from a PC. The cloned drive boots on its own with no issues. But when I went to clone another drive using this same cloned drive I am getting an error message in Rescuezilla. The error occurs on step 2 when I select the source drive.
This error message is a bug in Rescuezilla. When scanning the disk, it was expecting some information that turned out not be there. Based on your error report alone I'm not sure the root cause, but I'll investigate.
I've been very busy recently but I know I need to create a new (non-rolling release) version of Rescuezilla.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2024-03-19
Thank you for all that you do to maintain this software! If a patch is made, would I need to download a new version of the program or can I just update from the terminal within the existing version I am running?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For a Rescuezilla live USB, the approach to update download a whole new 1 gigabyte ISO image and write it onto your USB stick again.
Rescuezilla is technically also available as a tiny ~300 kilobyte package that could be installed from a terminal, but using that to update your USB stick is not yet a pathway that's supported. Because the USB stick live environment is read-only and nothing persists between reboots.
Side note: I have a block of time coming up, so I'm expecting Rescuezilla v2.5 to be released in about 3 weeks.
As mentioned based on your error report I'm not sure the root cause. The log file would help, and it's gathered by running /usr/sbin/rescuezilla > /home/ubuntu/Desktop/logfile.txt in a terminal (so not easy to get for many users). If you can get this and upload it (either here, or for privacy email to rescuezilla at gmail) I'll be able to identify what went wrong and fix it for your system.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the delay -- I just analyzed the log file you uploaded above and it doesn't actually contain enough information to fix this bug in Rescuezilla.
Sorry, I forgot to mention that just opening Rescuezilla and closing it isn't enough -- you needed to click eg, 'Restore' or 'Backup' for Rescuezilla to scan your systems hard drives. Then the log file will contain the information I need to resolve the bug.
Please upload a new log file with that information and there's a good chance I can land a fix in the upcoming version of Rescuezilla.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2024-05-03
Similar issue has been found as this is like constantly coming. out of 20 attempts to clone, i get 1 success only and not sure what made it work. I am still struggling getting clone. As soon we click on source, then gives Traceback(most recent call last):
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2024-11-30
I'm new to Rescuezilla.
I downloaded the “rescuezilla-2.5.1-32bit.bionic.iso” and installed it on the USB stick, it started without any problems.
When I try to make a backup or a clone I get a similar error message.
Computer is an old Acer Aspire One netbook, dual boot (Win10 / MX-Linux), USB stick is a SanDisk Extreme Pro (256GB).
The stick is used to start Rescuezilla and should also be the target drive for saving the backup.
The attempt with a second USB stick (as storage location) also shows the error message.
Am I doing something wrong?
Translated with DeepL.com (free version)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yep sorry, the 32-bit Bionic version of Rescuezilla v2.5.1 has a bug that was not present in 2.4.2 that broke how drives are queried. Will fix in the upcoming release
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2025-01-31
When is the new version expected to be released?
Translated with DeepL.com (free version)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2024-12-09
Thank you very much for your feedback.
No problem, wait for the new version.
Intermediate question:
Is it possible to save backups of different computers (Win, Linux MacOS) on one HD, even if they are created by different Rescuezilla versions (32/64 bit)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is it possible to save backups of different computers (Win, Linux MacOS) on one HD, even if they are created by different Rescuezilla versions (32/64 bit)?
Yes. The backup images can be restored using different versions of Rescuezilla. The 32-bit release is based on an Ubuntu release from 2018, so many not use the latest version of software like the 64-bit versions but it should all be compatible.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2024-12-10
Thank you very much for your feedback.
I will prepare two USB sticks, one 32 bit (when the new version is available) and one 64 bit.
That way I can back up my different systems.
Translated with DeepL.com (free version)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2025-04-07
The new version rescuezilla-2.6-32bit.bionic.iso works perfectly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi All,
I have cloned a drive from a PC. The cloned drive boots on its own with no issues. But when I went to clone another drive using this same cloned drive I am getting an error message in Rescuezilla. The error occurs on step 2 when I select the source drive.
Has anyone seen this before?
I'm glad your cloned drive boots.
This error message is a bug in Rescuezilla. When scanning the disk, it was expecting some information that turned out not be there. Based on your error report alone I'm not sure the root cause, but I'll investigate.
I've been very busy recently but I know I need to create a new (non-rolling release) version of Rescuezilla.
Thank you for all that you do to maintain this software! If a patch is made, would I need to download a new version of the program or can I just update from the terminal within the existing version I am running?
For a Rescuezilla live USB, the approach to update download a whole new 1 gigabyte ISO image and write it onto your USB stick again.
Rescuezilla is technically also available as a tiny ~300 kilobyte package that could be installed from a terminal, but using that to update your USB stick is not yet a pathway that's supported. Because the USB stick live environment is read-only and nothing persists between reboots.
Side note: I have a block of time coming up, so I'm expecting Rescuezilla v2.5 to be released in about 3 weeks.
As mentioned based on your error report I'm not sure the root cause. The log file would help, and it's gathered by running
/usr/sbin/rescuezilla > /home/ubuntu/Desktop/logfile.txtin a terminal (so not easy to get for many users). If you can get this and upload it (either here, or for privacy email to rescuezilla at gmail) I'll be able to identify what went wrong and fix it for your system.Here is the requested log file
Bump
Sorry for the delay -- I just analyzed the log file you uploaded above and it doesn't actually contain enough information to fix this bug in Rescuezilla.
Sorry, I forgot to mention that just opening Rescuezilla and closing it isn't enough -- you needed to click eg, 'Restore' or 'Backup' for Rescuezilla to scan your systems hard drives. Then the log file will contain the information I need to resolve the bug.
Please upload a new log file with that information and there's a good chance I can land a fix in the upcoming version of Rescuezilla.
Similar issue has been found as this is like constantly coming. out of 20 attempts to clone, i get 1 success only and not sure what made it work. I am still struggling getting clone. As soon we click on source, then gives Traceback(most recent call last):
Please see error
I'm new to Rescuezilla.
I downloaded the “rescuezilla-2.5.1-32bit.bionic.iso” and installed it on the USB stick, it started without any problems.
When I try to make a backup or a clone I get a similar error message.
Computer is an old Acer Aspire One netbook, dual boot (Win10 / MX-Linux), USB stick is a SanDisk Extreme Pro (256GB).
The stick is used to start Rescuezilla and should also be the target drive for saving the backup.
The attempt with a second USB stick (as storage location) also shows the error message.
Am I doing something wrong?
Translated with DeepL.com (free version)
Yep sorry, the 32-bit Bionic version of Rescuezilla v2.5.1 has a bug that was not present in 2.4.2 that broke how drives are queried. Will fix in the upcoming release
When is the new version expected to be released?
Translated with DeepL.com (free version)
Thank you very much for your feedback.
No problem, wait for the new version.
Intermediate question:
Is it possible to save backups of different computers (Win, Linux MacOS) on one HD, even if they are created by different Rescuezilla versions (32/64 bit)?
Yes. The backup images can be restored using different versions of Rescuezilla. The 32-bit release is based on an Ubuntu release from 2018, so many not use the latest version of software like the 64-bit versions but it should all be compatible.
Thank you very much for your feedback.
I will prepare two USB sticks, one 32 bit (when the new version is available) and one 64 bit.
That way I can back up my different systems.
Translated with DeepL.com (free version)
The new version rescuezilla-2.6-32bit.bionic.iso works perfectly.