Re: Grub and nvme disk issue

[Andrei Borzenkov]

25.03.2016 22:05, Benoit пишет:
> excuse me for the SPAM
> it is definitely an issue of Grub not generating a valid line.

The EFI boot menu entries are managed by efibootmgr. It is of course
possible that GRUB is using it somehow incorrectly. Could you please run
grub-install with additional --debug flag and attach full output?

> I just confirmed and create a manual value in my BIOS and now I can boot...
> 
> efibootmgr -v
> BootCurrent: 0001
> Timeout: 0 seconds
> BootOrder: 0001
> Boot0000* Parabola
> HD(1,0,00000000000000000000000000000000,0x0,0x0)/File(\EFI\Parabola\grubx64.efi)
> 
> Boot0001* para
> PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-41-61-B4-81-1C)/HD(1,GPT,b292a4e4-0314-47ba-982a-ae06289f25f2,0x800,0x100000)/File(\EFI\Parabola\grubx64.efi)
> 
> 
> para line is created manually
> 
> On 03/25/2016 07:42 PM, Benoit wrote:
>> I made a little bit of cleaning now I have
>>
>> efibootmgr -v
>> BootCurrent: 0004
>> Timeout: 0 seconds
>> BootOrder: 0000,0004,0006
>> Boot0000* Parabola
>> HD(1,0,00000000000000000000000000000000,0x0,0x0)/File(\EFI\Parabola\grubx64.efi)
>>
>> Boot0004* UEFI: SMI USB DISK 1100, Partition 1
>> PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(1,MBR,0x4294967272,0xfc,0xf800)..BO
>>
>> Boot0006* UEFI: PM951 NVMe SAMSUNG 512GB, Partition 1
>> HD(1,GPT,feb715e6-59b0-41b8-8ecc-c5b7965edf25,0x800,0x100000)/File(EFI\boot\bootx64.efi)..BO
>>
>>
>> but same issue..
>> When I see HD(1,0,00000000000000000000000000000000,0x0,0x0) it is like
>> a empty address, probably the issue is coming from here?
>> don't know if there is a way to generate another line manually?
>>
>> I read a tons of article regarding Grub and NVMe and lot are saying
>> that it is not supported, or on the last version perhaps it is but I
>> can't find a working solution unfortunately...
>>
>> On 03/25/2016 03:47 PM, Benoit wrote:
>>> Thanks Andrei for your response, my replies below
>>>
>>> On 03/25/2016 03:41 PM, Andrei Borzenkov wrote:
>>>> On Fri, Mar 25, 2016 at 2:28 PM, Benoit <address@hidden> wrote:
>>>>> Hi Grub :)
>>>>>
>>>>> I use Grub for almost 10 years and I am in a situation where I am
>>>>> unable to
>>>>> make it work on my brand new laptop :(
>>>>> The laptop has a nvme disk and I read it could be the issue...
>>>>> Grub version is : grub 1:2.02.beta3-1
>>>>> OS: Parabola (Arch Linux based)
>>>>>
>>>>> I am doing :
>>>>> nano /etc/mkinitcpio.conf
>>>>> MODULES="nvme"
>>>>>
>>>>> HOOKS="base udev autodetect modconf block keymap keyboard encrypt
>>>>> filesystems fsck"
>>>>>
>>>>> /etc/default/grub
>>>>> GRUB_CMDLINE_LINUX="cryptdevice=/dev/nvme0n1p2:nvme0n1p2_decrypted"
>>>>> GRUB_ENABLE_CRYPTODISK=y
>>>>>
>>>>> mkdir /boot/grub
>>>>> grub-mkconfig -o /boot/grub/grub.cfg
>>>>> grub-install --target=x86_64-efi --efi-directory=/boot/efi
>>>>> --bootloader-id=Parabola --recheck /dev/nvme0n1p1
>>>
>>> Forgot to mention that I don't have any error message, everything is
>>> done succesfully
>>>>> mkinitcpio -p linux-libre
>>>>>
>>>>> (I am trying to use Grub with a full encryption disk, but I am
>>>>> almost sure
>>>>> it is not the issue as doing exactly the same on another computer
>>>>> is working
>>>>> perfectly...)
>>>>>
>>>>> When I restart the computer after the Grub installation I can see
>>>>> the new
>>>>> entries in the UEFI list in my BIOS
>>>> And these entries are ... ?
>>>
>>> I can see "Parabola"
>>> which is fine as it is the one I added with this command:
>>>
>>> grub-install --target=x86_64-efi --efi-directory=/boot/efi
>>> --bootloader-id=Parabola --recheck /dev/nvme0n1p1
>>>
>>>
>>>
>>>>
>>>>> but it makes a black screen and
>>>>> immediately jumping into another entries which is a system recovery
>>>>> type of
>>>>> thing...
>>>>>
>>>> Where your /boot/grub is located? Is it on NVMe device?
>>> Yep, my /boot/grub is on NVMe device as I only have this drive on my
>>> laptop
>>>>
>>>> Show output of "efibootmgr -v" and tell which entry corresponds to
>>>> your grub installation.
>>> efibootmgr -v
>>> BootCurrent: 0005
>>> Timeout: 0 seconds
>>> BootOrder: 0003,0005
>>> Boot0000  Windows Boot Manager
>>> HD(1,GPT,b3b80ac4-ce54-4b15-9a16-e79bff51213e,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
>>>
>>> Boot0001* Parabola
>>> HD(1,0,00000000000000000000000000000000,0x0,0x0)/File(\EFI\Parabola\grubx64.efi)
>>>
>>> Boot0002* Systemd Boot Manager
>>> HD(1,GPT,9f89ce5e-fd6d-4bb7-96d0-6739a5e5e8a0,0x800,0x100000)/File(\EFI\systemd\systemd-bootx64.efi)
>>>
>>> Boot0003* Systemd Boot Manager
>>> HD(1,GPT,feb715e6-59b0-41b8-8ecc-c5b7965edf25,0x800,0x100000)/File(\EFI\systemd\systemd-bootx64.efi)
>>>
>>> Boot0005* UEFI: SMI USB DISK 1100, Partition 1
>>> PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(1,MBR,0x4294967272,0xfc,0xf800)..BO
>>>
>>>
>>> Boot0001* Parabola
>>> HD(1,0,00000000000000000000000000000000,0x0,0x0)/File(\EFI\Parabola\grubx64.efi)
>>> is the one I try to make it work
>>>>> Any idea what would be wrong ? I know systemd-boot is working and I
>>>>> have
>>>>> been able to see the list but I would like to stay with Grub as I
>>>>> like it
>>>>> and particularly the fact I can use a full encrypted disk with /boot
>>>>> included...
>>>>>
>>>>> Many thanks
>>>>>
>>>>> Belette
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Help-grub mailing list
>>>>> address@hidden
>>>>> https://lists.gnu.org/mailman/listinfo/help-grub
>>>
>>
> 
>