Bug#987008: Grub fails to find LVM volume after previous LV rename
Hoyer, David
David.Hoyer at netapp.com
Fri Sep 24 15:42:14 BST 2021
On Sat, 28 Aug 2021 09:57:35 +0200 Rogier <rogier777 at gmail.com> wrote:
> Additional information for the benefit of anybody who uses LVM and
> grub, and is unsure if or when this problem will affect them:
>
> Besides the system being rendered unbootable, another symptom of this
> problem being acute is that, at that time, update-grub will most
> probably(*) print messages of the following kind, one for each LVM
> filesystem affected:
>
> grub-probe: error: disk `lvmid/******-****-****-****-****-****-
> ******/******-****-****-****-****-****-******' not found.
>
> The immediate workaround, if this problem occurs, would be to make
> another modification to the LVM configuration. Then run update-grub
> again. For verification, the following command can also be used:
>
> grub-probe -d /dev/mapper/<device corresponding to one of the LVs> -t
> fs
>
> If the problem is acute, the error message should be printed, if it is
> not acute, then there should be no error message (no warranties :-).
>
> Kind regards,
>
> Rogier.
>
>
> (*) but not if os-prober is disabled for update-grub.
>
>
>
I have tested the patch and it fixes the issue we were seeing.
More information about the Pkg-grub-devel
mailing list