Closed iofloodbrian closed 4 months ago
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 30 days since being marked as stale.
On my end, this was due to the configuration set by the /etc/default/grub.d/10_cloud.cfg
file.
# Use PARTUUID instead of UUID for root=
GRUB_DISABLE_LINUX_UUID=true
GRUB_DISABLE_LINUX_PARTUUID=
Problem Description: When deploying a machine with the root file system mounted directly from a device (e.g., md0 in my case), Debian 12 hangs indefinitely on the first boot at the end of deployment.
Cause: Upon investigation, this issue appears to be due to /boot/grub/grub.cfg expecting a PARTUUID which makes it incompatible with a regular UUID.
Example Configuration: In a scenario where the root is directly mounted from md0, the relevant kernel configurations in grub.cfg appear as follows:
As shown above, root=PARTUUID= is left empty, since md0 lacks partitions and thus has no PARTUUID. Instead, the configuration should refer to a regular UUID in this scenario.
Workaround: Creating a partition on the RAID device (e.g., md0-part1) resolves this issue. With a PARTUUID available for the partition, Debian 12 completes deployment without hanging.
Request: Other images, such as those of AlmaLinux, appear to support both UUID and PARTUUID. It would be helpful if the Debian 12 image could also handle both types to prevent hanging during deployment.
Testing Status: I have not tested other Debian images, so I'm unsure whether the same issue affects them.