0

I'm trying to setup a Ubuntu 19.10 server using software RAID-5. I have a small NVMe drive and six 12TB NAS drives. The six NAS drives are connected to a SATA HBA because my mobo doesn't have enough free SATA ports.

During the install I partitioned each NAS drive and add eac partition to the RAID-5 array. I then created a LVM volume group and added the MD0 device. Then I created a logical drive for the root filesystem formatted it as BTRFS. I then make the NVMe bootable so the /boot/efi partition is on the NVMe drive. The installer finishes with no errors but after I reboot it always boots to the GRUB shell. Even if I hit the F12 key and pick Ubuntu EFI entry it still ends up at the GRUB shell.

I've booted with a LiveCD, chrooted and reran the grub-installer and it still continues to boot to the GRUB shell.

I know this should work because I setup a Hyper-V VM on my laptop and using the exact same installer configuration it works flawlessly.

So I'm deducing that since I'm ending up at the GRUB shell the bootloader can't find my /boot partition on the array so I reran the Ubuntu installer again, did a fresh install but this time I put the /boot and a /boot/efi partitions on the NVMe drive and now it boots up.

What is the reason why I have to put the /boot partition on a non-array drive on my physical PC but it works in a Hyper-V VM?

2
  • Update: When I on my physical machines when I do an ls at the grub shell all I see is (hd0,gpt1) containing my /boot/efi partition but on my VM I see the MD and LVM devices which is why I can boot the kernel.
    – Echoxxzz
    Mar 25, 2020 at 22:01
  • Update2: I think the problem is that EFI isn't able to see any of the drives attached to the SATA HBA and is only seeing drives attached the onboard SATA controller.
    – Echoxxzz
    Mar 25, 2020 at 22:11

0

You must log in to answer this question.

Browse other questions tagged .