You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debian 12 is broken after first apt upgrade with installed on MDRAID.
apt upgrade causes to change /boot/grub2/grub.cfg and inject PARTUUID= which doesn't have a value causing futher boots to fail.
Removing grub-cloud-amd64 and /etc/default/grub.d/10_cloud.cfg fixes issue.
Original contents of that file exclusively disables UUID and forces PARTUUID which simply cannot be used in RAID setup.
# Use PARTUUID instead of UUID for root=
GRUB_DISABLE_LINUX_UUID=true
GRUB_DISABLE_LINUX_PARTUUID=
By the way grub-cloud-amd64 package is marked with "You don't want to use this package outside of cloud images" in debian repositories and bare-metal servers shouldn't use cloud images since it doesn't contain drivers for hardware...
The Debian image has definitely changed since my last install (around May/Jun) because other init scripts I had also stopped working, so I'm pretty sure this must be "new" (few months at most) bug.
The text was updated successfully, but these errors were encountered:
Debian 12 is broken after first
apt upgrade
with installed on MDRAID.apt upgrade
causes to change/boot/grub2/grub.cfg
and injectPARTUUID=
which doesn't have a value causing futher boots to fail.Removing
grub-cloud-amd64
and/etc/default/grub.d/10_cloud.cfg
fixes issue.Original contents of that file exclusively disables
UUID
and forcesPARTUUID
which simply cannot be used in RAID setup.# Use PARTUUID instead of UUID for root= GRUB_DISABLE_LINUX_UUID=true GRUB_DISABLE_LINUX_PARTUUID=
By the way
grub-cloud-amd64
package is marked with "You don't want to use this package outside of cloud images" in debian repositories and bare-metal servers shouldn't use cloud images since it doesn't contain drivers for hardware...The Debian image has definitely changed since my last install (around May/Jun) because other init scripts I had also stopped working, so I'm pretty sure this must be "new" (few months at most) bug.
The text was updated successfully, but these errors were encountered: