Fwd: Booting from NVMe controller enters GRUB rescue

[vinayak holikatti]

Hi Jordan,

I have tried with latest grub 2.02 beta version. And the problem
booting NVMe device still persists.
but with the workaround grub install we are able to boot Fedora 20.

Please let us know further course of action.


---------- Forwarded message ----------
From: vinayak holikatti <address@hidden>
Date: Thu, Jan 23, 2014 at 6:35 PM
Subject: Re: Booting from NVMe controller enters GRUB rescue
To: Jordan Uggla <address@hidden>


Hi Jordan,

We are able to Boot to FC20, with the workaround suggested by you.
After installing FC20 on our device. We ran this command

"grub-install --modules=part_msdos --boot-directory=/mnt/sysimage/boot
/dev/nvme0n1"

after rebooting the system and booting from NVMe device. We are able
to boot to FC20. first we got the grub menu and then after selecting
the choice we were able to boot to FC20.

You were right. That it might be treating it as totally different
device. Thanks a lot for your valuable suggestions. We will also try
with grub version 2.02 beta. and let you know what happens.


On Wed, Jan 22, 2014 at 10:00 PM, Jordan Uggla <address@hidden> wrote:
> On Tue, Jan 21, 2014 at 12:14 AM, vinayak holikatti
> <address@hidden> wrote:
>> On Mon, Jan 13, 2014 at 11:51 PM, Jordan Uggla <address@hidden> wrote:
>>> On Thu, Jan 9, 2014 at 10:53 PM, vinayak holikatti
>>> <address@hidden> wrote:
>>>> Hi All,
>>>>
>>>> We have developed Legacy OptionROM for NVMe controller device. We are
>>>> able to boot to all Windows 7 and later OS. But we are facing issue in
>>>> booting Fedora 20 x86_64 OS. Fedora 20 gets installed successfully on
>>>> NVMe device. While booting from NVMe device we are observing error as
>>>> follows and enters grub rescue. We are clueless about what is
>>>> happening here. We would like to know how to over come this issue and
>>>> boot to Fedora 20 OS from our controller.
>>>>
>>>> "error : no such device: 44d1bf09-4e8a-4f46-aea6-09e364abf5cb.
>>>>  Entering rescue mode...
>>>>  grub_rescue>"
>>>
>>> Please run "ls" at the rescue prompt and post the output.
>>
>> The ls command at grub_rescue shows as below
>>
>> grub_rescue>ls
>> (hd0)
>>
>> And set command output as below
>>
>> grub_rescue>set
>> prefix = (hd0)/grub2
>> root = hd0
>
> It looks like the problem is as I expected, grub-install is treating
> /dev/nvme0n1p1 as a *drive* (not a partition), and is treating
> /dev/nvme01 as another drive, with no relation to /dev/nvme01p1. From
> there, it realizes that you're doing a cross-disk install (though
> you're actually not) and so configures things for that case (searching
> for $prefix by UUID), and it also realizes that there is no partition
> table on /dev/nvme0n1p1 (because said device *is* a partition) and so
> expects that it will not need any partition modules at boot to read
> from it.
>
> You can likely work around this problem therefore by running
> "grub-install --modules=part_msdos /dev/nvme0n1", but *please* try
> grub 2.02 beta2 anyway (without --modules) and file a bug report if it
> fails, even if this works, because A: It's an ugly hack that could
> stop working at any time and B: It would be nice to have this working
> properly by 2.02 final.
>
>>
>> I think the information of prefix and root are wrongly set. It should be
>>
>> prefix = (hd0,1)/grub2
>> root = (hd0,2)
>>
>> /boot partition corresponds to /dev/nvme0n1p1
>> / paration corresponds to /dev/nvme0n1p2
>>
>>>
>>> --
>>> Jordan Uggla (Jordan_U on irc.freenode.net)
>>
>>
>>

--
Thanks & Regards,
Vinayak Holikatti