False menu items such as "(Windows Boot Manager, )" with Rescuezilla v1.0.5.1 #69
Comments
|
Thanks for reporting the issue. Did you see a screen similar to the image below?
Rescuezilla v1.0.5.1 is not merging the menu entries. For now, it should be possible to workaround the issue by selecting the menu item starting with "Drive" that corresponds to the correct hard drive capacity. Rescuezilla v1.0.6 will be released in a few weeks with this issue (and many others) fixed. |
|
@shasheene thanks to your advice, I completed the backup successfully!! |
|
I thought I had recognized the name, but I couldn't remember where from. Thanks for your generous support! As you may have seen, there are many bug fixes coming in Rescuezilla v1.0.6, but from the log file you provided it looks like these issues won't affect your Windows backup at all. Let me know if you have any issues. |
|
FYI, I also just visited Adelaide back in February. Very impressed and
really enjoyed my time there! The Pasadena Foodland there is so impressive!!
billlum
…On Tue, May 19, 2020, 6:26 PM Shasheen Ediriweera ***@***.***> wrote:
@billlum <https://github.com/billlum>
I thought I had recognized the name, but I couldn't remember where from.
Thanks for your generous support!
As you may have seen, there are many bug fixes coming in Rescuezilla
v1.0.6
<https://github.com/rescuezilla/rescuezilla/projects/2#card-38512940>,
but from the log file you provided it looks like these issues won't affect
your Windows backup at all.
Let me know if you have any issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#69 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APT3YV6HWXY6IL4B7L2ULMTRSMWUZANCNFSM4NE7L47A>
.
|
shasheene
changed the title
shasheene
changed the title
Prevents spurious items in the device selection menu by removing the leading "/dev/" string (and EFI bootloader string) from the output of `os-prober` and ensuring the device string gets correctly processed by the NVMe support functions. Also prints out the `os-prober` output to STDOUT (and thus written to log file), which helps with any future debugging. This regression occurred when NVMe support was integrated. Unit tests have not been added in this commit, but will be done as part of rescuezilla#49. Fixes rescuezilla#69
|
This issue has been fixed by Rescuezilla v1.0.6. |
A user recently reported not being able to see an "ADATA m.2 NVMe SSD source drive", claiming to have seen this issue on Rescuezilla v1.0.5.1. The user uploaded a log file when requested.
From this log file, it can be inferred that Rescuezilla v1.0.5.1 is indeed being used, as an ISO9660 filesystem labelled Rescuezilla sized at 666MB is present (side note: added 5ab9dd7 in response to this bug report, so that in future such inferring of the version from the log won't be needed).
The key part of the log appears to be right at the start (
lsblk: /dev//dev/nvme0n1p1: not a block device). This indicates the output of eitheros-proberorfsarchiver probecommand (which provides the data used in a call tolsblk --noheadings --output=pkname --nodeps /dev/$input_partition) has has been prepended with "/dev/".Further examination suggests the root cause is
os-prober, having been broken when NVMe support was added (regressions like these can be fixed with unit tests, which are planned with #49).The text was updated successfully, but these errors were encountered: