Dual boot install fails when saving bootloader configuration


Installing 13.2 on a desktop with an existing Win 10 system booting from EFI. Partitions on SSD hd0 are set up thus: sda1 - 500MB efi-boot, sda2 - 100GB Windows OS and then sda3 - an LVM for the Linux install and an NTFS and Linux swap partitions at the end of the drive. Setup is very similar to my laptop on which I successfully installed openSuse on an LVM volume after the Windows parts, only difference is there are some additional Windows recovery partitions on my laptop where it came pre-installed, whereas I installed Win 10 myself on the desktop and have opted against any recovery bits.

I’ve followed the laptop install exactly, setting the efi-boot partition to be mounted at /boot/efi and specifying GRUB2-EFI as the bootloader.

When it gets to the end of the install and attempts to save the bootloader it fails with ‘An error occurred during initrd creation’. The detailed log text suggests an lvm volume is missing. If I OK the error detail it then prompts me to retry boot loader config, but nothing I do seems to make a difference. Re the full log text, is there any way to post a photo here because it seems you can only insert images from a URL? It isn’t feasible to copy type the full error text here. Here’s an extract where the point of failure appears to be:

Generating grub configuration file…
Found linux image: /boot/vmlinuz-3.16.6-2-desktop
Found initrd image: /boot/initrd-3.16.6-2-desktop
/usr/sbin/grub2-probe: error: disk ‘lvmid/udj8Gt-psoh-kMvV-pUi1-nFdw-A0i5-ISBMEL/OZscG-KUOG-Wds4-lwjg-IBwq-32bv-ohi6f1’ not found

Followed by 5 similar lines of grub2-probe failures, then it finds the Windows Boot Manager on sda1, then it finds openSuse on sda3, then another grub2-probe error looking for lvmid/…/…

There is output beforehand which may be relevant however. Will happily post photo of the rest and partition setup if requested and someone can tell me how.

If I F11 at boot to manually select boot device, the opensuse partition is listed but when I select it takes me straight to the grub 2.02 command line. Initially I thought hey-ho, I may still be able to get in, but two problems. First I’m not familiar with EFI grub2 commands. I used to do something like

set root=(drive,part)
linux /boot/vmlinuz
initrd /boot/initrd

But I noticed linux has been replaced by linuxefi, no idea if I can just follow the above pattern. Second, and most problematic, even if I knew the commands it looks like the lvm volumes aren’t recognised at all. On my laptop, if I dive in to the grub command line at boot and list partitions on hd0, the lvm volumes are listed. On my desktop, there are no lvm volumes listed, only boot-efi as gpt1 followed by 4 gpt partitions with no known filesystem detected. So, looks like the lvm components aren’t being recognised, though nothing occurs in the partitioning phase of install to suggest they haven’t been created properly and when I re-run the installation all are present and correct in the partitioner.

Only other differences I can think of between desktop and laptop is that I initially installed Windows to use a legacy MBR boot, then faffed around to change it to EFI once I realised the error of my ways and it is now booting fine in UEFI mode. But don’t see why this should matter since the creation of the LVMs is internal to the install process anyway. Other thing is I’ve left a gap between sda2 and sda3 because I intend to increase the size of my Windows partition a bit, could non-contiguous partitions be messing with the bootloader?