When I boot from my NVMe device, Grub presents its rescue console. From there, Grub behaves as though it thinks my NVMe partitions are drives. This bug has been reported upstream: http://savannah.gnu.org/bugs/?41883. The upstream bug has a patch attached to it. I verified that the patch does not exist in grub-2.02~beta2.tar.xz and is not in the grub-2.02_beta2-gentoo-r3.tar.xz patch tarball. Reproducible: Always
Here's the commit in git. http://git.savannah.gnu.org/cgit/grub.git/commit/?id=9706066791b994a55fb2d3d532a86aa1fde2a457
Hi I have the very same problem on my brand new nvme-based laptop. Beyond the grub-core patch mentioned here, debian had grub[2]-install patched too as in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785149#44 patch is here: https://anonscm.debian.org/cgit/d-i/grub-installer.git/commit/?id=22a8aef I will try this this evening, hope it helps.
Hi again sorry for the noise, the debian patch is for a debian-specific script, not for grub itself... Will try with grub-9999-r1 and report here; it is very frustrating to have a brand-new gentoo system and a grub that does not want to boot it...
Same issue here, I'm using MSI GS60 070XCN, with grub-9999-r1 it works.
Same here with a Thinkpad T460s, upgrading to grub-9999-r1 fixed NVMe boot for me. It would be great if the patch could be backported to a stable grub version.
(In reply to Jens Pranaitis from comment #5) > Same here with a Thinkpad T460s, upgrading to grub-9999-r1 fixed NVMe boot > for me. It would be great if the patch could be backported to a stable grub > version. I have a stable request bug open for 2.02 beta3, which should include the fix.
