Rescuezilla

I am currently testing the next release of Rescuezilla and if all goes well it should be released next Sunday night (May 10th) San Francisco time. I am intending the primary variant to be based on the recently released Ubuntu 26.04 LTS ("Resolute") version. Sorry for the lack of update in this specific thread. My target date of next weekend is actually no different to an update I made on April 10 2026 in a random GitHub issue: I hoped to have the next release about now but it's not done yet. That...

Long time no see indeed, Orfeous! The last time I checked this was with partclone v0.3.13 back in May 19, 2020 (github.com). In testing, partclone v0.3.13 as available on Ubuntu 20.04 Focal has immature APFS support exiting with "bitmap error" when using a real APFS filesystem. Because of that I left APFS support disabled and instead used raw 'dd' byte-for-byte copy (so a 500GB hard drive with 50GB of usage leads to 500GB of space usage) Since then there has indeed been some development in apfs support...

The 'Clone' option within the Rescuezilla frontend should list all the partitions on the disk. I can imagine your resolution of Rescuezilla might be low and it might not be obvious that "Step 4" (select partitions to clone) is a scrollable list? It may appear there's only one row but you can potentially scroll down. There are lots of videos on YouTube going through the process with Rescuezilla that may be helpful. Also separately, if your drive is really starting to dying or otherwise unreliable...

Update: I've made progress towards an ARM64 build (still incomplete) but I'm looking unlikely to hit a mid-April release of Rescuezilla v2.7 right now.

I don't know the reason you don't want to update your SBAT revocation list, but for completeness for others coming across this thread, I should mention it's possible to use the command-line from Rescuezilla itself to query the SBAT revocation list potentially (not recommended) update it without going through eg, Windows Update. Here are some technical breadcrumbs with more details of details on SBAT + mokutil more than you ever want to know in https://launchpad.net/ubuntu/+source/shim-signed/+changelog...

Just noting I can't provide guarantees on when I'll get to creating a Ubuntu release specific shim versions into the Rescuezilla releases. But I'll try and prioritize it. Also noting that Rescuezilla is just me working on it in my (increasingly limited) free-time with new features, new releases and bug-fixes not always happening as frequently as everybody would like. Also unfortunately it's been very rare to receive community-developed open-source contributions that I can immediately integrate into...

I don't know the reason you don't want to update your SBAT revocation list, but for completeness for others coming across this thread, I should mention it's possible to use the command-line from Rescuezilla itself to query the SBAT revocation list potentially (not recommended) update it without going through eg, Windows Update. Here are some technical breadcrumbs with more details of details on SBAT + mokutil more than you ever want to know in https://launchpad.net/ubuntu/+source/shim-signed/+changelog...

Great question! Like other Linux-based operating systems, Rescuezilla supports Secure Boot using theshim-signed package. Each version of Ubuntu has a different shim-signed package that supports a different certificate level, eg Ubuntu 25.10 "Plucky": 1.59+15.8-0ubuntu2 Ubuntu 24.04 "Noble": 1.58+15.8-0ubuntu1 Ubuntu 22.04 "Jammy": 1.51.4+15.8-0ubuntu1 So for official releases of Ubuntu, using the earlier release (still supported for security updates etc) should work. Unfortuantely unlike official...