Re: Grub2 install with / on lvm

[jeff]

Well, trying your latest suggestion to bypass shim didn't work either.  I get 
the same error message "failure to read sector x?x?x?x from hd1" for a short 
period, then it moves on to flashing the error "no such device: 27ae300a-...." 
which maps back to the UUID of my lvm volume lv_mintroot (/ partition).

So for doing a reinstall of this, what is the current standard (best practices, 
opinion?) for partitions for /, /boot, and /boot/efi these days.  I believe 
that I recall that /boot/efi needs to be on its own partition, and it would 
seem logical to me that /boot would also be on its own partition, but don't 
recall in all the reading I have been doing lately.  I would like to keep my / 
partition on lvm as that gives me options for changing the size later without 
it being too much of a hassle.

I am going to take some time over the next day or so to write up all my notes 
on this adventure before starting the reinstall.  Thanks again.

Jeff



-----Original Message-----
From: "Andrei Borzenkov" <address@hidden>
Sent: Wednesday, February 11, 2015 8:16pm
To: address@hidden
Cc: address@hidden
Subject: Re: Grub2 install with / on lvm

В Wed, 11 Feb 2015 12:47:06 -0800 (PST)
address@hidden пишет:

> The quick work around you suggested did not work.  The result of that was 
> when booting it would display several lines of an error message "failure 
> reading sector x?x?x?x from hd1".  These several lines would alternately 
> display and disappear, seemingly as if it was stuck in a boot loop.  A 
> cnt-alt-del would get out of it, then using the SuperGrub2 CD I could get it 
> to boot again after adding the LVM option.
> 
> I am ready to give up on this and do a reinstall (taking more detailed notes 
> next time).  Unless you want me to continue exploring something that would 
> assist you.  I probably won't find the time to do the re-install for at least 
> a day or so, if you would like additional information.  Thanks again for your 
> assistance.

Well, the last chance would be to set your system to use grubx64.efi
directly, bypassing shim. I.e., right now you have

Boot0000* ubuntu        
HD(1,800,fa000,efdf8fb6-08fd-45bc-b62c-ab9bc39721ee)File(\EFI\ubuntu\shimx64.efi)

Do (below is one line!)

efibootmgr -c -d /dev/sda -p 1 -w -L "GRUB on Ubuntu" -l 
'\EFI\ubuntu\grubx64.efi'

-L is title in EFI boot menu - pick your choice. Verify with efibootmgr
-v - HD(...) part should be identical to the above. Check that it is
set as default (i.e. number in BootXXXX has to be first in BootOrder).

Note that it will effectively disable secure boot!