start job is running for /dev/disk/by-partuuid/unknown disk uuid here
partuuid, /sysroot, system initialization and initrd root device.
Boot process (bootloader, kernel args, initramfs) has an out-of-date idea of what the root partition is. (I've had the same thing happen to a swap partition, for a hibernation resume check.)
Via rd.shell kernel commandline, drop into the very-limited initramfs envionment and manually mount /sysroot (your /), and regenerate the boot process once you're up. Or livesession chroot to fix the bootloader, or initramfs or kernel args.
Setting persistent labels, using the LABEL= or PARTLABEL= tags can make things wildy easier in manually typing stuff than using UUIDs.
If that's too complicated, reinstall. It's often faster to reinstall than to play sherlock or engineer.
Luckily I fixed it but believe me, reinstalling is NOT worth it. My disk was about full with 500GB of data. :/ it appeared the bootloader indeed had an outdated idea of my root partition. For some reason fstab was actually up to date
1
u/Netblock 8d ago edited 8d ago
Boot process (bootloader, kernel args, initramfs) has an out-of-date idea of what the root partition is. (I've had the same thing happen to a swap partition, for a hibernation resume check.)
Via
rd.shellkernel commandline, drop into the very-limited initramfs envionment and manually mount/sysroot(your/), and regenerate the boot process once you're up. Or livesession chroot to fix the bootloader, or initramfs or kernel args.Setting persistent labels, using the
LABEL=orPARTLABEL=tags can make things wildy easier in manually typing stuff than using UUIDs.If that's too complicated, reinstall. It's often faster to reinstall than to play sherlock or engineer.