Bug#1035317: grub-pc: /boot on LVM fails if logical volume consists of multiple physical volumes

[Vagrant Cascadian]

On 2023-04-30, Steve McIntyre wrote:
> On Sun, Apr 30, 2023 at 12:56:29PM -0700, Vagrant Cascadian wrote:
>>When I tried extending the /dev/vvm/root partition to include more
>>space from the /dev/vdc1 physical volume, grub fails to load at boot,
>>unable to find the lvm volume.
...
> Can you give us a bit more detail about the system please? With
> /dev/vdc, this suggests you're in a VM and this is the third drive
> using virtio? How big is /dev/vdc? What's the partition type?

The disk is about 2TB and the partition type is GPT.

There is also a 1TB disk as /dev/vdb GPT, unused.

The main boot disk is ~500GB /dev/vda MBR.

> Why am I asking? grub-pc is limited by the platform underneath here
> when it comes to assembling RAID or LVM volumes. If a complex disk
> setup depends on a drive that can't be seen/read by grub at boot, it's
> going to struggle. I'm wondering if this might be the underlying cause
> of your issue.
>
> If possible, on your system, could you also reboot and call up a grub
> command line (hit "c" from the grub menu)?

At the moment, this is difficult as I am now doing some long-running
builds on it... but will try when I get the chance or maybe reproduce
the situation in another VM.


> From there, I'd love to see what you get if you run "ls" here...

Will do!

Thanks for the quick response!


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20230430/f86de51d/attachment.sig>