I hope some one is able to help. I have successfully used ReDo Backup over the years, but, the CD I have, won't boot on a fairly new laptop. I have put ReDo Rescue onto a bootable flash disk. Thank you for supplying the information to make that an easy process.
I appear to have made backups using the flashdisk of both my desktop and laptop, using indepenent external drives.
However, when I went to put the laptop image onto a brand new internal hard disk I had the error message as follows 'Operation failed and must be cancelled. The error given was: read image_hdr block_size error'
I made a new image, and verified it, this gave the same error message. I checked the desktop image, and again, the same message.
I have attached photographs of the sda1.log and redo.log from verifying the desktop image. Sorry, I was not able to see how to save the files to an exteranl drive so that I could access them from Windows. I have just realised that I should be able to access this web page using the bootable flash disk, so will try that in future.
If any one is able to help, I would greatly appreciate it. If further information is required, please let me know.
Also can you please verify the version you are running? We assume it is the latest release (2.0.5), but this information is not visible from the images.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for taking the time to submit the details about what you encountered. Can you please try the operation once more, and this time do not name the destination folder with a space (e.g. "REDO_Backups" instead of "REDO Backups") and see if this allows you to successfully complete the operation?
If so, that means the current version is not properly escaping spaces for certain mount commands, and we will need to fix that ASAP. It would be similar to this issue: https://github.com/redorescue/redorescue/issues/13
Thank you for your input!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Having a space, or not, in the folder name appears to make no difference.
One of the disks I am trying to image conatins four partitions, one is only 16M, Type Microsoft reserved, but, no filesystem listed. This appears to be causing the problem, as the other three partions appear to verify without a problem. Note that this 16M partition is not visible in Windows - Computer Management - Disk Management.
It is getting late now, so I will confirm this, and provide better details on the weekend.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I DO get the error when there is space in the folder name. There is also a partion on the drive that is causing the same error message.
There appear to two problems with the current version of the software. I hope the information below helps.
I have both a laptop and desktop computer. Using what I have learned from trying various things with the desktop disk, I have successfully created, verified and restored, an image on my laptop computer. The laptop computer also had a partition similar to C below. I simply unticked this when creating an image of the drive.
I have created an image of C below, and attached this. No idea if it is of any use to you.
If I have not adequately explained something, feel free to ask questions. I will try to provide any information that you may find useful.
Thank you so much for the detailed information and the files you attached. These will be very helpful in determining the problem.
The latest release, 2.0.6, should correct the pathname problem you originally described. However, if there is a problem with the way the "Microsoft reserved" partitions are being handled, then this is a separate issue we'll need to figure out (and this appears to be the case based on your excellent testing).
In the post above, for partition C, you wrote "blue i". Are you referring to the tooltip icon? If so, when you hover over that icon, what is the message that is displayed? We suspect that it is letting you know that the filesystem was not identified, and that the partition will be cloned byte-for-byte (which is fine, but we want to confirm).
Thanks again, and we will be doing our best to determine from this information what may be causing this issue.
Edit: And to clarify, no errors are reported when the reserved partition is backed up, correct? The problem only happens when verifying or restoring?
Edit 2: The problem you describe seems to be the same as https://github.com/redorescue/redorescue/issues/40, so we will be continuing our discussion there if you would like to join on the issue tracker. Thank you!
Last edit: Redo Rescue 2020-10-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No error message when creating the image, only when attempting to verify or restore.
However, from our tests, it appears that the "Microsoft reserved" partition can be restored successfully, just not verified. Is this your experience as well, or were you definitely unable to restore the partition?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I only tried to restore the "Microsoft reserved" partition once, and did get the error. But, this was possibly due to having a space in the folder name.
Sorry I don't have better information.
Philip
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Philip, thank you for your valuable input and testing, and the detailed logs and files you provided. Your efforts will make Redo better for hundreds of thousands of other users, and they appreciate it too. Working together, we can achieve great things!
Based on the results of your tests along with ours, we believe these partitions are being handled properly when backed up and restored, but since verification cannot be completed with the partclone utilities, we have elected to disable the option to verify partitions which contain raw data rather than a valid filesystem. For now, this is the best solution to prevent users from thinking (incorrectly) that their backups are invalid, and worrying that their data is not safe.
(In the future we may try to make it possible to check the integrity of the archive created by pigz, but that utility provides very little insight and no command line output when using the --test flag, so it remains to be seen if that is feasible.)
Again, thank you so much for your help, and this change will be included in release 2.0.7, which will be out soon. Have a great week and let us know if you run into anything else.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I hope some one is able to help. I have successfully used ReDo Backup over the years, but, the CD I have, won't boot on a fairly new laptop. I have put ReDo Rescue onto a bootable flash disk. Thank you for supplying the information to make that an easy process.
I appear to have made backups using the flashdisk of both my desktop and laptop, using indepenent external drives.
However, when I went to put the laptop image onto a brand new internal hard disk I had the error message as follows 'Operation failed and must be cancelled. The error given was: read image_hdr block_size error'
I made a new image, and verified it, this gave the same error message. I checked the desktop image, and again, the same message.
I have attached photographs of the sda1.log and redo.log from verifying the desktop image. Sorry, I was not able to see how to save the files to an exteranl drive so that I could access them from Windows. I have just realised that I should be able to access this web page using the bootable flash disk, so will try that in future.
If any one is able to help, I would greatly appreciate it. If further information is required, please let me know.
Thank you for your time.
PS I am essentially ignorant of linux.
Philip
Also can you please verify the version you are running? We assume it is the latest release (2.0.5), but this information is not visible from the images.
Hi Philip,
Thank you for taking the time to submit the details about what you encountered. Can you please try the operation once more, and this time do not name the destination folder with a space (e.g. "REDO_Backups" instead of "REDO Backups") and see if this allows you to successfully complete the operation?
If so, that means the current version is not properly escaping spaces for certain mount commands, and we will need to fix that ASAP. It would be similar to this issue: https://github.com/redorescue/redorescue/issues/13
Thank you for your input!
Hi
Thank you for the response. The iso I used is redorescue-2.0.5.iso.
It is likely to take me couple of days to check the rest. I will have to start again.
I will test with and without spaces in the folder names.
Hi
Having a space, or not, in the folder name appears to make no difference.
One of the disks I am trying to image conatins four partitions, one is only 16M, Type Microsoft reserved, but, no filesystem listed. This appears to be causing the problem, as the other three partions appear to verify without a problem. Note that this 16M partition is not visible in Windows - Computer Management - Disk Management.
It is getting late now, so I will confirm this, and provide better details on the weekend.
Hi
I have tested with and without spaces, I get the same error each time.
Any other suggetions?
Tried folder names "Test Space1" and "TestNoSpace1"
Hi
I DO get the error when there is space in the folder name. There is also a partion on the drive that is causing the same error message.
There appear to two problems with the current version of the software. I hope the information below helps.
I have both a laptop and desktop computer. Using what I have learned from trying various things with the desktop disk, I have successfully created, verified and restored, an image on my laptop computer. The laptop computer also had a partition similar to C below. I simply unticked this when creating an image of the drive.
I have created an image of C below, and attached this. No idea if it is of any use to you.
If I have not adequately explained something, feel free to ask questions. I will try to provide any information that you may find useful.
Philip
The desktop disk has four partitions
The partitions are
Win10
1: Recovery - 499 MB NTFS - Healthy (Recovery Partit)ion
2: 99 MB - Healthy - (EFI System Partion)
3: System (C:) - 446.54 GB NTFS - Healthy (Boot, Page File, Crash Dump, Basic Data Partition)
Redo Rescue
ID - Size - Type - Filesystem - Details
A: sda1 -499M - Windows recovery environment - ntfs - Recovery
B: sda2 - 99M - EFI System - vfat - BLANK
C: sda3 - 16M - Microsoft reserved - blue i - BLANK
D: sda4 - 446.6G - Microsoft basic data - ntfs - System
1: Created an image containing three of the partions (A,B,D). Saved into folder "Temp Space1".
This image gave the same error when verified.
This image was moved (using Win10) to a folder with no spaces in the name.
This time, no errors found.
2: Created an image containing three of the partions (A,B,D). Saved into folder "TempNoSpace1".
This image did not have errors when verified.
3: Created an image with all four partions. Saved into folder "TempNoSpace1".
This image gave the same error when verified.
Philip,
Thank you so much for the detailed information and the files you attached. These will be very helpful in determining the problem.
The latest release, 2.0.6, should correct the pathname problem you originally described. However, if there is a problem with the way the "Microsoft reserved" partitions are being handled, then this is a separate issue we'll need to figure out (and this appears to be the case based on your excellent testing).
In the post above, for partition C, you wrote "blue i". Are you referring to the tooltip icon? If so, when you hover over that icon, what is the message that is displayed? We suspect that it is letting you know that the filesystem was not identified, and that the partition will be cloned byte-for-byte (which is fine, but we want to confirm).
Thanks again, and we will be doing our best to determine from this information what may be causing this issue.
Edit: And to clarify, no errors are reported when the reserved partition is backed up, correct? The problem only happens when verifying or restoring?
Edit 2: The problem you describe seems to be the same as https://github.com/redorescue/redorescue/issues/40, so we will be continuing our discussion there if you would like to join on the issue tracker. Thank you!
Last edit: Redo Rescue 2020-10-11
Hi
Yes, the "blue i" is the tooltip icon, I will have to check (tomorrow) what the message actually is.
As for the reserved partition, you are correct. No error message when creating the image, only when attempting to verify or restore.
I have often used free software, and it is a pleasure to actually be able to help identify issues.
If you would like me to test at some stage, feel free to contact me. I will be having a look at the other issue.
Philip
Philip,
You wrote:
However, from our tests, it appears that the "Microsoft reserved" partition can be restored successfully, just not verified. Is this your experience as well, or were you definitely unable to restore the partition?
Hi
I only tried to restore the "Microsoft reserved" partition once, and did get the error. But, this was possibly due to having a space in the folder name.
Sorry I don't have better information.
Philip
Hi
I have just created a new image, with the "Microsoft reserved" partition (on my laptop). I then restored it to a new drive.
When I try to verify it, the "Microsoft reserved" partition gives the usual error.
However, it appears to have been restored without a problem. I am using it now.
Philip
Philip, thank you for your valuable input and testing, and the detailed logs and files you provided. Your efforts will make Redo better for hundreds of thousands of other users, and they appreciate it too. Working together, we can achieve great things!
Based on the results of your tests along with ours, we believe these partitions are being handled properly when backed up and restored, but since verification cannot be completed with the
partcloneutilities, we have elected to disable the option to verify partitions which contain raw data rather than a valid filesystem. For now, this is the best solution to prevent users from thinking (incorrectly) that their backups are invalid, and worrying that their data is not safe.(In the future we may try to make it possible to check the integrity of the archive created by
pigz, but that utility provides very little insight and no command line output when using the--testflag, so it remains to be seen if that is feasible.)Again, thank you so much for your help, and this change will be included in release 2.0.7, which will be out soon. Have a great week and let us know if you run into anything else.