> This occurred on my laptop so I can pretty confidently state that there
> have been no hardware changes to my system over that period of time (or
> ever).
Well it is your hardware in any case, so you would be in a position to know! (Swapping out hard drives in a laptop is certainly a possibility.)
> just did some quick searching. it does appear to have been caused by a
> kernel update for a user of rocky linux
> https://forums.rockylinux.org/t/lvm-device-identifiers-changed-after-
> kernel-updates-resulting-in-missing-vgs-pvs/10059 . same change from
> nvme-eui to nvme-nvme
Yes, so this is a change in kernel device names which we need to handle gracefully on the grub side instead of throwing errors / debconf prompts.
> This occurred on my laptop so I can pretty confidently state that there
> have been no hardware changes to my system over that period of time (or
> ever).
Well it is your hardware in any case, so you would be in a position to know! (Swapping out hard drives in a laptop is certainly a possibility.)
> just did some quick searching. it does appear to have been caused by a /forums. rockylinux. org/t/lvm- device- identifiers- changed- after- updates- resulting- in-missing- vgs-pvs/ 10059 . same change from
> kernel update for a user of rocky linux
> https:/
> kernel-
> nvme-eui to nvme-nvme
Yes, so this is a change in kernel device names which we need to handle gracefully on the grub side instead of throwing errors / debconf prompts.