Zebradots Open Source

Please don't misunderstand! We definitely agree that restoring from any backup made with an official Redo release is not an "edge-case scenario." However, let's be clear: you are referring to forks of our project, not Redo itself. With regard to the bug you mentioned: Obviously all data was not lost, and is safely stored in the backup. This is evidenced by the fact that the vast majority did not encounter the problem, as it would require certain alterations to their hardware configuration even though...

Sorry to hear this! Hopefully you had a Redo backup of the data :)

Thanks again for the detailed report, steve6375a. The code to fix this has been pushed and the new issue at https://github.com/redorescue/redorescue/issues/80 has now been closed. This will be included in the next release!

Thanks again for the detailed report, steve6375a. The line to fix this has been pushed at https://github.com/redorescue/redorescue/issues/80 and it will be included in the next release.

You are exactly correct. We missed this the first time around, but upon testing with two SATA drives, the behavior you describe is present. The only way to correct it is to close and re-open the Redo application. We've opened an issue to get this fixed in the next release. Thanks again for your input!

Hi Steve, Would you be able to open an issue on Github? We haven't seen this come up before and it seems to be a pretty big deal. To be clear, are you saying that: 1) If you had not clicked "Back" then it would have functioned normally, but 2) when you click "Back" and change drives, the change does not take effect (and you are stuck with the original selection)? Thank you for your input!

Hi Steve, Would you be able to open an issue on Github? We haven't seen this come up before and it seems to be a pretty big deal. To be clear, are you saying that: 1) If you had not clicked "Back" then it would have functioned normally, but 2) when you click "Back" and change drives, the change does not take effect (and you are stuck with the original selection)? Thank you for your input!

Give the 4.0.0 release a try, as it is now based on Debian 11 and a more recent kernel.