This release is old. Always use the latest release.
Thank you to the 5 people who supported Rescuezilla on Patreon since the last release. Developing a sustainable funding model is crucial for the continued development of Rescuezilla. Please consider becoming a Patreon. With your support Rescuezilla will continue.
Version 1.0.5.1 (2020-03-22)
- Added support for NVMe hard drives (#27)
- Fixed Redo Backup’s notorious “restore succeeded but all partitions unknown” bug (#36)
- Fixed restoring of backups created with several unofficial Redo Backup v1.0.4 updates
- Fixed “stuck at text login prompt unless using Safe Mode” issue (#25)
- Added version field for SMB/CIFS network drives for connecting to older shares (#22)
- Added retry unmount box to fix backing up of unmountable partitions (#16)
- Prevented Rescuezilla using swap partitions that are present (#37)
- Switched drive/partition list to sort by numeric not lexical ordering (1/2/3/10, not 1/10/2/3)
- Fixed switch to multithreaded ‘pigz’ for backup compression, which was intended for v1.0.5
- Ensured French Safe Mode boots into French-language with French keymap, not into English
- Added Spanish/Español (ES-es) translation by caralu74 (¡gracias!) (#28)
- Ensured that every French/German/Spanish translated string gets displayed to end-users
- Fixed an issue where some French/German/Spanish characters were not being rendered correctly
You can find the single-page changelog for all of Rescuezilla here.
Backwards compatibility
Rescuezilla v1.0.5.1 is able to restore backups created by Redo Backup and Recovery v0.9.8, v0.9.9, v1.0.0, v1.0.1, v1.0.2, v1.0.3, v1.0.4, Rescuezilla v1.0.5.0, as well as backups created by the old, unofficial Redo Backup v1.0.4 updates by Sourceforge users OAM775, chcatzsf and louvetch. Importantly, backups created by Rescuezilla v1.0.5.1 and v1.0.5.0 cannot be restored using any prior versions of Redo Backup.
Checksums
sha256sum: 6777cb19577fd229309ff9c3256d91fd11e575597d80c25bacdacbeb5b8d64dc redobackup-livecd-1.0.5.1.iso
sha1sum: e999f79eaa6fdd32c3c7ec4b31809fbbcbbe9dc0 redobackup-livecd-1.0.5.1.iso
md5sum: 0bfcf6d4d23039967caf7700d1432d71 redobackup-livecd-1.0.5.1.iso
Limitations
Rescuezilla v1.0.5.1 only officially supports backing up and restoring entire disks. Backing up and restoring individual partitions is not recommended because there is not yet the ability to select individual partitions to restore (it's restore everything which was backed up or nothing). This will be fixed in #46
Please note: While Rescuezilla can backup and restore EFI drives without issue, if you machine's firmware only supports booting from EFI drives and does not have a legacy boot option (eg, a Mac), you will need to follow the instructions in #1 to be able to boot Rescuezilla using rEFInd installed on a second USB drive. Support for booting on EFI-machines was be added in v1.0.6
See here for a full list of Rescuezilla's limitations. Rescuezilla is still very useful for entire disk backup/restore use-cases for most typical end-users. The application is being actively developed and will eventually solve all these limitations.
Discussion
Discuss this release in the Redo Backup and Recovery Sourceforge forum's official discussion thread
Bug advisories
Rescuezilla is thoroughly tested using Windows, Linux, and Mac environments. The following are known bugs in v1.0.5.1. Please regularly consult the following table in case new bugs are discovered.
| Severity | Tracking # | Description | Fixed in release |
|---|---|---|---|
| High | #50 | Two users have reported GRUB failing to restore correctly on certain Ubuntu-derivatives such as 'Linux Mint', 'MXLinux' and 'Peppermint Linux', so on these environments a GRUB repair is needed to properly boot. It appears the cause is a larger than typical GRUB region on legacy MBR disks. See #64 for full details. This bug affects all prior versions. | v1.0.6 |
| Medium | #15 | On systems with 16GB of RAM or greater, backup/restore speed is VERY slow due to a bug in the Linux memory allocator on 32-bit builds. The bug can be avoided by adding "mem=10G" to kernel boot options by pressing 'tab' at the boot menu and modifying the line so it ends in "quiet mem=10G splash --" instead of "quiet splash --", then pressing enter. Rescuezilla v1.0.6 has a 64-bit version, so runs at full speeds on all systems without the need to modify anything. | v1.0.6 |
| Medium | #15 | Source and destination paths cannot contain special characters such as quotation marks, dollar signs, hash symbols etc (' " $ # etc). Nested directory hierarchies containing spaces work fine. This bug effects every prior version since June 2010's Redo Backup 0.9.2. Rescuezilla v1.0.6 allows special characters were applicable. | v1.0.6 |
| Medium | #84 | Attempting to backup an images to an Ubuntu 20.04 samba server (SMB/CIFS) fails with a "stuck at 0%" error, but samba servers on Ubuntu 19.04 and Ubuntu 18.04 work fine. This issue has been resolved by switching to the Python programming language since Rescuezilla v2.0. | v2.0 |
| Low | #55 | Very small hard drives smaller than typically around 40 megabytes (yes, megabytes) can not be backed up or restored. Regular sized hard drives are unaffected. It's very clear if you have triggered this bug as it remains "stuck at 0%" and doesn't progress. | v1.0.6 |
| Low | #90 | The "search network" button to automatically find network shares does not work. This issue affected Redo Backup and Recovery v1.0.4 but it had been too low a priority to worry about. The simple workaround has been to enter the SMB/CIFS details manually. After deliberation, the search network function has been removed in future versions in favor of a more polished improved SMB/CIFS user-interface. | v2.0 |
| Low | #29 | If an unexpected error situation occurs, it may not be handled at all, not even having a message dialogue box to explain why. This is notorious issue affects all publicly available releases. Every Rescuezilla release is incrementally improving how these unexpected situations are handled. In v1.0.5.1, no issues relating to poor error handling have yet been observed. If you ever see any bugs on latest Rescuezilla version, please report them. This issue has been resolved with the significant improvements completed for Rescuezilla v2.0. | v2.0 |
Rescuezilla v1.0.5.1 rectifies the issues above.
Download
This release is old. Always use the latest release.