Bug#1035317: grub-pc: /boot on LVM fails if logical volume consists of multiple physical volumes
Steve McIntyre
steve at einval.com
Sun Apr 30 23:26:49 BST 2023
Hi Vagrant!
On Sun, Apr 30, 2023 at 12:56:29PM -0700, Vagrant Cascadian wrote:
>Package: grub-pc
>Version: 2.06-12
>Severity: important
>X-Debbugs-Cc: vagrant at debian.org
>
>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.
>
>I tried re-installing grub from the debian-installer rescue image, but
>that did not help.
>
>Removing /dev/vdc1 from the volume group fixed the issue, but
>significantly limits the benefit of LVM...
>
>A workaround is, of course, using a separate boot partition, or
>maybe keeping to only a single physical volume for the logical
>volume on which /boot resides.
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?
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)?
>From there, I'd love to see what you get if you run "ls" here...
--
Steve McIntyre, Cambridge, UK. steve at einval.com
Who needs computer imagery when you've got Brian Blessed?
More information about the Pkg-grub-devel
mailing list