You are not logged in.
[SOLVED ]I run a full system upgrade today and after a reboot arch failed to mount /boot

I used a live ISO to boot and mount all partitions, then arch-chroot and run a `journalctl -xb -p 3`
Dec 11 20:13:43 moria kernel: blacklist: Problem blacklisting hash (-13)
Dec 11 20:13:43 moria kernel: blacklist: Problem blacklisting hash (-13)
Dec 11 20:13:43 moria kernel: blacklist: Problem blacklisting hash (-13)
Dec 11 20:13:43 moria kernel: blacklist: Problem blacklisting hash (-13)
Dec 11 20:13:43 moria (sd-exec-[2176]: /usr/lib/systemd/system-generators/zram-generator failed with exit status 1.
Dec 11 20:13:43 moria systemd-modules-load[2211]: Failed to find module 'crypto_user'
Dec 11 20:13:43 moria systemd-modules-load[2211]: Failed to find module 'i2c-dev'
Dec 11 20:13:43 moria systemd-modules-load[2211]: Failed to find module 'nvidia-uvm'
Dec 11 20:13:43 moria systemd-modules-load[2211]: Failed to find module 'pkcs8_key_parser'
Dec 11 20:13:44 moria systemd[1]: Failed to mount /boot.
░░ Subject: A start job for unit boot.mount has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit boot.mount has finished with a failure.
░░
░░ The job identifier is 76 and the job result is failed.
Dec 11 20:14:44 moria (sd-exec-[2516]: /usr/lib/systemd/system-generators/zram-generator failed with exit status 1.
Dec 11 20:14:44 moria systemd[1]: Failed to mount /boot.
░░ Subject: A start job for unit boot.mount has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit boot.mount has finished with a failure.
░░
░░ The job identifier is 310 and the job result is failed.
Dec 11 20:15:13 moria systemd[1]: Timed out waiting for device /dev/zram0.
░░ Subject: A start job for unit dev-zram0.device has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit dev-zram0.device has finished with a failure.
░░
░░ The job identifier is 50 and the job result is timeout.
Dec 11 20:15:55 moria (sd-exec-[2567]: /usr/lib/systemd/system-generators/zram-generator failed with exit status 1.
Dec 11 20:15:55 moria systemd[1]: Failed to mount /boot.
░░ Subject: A start job for unit boot.mount has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit boot.mount has finished with a failure.
░░
░░ The job identifier is 526 and the job result is failed.The kernel parameters include `systemd.zram=0` and `zswap.enabled=0`
While in chroot I've run a `pacman -Syu linux linux-lts` but didn't help.
Anyone knows how to debug this?
Last edited by svartkanin (2023-12-12 07:44:13)
Offline
I am having the same issue on EndeavourOS. Updated to 6.6.5 and get failed to mount /efi and all the snap targets.
Digging some more, I noticed that my bootloader says 6.6.2. I tried downgrading to kernel 6.6.2 and rebooted, and was able to get my system running again.
Last edited by j0rbsh (2023-12-11 14:19:58)
Offline
journalctl -xb -p 3
that's useless and spam
journalctl -b | curl -F 'file=@-' 0x0.stDec 11 20:13:43 moria systemd-modules-load[2211]: Failed to find module 'crypto_user'
Dec 11 20:13:43 moria systemd-modules-load[2211]: Failed to find module 'i2c-dev'
Dec 11 20:13:43 moria systemd-modules-load[2211]: Failed to find module 'nvidia-uvm'
Dec 11 20:13:43 moria systemd-modules-load[2211]: Failed to find module 'pkcs8_key_parser' as well as the failure to mount a vfat partition yells that you're booting an older kernel, either because you forgot to mount the /boot partition or because you mounted one, but are actually not booting from there.
Journal will tell.
Offline
Okay I looked more closely through the journal and found
Unknown filesystem type vfatIn the live ISO I mounted the boot partition to /mnt/boot and root to /mnt and run another `pacman -Sy linux linux-lts`, rebooted and now everthing works. I don't know why as I'm certain I've run the same thing yesterday already and it didn't work afterwards...
Offline
you're booting an older kernel, either because you forgot to mount the /boot partition or because you mounted one, but are actually not booting from there
pacman -Sy linux linux-lts
Or your're habitually running partial updates, make sure to "pacman -Syu", otherwise the next "pacman -S foo" might get you into trouble.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline