Hello all,
after upgrading my kernel (standard linux package) yesterday to
6.12.10.arch1-1, my computer would now only boot into the systemd
emergency shell.
After further inspection, I believe this was caused by the kernel
failing to mount my EFI system partition which caused systemd to no
longer be able to reach local-fs.target[0].
Furthermore the kernel does not appear to actually be 6.12.10 but 6.12.9
as indicated by /proc/version and the journal[1].
I first thought this was an error and that pacman just didn't upgrade
the package correctly, but after reinstalling it (signature matched),
manually deleting the old kernel, regenerating the initramfs and
verifying that pacman had actually downloaded the newest version, I
still got the same result.
I really have no idea of how I would fix this, since the kernel is
supposed to have FAT32 support by default so I just downgraded linux and
linux-headers back to 6.12.9.arch1-1 and everything seems to be working
again.
I Just thought I should send a mail to let someone know about it since
it might be important.
Cheers
J. Gerhards
[0] stripped snippet of the journal:
mount[572]: mount: /efi: unknown filesystem type 'vfat'.
mount[572]: dmesg(1) may have more information after failed mount
system call.
systemd[1]: efi.mount: Mount process exited, code=exited, status=32/n/a
systemd[1]: efi.mount: Failed with result 'exit-code'.
systemd[1]: Failed to mount /efi.
systemd[1]: Dependency failed for Local File Systems.
systemd[1]: local-fs.target: Job local-fs.target/start failed with
result 'dependency'.
systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
[1] Kernel boot message:
kernel: Linux version 6.12.9-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1
20240910, GNU ld (GNU Binutils) 2.43.1) #1 SMP PREEMPT_DYNAMIC Fri, 10
Jan 2025 00:39:41 +0000
