Post-update boot: cannot find UUID, fallback working

Hi,

On Sunday I updated by system and rebooted. It gave an error during boot: cannot find UUID, with the UUID of my / partition.

If I use the fallback boot option, it works fine.

Any thoughts on what this could be? Thank you,

Bastiaan

EDIT exact message:

:: running early hook [udev]
Starting systemd-udev version 253.7.1-arch
:: running hook [udev]
:: Triggering uevents...
:: running hook [keymap]
Loading keymap...done
Waiting 10 seconds for device /dev/disk/by-uuid/281e5766-9f68-4864-9413-7082c16126cf ...
Waiting 10 seconds for device /dev/disk/by-uuid/281e5766-9f68-4864-9413-7082c16126cf ...
ERROR: device '281e5766-9f68-4864-9413-7082c16126cf' not found. Skipping fsck.
:: mounting '281e5766-9f68-4864-9413-7082c16126cf' on real root
mount: /new_root: can't find UUID=281e5766-9f68-4864-9413-7082c16126cf.
ERROR: failed to mount 'UUID=281e5766-9f68-4864-9413-7082c16126cf' on real root
You are new being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ~]# _

can you give more info? like bootloader , from which iso you installed endeavouros ?

thanks for writing, I’ve added the full error as an EDIT to the post at the top.

Is this what you need?

Ah few more rounds of updates and this issue disappeared. I cannot say anything useful about what happened or what fixed it. Closing the topic.

because i asked for more info, there are groups installed endeavour from apollo iso group installed from casini, configuration can be shifted for some…

using dracut or mkinitcpio… casini does dracut…

other part is systemd-boot or grub…

i gues somehow the hooks did not properlty generated…

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.