Re: How to Boot with LVM
On Wednesday, September 9, 2015 at 2:10:04 PM UTC-5, Pascal Hambourg wrote:
> ray a écrit :
> > On Tuesday, September 8, 2015 at 8:10:08 AM UTC-5, Pascal Hambourg wrote:
> >> After booting the HDD system with rEFInd, running 'grub-install' should
> >> reinstall the bootloader properly. See also useful options in my
> >> previous message.
> > Yes, it is now booting. This is with the rEFInd stick: <This is booting the HDD instance through the rEFInd stick>
> > root@mc:/boot/efi/EFI# mount /dev/sdf1 /boot/efi
> > mount: /dev/sdf1 is already mounted or /boot/efi busy
> > /dev/sdf1 is already mounted on /boot/efi
> Which instance did you boot with rEFInd ?
I have only been able to boot the HDD instance. When I navigate to the SSD instance, nothing is there.
> /dev/sdf is one of the SSD used for RAID 0 and LVM, right ?
/dev/sdf is a HDD, no md or LVM.
> > root@mc:/boot/efi/EFI# apt-get install --reinstall grub-efi
> Note that grub-efi is a dummy package which depends on either
> grub-efi-amd64 or grub-efi-ia32 depending on the installed architecture.
> Reinstalling it does nothing.
> > root@mc:/boot/efi/EFI# grub-install /dev/sdf
> > Installing for x86_64-efi platform.
> > Installation finished. No error reported.
> The device name is not used by grub-install with an EFI target.
> You could have tried to use the option --boot-loader-id I mentioned in
> a previous post.
Which device name is not used by grub-install?
I did not find a way to use --boot-loader-id. I googled this exact phrase and did not find anything but this posting. How do I use it?
> > root@mc:/boot/efi/EFI# file /boot/efi/EFI/debian/grubx64.efi
> > /boot/efi/EFI/debian/grubx64.efi: PE32+ executable (EFI application) x86-64 (stripped to external PDB), for MS Windows
> > root@mc:/boot/efi/EFI# efibootmgr --verbose | grep debian
> > Boot0000* debian HD(1,GPT,87471e98-b814-4aa9-b2bc-ea4669c75565,0x800,0x100000)/File(\EFI\debian\grubx64.efi)
> Looks as expected. You can check with blkid which partition has
> PARTUUID=87471e98-b814-4aa9-b2bc-ea4669c75565. If you wonder about the
> formard / in the boot entry pathname, that's because the UEFI uses
> MS-style path.
blkid shows PARTUUID=87471e98-b814-4aa9-b2bc-ea4669c75565 to be /dev/sdf1.
> > A baffling point: In rEFInd the path is /boot/efi/EFI/debian/grubx64.efi
> How is it baffling ? The EFI system partition is mounted on /boot/efi
> and the path relative to the partition filesystem root is
> /EFI/debian/grubx64.efi. The EFI firmware does not care about where you
> mount the EFI system partition.
Baffling: Viewing with rEFInd, I see /boot/efi/EFI/debian/grubx64.efi
> > After booting up into the HDD instance, I get:
> Booting how ? On its own or from rEFInd ?
This is after booting on its own.
> > root@mc:/boot# ls -a
> > . config-4.0.0-2-amd64 grub System.map-4.0.0-2-amd64
> > .. efi initrd.img-4.0.0-2-amd64 vmlinuz-4.0.0-2-amd64
> > root@mc:/boot# cd grub
> > root@mc:/boot/grub# ls -a
> > . .. fonts grub.cfg grubenv locale unicode.pf2 x86_64-efi
> So far so good.
> > root@mc:~# cd /boot
> > root@mc:/boot# cd efi
> > root@mc:/boot/efi# ls -a
> > . ..
> > There is nothing past /boot/efi
> What's mounted on /boot/efi ?
I am not sure what it means 'what's mounted on ...'.
#mount | grep boot returns empty
#mount | grep efi returns efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
root@md:/home/rayj# df -h /boot/
Filesystem Size Used Avail Use% Mounted on
/dev/sdf2 1.4T 4.2G 1.3T 1% /
# mount | column -t returns empty
# df /boot
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdf2 1408531700 4380392 1332578984 1% /
OK, a little more reading tells me /dev/sdf2 is mounted on /boot