dell inspiron 1525 (no efi) made a backup after a freash install single drive setup but after restore could not boot up i thought i saw a bug report about this so forgive me if already addressed. i thought it had something to do with the MBR cause there is no efi on this machine. anyway clonezilla was able to work through the issue after doing a reinstall of the backup that was make from recuezilla. let me know if that made any sense to anyone.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So you used Rescuezilla to backup a Windows 10 environment, then immediately tried to restore it (overwriting your existing install) and was left with a laptop that was unable to boot up?
But then you tried restoring that exact same Rescuezilla image using Clonezilla and Windows was able to start up?
If correct, I consider that a very high severity bug. I will try to reproduce that exact case locally, and if necessary I will release Rescuezilla v2.1 earlier than otherwise.
You're correct that Rescuezilla v2.0 has introduced a bug affecting MBR disks (task #131, affecting disks with a large gap before the first partition). But I wouldn't have thought that specific bug would have affected your disk (it required users to have shifted around their partitions).
Last edit: Rescuezilla 2020-11-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did format the entire disk so it would be clean. mainly because I had another version of Windows 10 running on it and it was running super slow so I went back to the original. just to put things into context that's why I did that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was unable to reproduce your issue. Rescuezilla v2.0 was able to make a backup of a Windows 10 MBR installation and (after zeroing the drive for testing purposes) the restore succeeded and the Windows 10 environment booted without issue.
While comparing the images created by Rescuezilla and Clonezilla I did discover a bug where Rescuezilla v2.0 is not creating the file about the "Microsoft Reserved partition" (or MSR). This file is used by Clonezilla when doing a "proportional restore" (in other words restoring to a different sized disk) but it's not currently used by Rescuezilla (which has limited "proportional restore" capabilities). I have captured the full details of this bug as task #144.
You're restoring to a hard drive that is exactly the same size as the image source, so the bug above shouldn't affect you.
By the way, what version of Clonezilla did you use to do the restore?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-11-27
2.0-64-bit
machine has 4 gig of memory
used clonezilla live 22.7.0-10-amd64
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I still haven't managed to reproduce your issue, but Rescuezilla v2.1 made some improvements around the backup and restore of MBR disks (gory details in the previously linked tasks).
I have also created task #146 to match some Clonezilla restore behavior that's not yet implemented by Rescuezilla. It's worth noting that previous versions of Rescuezilla (before switching to Clonezilla image format) did not do the advanced operations listed in task #146 and had no apparent issues.
If you're still interested in Rescuezilla feel free to create new backups using v2.1 and let me know how it goes.
Also if anybody reading experiences similar issues let me know.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure if you tried Rescuezilla since v2.1's release, but I have discovered that Rescuezilla v2.0-v2.1.1 has a bug where restoring a Clonezilla or Rescuezilla v2.0+ MBR image from some locations would cause the restored disk to not be able to boot due to differences in the behavior of an incorrect filename pattern match (issue #162).
I suspect it was this bug that was causing your issue, and it also explains why you had success booting after restoring your Rescuezilla backup with Clonezilla. I have created a fix and released Rescuezilla v2.1.2. Simply restore your backup with Rescuezilla v2.1.2 or newer and things should work fine.
Last edit: Rescuezilla 2021-01-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
dell inspiron 1525 (no efi) made a backup after a freash install single drive setup but after restore could not boot up i thought i saw a bug report about this so forgive me if already addressed. i thought it had something to do with the MBR cause there is no efi on this machine. anyway clonezilla was able to work through the issue after doing a reinstall of the backup that was make from recuezilla. let me know if that made any sense to anyone.
Hi Matthew,
So you used Rescuezilla to backup a Windows 10 environment, then immediately tried to restore it (overwriting your existing install) and was left with a laptop that was unable to boot up?
But then you tried restoring that exact same Rescuezilla image using Clonezilla and Windows was able to start up?
If correct, I consider that a very high severity bug. I will try to reproduce that exact case locally, and if necessary I will release Rescuezilla v2.1 earlier than otherwise.
You're correct that Rescuezilla v2.0 has introduced a bug affecting MBR disks (task #131, affecting disks with a large gap before the first partition). But I wouldn't have thought that specific bug would have affected your disk (it required users to have shifted around their partitions).
Last edit: Rescuezilla 2020-11-27
I did format the entire disk so it would be clean. mainly because I had another version of Windows 10 running on it and it was running super slow so I went back to the original. just to put things into context that's why I did that.
I don't quite fully understand, but I will try and reproduce the issue you experienced.
let me know if you have any questions or need me to be more specific on anything. happy turkey day
I was unable to reproduce your issue. Rescuezilla v2.0 was able to make a backup of a Windows 10 MBR installation and (after zeroing the drive for testing purposes) the restore succeeded and the Windows 10 environment booted without issue.
While comparing the images created by Rescuezilla and Clonezilla I did discover a bug where Rescuezilla v2.0 is not creating the file about the "Microsoft Reserved partition" (or MSR). This file is used by Clonezilla when doing a "proportional restore" (in other words restoring to a different sized disk) but it's not currently used by Rescuezilla (which has limited "proportional restore" capabilities). I have captured the full details of this bug as task #144.
You're restoring to a hard drive that is exactly the same size as the image source, so the bug above shouldn't affect you.
By the way, what version of Clonezilla did you use to do the restore?
2.0-64-bit
machine has 4 gig of memory
used clonezilla live 22.7.0-10-amd64
I still haven't managed to reproduce your issue, but Rescuezilla v2.1 made some improvements around the backup and restore of MBR disks (gory details in the previously linked tasks).
I have also created task #146 to match some Clonezilla restore behavior that's not yet implemented by Rescuezilla. It's worth noting that previous versions of Rescuezilla (before switching to Clonezilla image format) did not do the advanced operations listed in task #146 and had no apparent issues.
If you're still interested in Rescuezilla feel free to create new backups using v2.1 and let me know how it goes.
Also if anybody reading experiences similar issues let me know.
Will do and thanks
(Edit by Rescuezilla: Removed Sourceforge's automatic quoting of my entire prior reply)
Last edit: Rescuezilla 2020-12-12
Hi again Matthew,
I'm not sure if you tried Rescuezilla since v2.1's release, but I have discovered that Rescuezilla v2.0-v2.1.1 has a bug where restoring a Clonezilla or Rescuezilla v2.0+ MBR image from some locations would cause the restored disk to not be able to boot due to differences in the behavior of an incorrect filename pattern match (issue #162).
I suspect it was this bug that was causing your issue, and it also explains why you had success booting after restoring your Rescuezilla backup with Clonezilla. I have created a fix and released Rescuezilla v2.1.2. Simply restore your backup with Rescuezilla v2.1.2 or newer and things should work fine.
Last edit: Rescuezilla 2021-01-01
Thanks, I'll check it out. Happy New Year
(Edit by Rescuezilla: Removed Sourceforge's automatic quoting of my entire prior reply)
Last edit: Rescuezilla 2021-01-01