Need Help?

Please take a moment to read our FAQ below, as it has the answers to the most common questions about Rescuezilla. If you don't find the answer here, please check Rescuezilla limitations and GitHub issues before posting your questions or suggestions to the Rescuezilla forum currently hosted on SourceForge.

Frequently Asked Questions

Q: Is Rescuezilla a drop-in replacement to Clonezilla?

A: No, not yet. However, with your contributions on Patreon it will be that, and much more!

Q: Does Rescuezilla support booting on EFI-only machines?

A: Rescuezilla can backup and restore EFI partitions without issue. However Rescuezilla cannot boot on machines with firmware that only supports EFI and does not support legacy-boot (eg, Macs) unless worked around by first booting rEFInd from a separate USB drive. EFI support is coming in v1.0.6 (#1)

Q: I want to surgically move a partition from one machine to another. Is Rescuezilla suitable for me?

A: No, absolutely not. As stated in the Rescuezilla limitations page, Rescuezilla only officially supports backing up and restoring entire disks. Individual partition backup and restore is very immature right now and is not recommended. This will be improved upon as part of task #46.

Q: Rescuezilla hangs during boot!

A: Some computers boot extremely slow. Give it a minute, especially if the computer continues to read from the USB drive. If you only experience this when booting from USB, it is possible that in the BIOS, your USB drive may need to be identified as USB-HDD, USB-ZIP, or some other setting that may improve performance.

Q: My backup froze at XX% and no error was given! What happened?

A: Close the backup program. Open the redobackup.logs directory on desktop and view the most recent log file to see what went wrong. Then file a bug report and upload the log file. Remember that Rescuezilla is a frontend to the Partclone project, so if you can run partclone successfully, Rescuezilla should work for you. Also remember that if the drive is filled or otherwise becomes inaccessible (e.g. loss of network connection) while a backup is being saved or restored, the process will fail.

Q: Can I restore a backup to a smaller drive?

A: No. Rescuezilla currently does not support this. Backups must be restored to a drive of equal or greater size.

However, you can always restore to a larger drive, resize the partition, and back up the smaller partition if needed. Partitions can easily be resized using the included partition editor utility (GParted). A future version will support this.

Q: I restored my Linux backup using Rescuezilla. It boots past the GRUB bootloader fully, but the Linux boot gets stuck at "Rescue Mode" login prompt. How do I fix this?

A: For modern systemd Linux environments (such as Ubuntu 18.04), the partitions listed in the /etc/fstab file must be present for the system to complete booting. This means if the hard drive environment does not match exactly, the system will enter Rescue Mode until the /etc/fstab is modified to only refer to the drives which are present in the system.

Fixing a machine in this situation requires logging in at the Rescue Mode prompt, remounting the root partition as read/write, modifying /etc/fstab to remove the line of the partition which is no longer present, then remounting the root partition as read-only before hard rebooting the machine. There are plenty of guides on the internet to help fix this particular issue. If you need further help, post on the discussion forum and you will receive detailed assistance for as long as it takes to fix your issues.

Please note, in some older Linux distributions it's not the partition's UUID that is used by /etc/fstab but the partition's device node (eg. /dev/sdc1). This means the Linux boot is expecting a hard drive connnected to an identical numbered SATA port! But dont worry, any problems can be resolved by modifying /etc/fstab. As mentioned, if you need more help please ask for it on the forum.

Q: Can I use the same Rescuezilla USB drive with many computers simultaneously?

A: Yes. Select the 'Safe Mode' menu item (which includes the 'toram' parameter) and wait for the system to boot before removing the USB drive. Because this loads all of Rescuezilla into memory, please note the minimum RAM requirements are higher.

Report a Bug

If you have encountered a bug, please review this checklist:

  • Please double-check you are using the latest version of Rescuezilla, and check whether the bug is already listed in the Bug Advisories section.
  • Is the problem the result of the Rescuezilla program, or is it a hardware incompatibility issue that should be reported to Ubuntu Linux?
  • If you provide the steps, can the error be reproduced by the Rescuezilla maintainer?
Create a GitHub issue with details of the bug (please attach the logs files from the rescuezilla.log desktop folder)


If you have questions, suggestions, or requests (rather than an actual bug report) please go to the Rescuezilla forum currently hosted on SourceForge, where you can participate in existing discussions or open a new topic.

Like Rescuezilla? Become a Patreon today!

Contribute a dollar or more on Patreon to help fund Rescuezilla's continued development!