GNU GRUB - Bugs: bug #63319, Unknown device type nvme0n1 when...
You are not allowed to post comments on this tracker with your current authentication level.
bug #63319: Unknown device type nvme0n1 when probing for hints string
Submitter: | Nathan Lane <canetonvolant> | ||
Submitted: | Sat 05 Nov 2022 06:46:22 AM UTC | ||
Category: | None | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Hardware-specific |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Open | Release: | 2.02 |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Sat 05 Nov 2022 06:51:22 AM UTC, comment #1: |
Nathan Lane <canetonvolant> |
Sat 05 Nov 2022 06:46:22 AM UTC, original submission:
While attempting to install a dual-boot Windows 10 / Arch Linux system with a shared EFI partition on an NVME drive in a new PC, I encountered a barrier to creating a Windows entry in GRUB. I was able to run `grub-probe --target=fs_uuid /boot/EFI/Microsoft/Boot/bootmgfw.efi`, and received an output in the expected format for an fs_uuid. I have no reason to believe that fs_uuid is inaccurate. The trouble arose when I ran `ub-probe --target=hints_string /boot/EFI/Microsoft/Boot/bootmgfw.efi`.
|
Nathan Lane <canetonvolant> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
And I see now I've made a typo and cannot find an edit button. I would not have expected `ub-probe --target=hints_string /boot/EFI/Microsoft/Boot/bootmgfw.efi` to work at all. The command that I used was, instead,`grub-probe --target=hints_string /boot/EFI/Microsoft/Boot/bootmgfw.efi`.