Agostinho Matos

Old computers like the one that was the reason for this post should run Rescuezilla based on ubuntu 22.04 and not the latest release.

I had to return to previous version 2.5.1 of Rescuezilla in order to backup an old dual-boot computer with several partitions, the new version 2.6 failed twice with the same error that it couldn't unmount the partition that had been backing up, a problem it never occured before, and using the previous version 2.5.1 I could backup the dual-boot desktop computer without any problems, as it happened in previous backups. I suspect that Resccuezilla does not wait for the unmount operation to complete...

Just like a train without brakes, it goes on and on, I had to press the power button for 10 seconds to interrupt the cloning process, in spite of the "Cancel" buttons along the way, they just don't cancel and keep going forward. CTRL + C does not stop, CTRL + ALT + DEL does not stop, only pressing the power button for 10 seconds, it should not be this way. I am using a two years old version of Clonezilla as the computer is 13 years old and the recent versions of Clonezilla are based on linux kernels...

I checked the clonezilla forum as clonezilla is the "father" of rescuezilla, they have a similar problem, although the log files exist in ramdisk, that is while the software is running. If the user decide, it can write the log file from the ramdisk to the usb drive. However this is a user request that will be accepted as an improvement for a future version of clonezilla, so it can be written automatically to the usb drive without having the user to manually do it.

This is a problem that has been occurring for some time (many months), but as I am not a beta tester or a software tester, I just try the latest version and when it does not work I use a previous one that has worked ok before. I have no image to share as all my Clonezilla backups are disk to disk and not disk to image. For the later I use Rescuezilla and Redo Backup, when backing to disk image. I always do 3 different types of backup in case some of them don't work when restoring a disk. Pls understand...

I understand you are a busy person, but pls could you give a follow-up to my last message of a week ago, in response to your request of an image of the error displayed by Clonezilla. Thank you.

Pls find in attachment the error I got with the latest stable version of Clonezilla in more than one desktop computer. The error is the same, the computers were bought in the same time period, most are Asrock motherboards. This error DOES NOT OCCUR with backup (disk to disk drive, not image backup) version 2.6.2-15-amd64 of 10-07-2019, which I am using in the affected desktop computers, but I would rather use the latest version of Clonezilla if possible. Tks for your time analysing the situation...

I got the above notification while running the last stable version of Clonezilla Live, on a 5-year old desktop computer. First, the phrase "maybe too old kernel" is not correct as I am running the last stable version of Clonezilla, so it is not an old kernel that is running and active in the computer. It should say "maybe it is an incompatible version of kernel" as newer kernels do support newer machines, while AT THE SAME TIME discontinuing support for older computers (and they shouldn't), in order...