Arch Linux

h1ru

Member

Registered: 2021-09-10

Posts: 12

[SOLVED] System broke (maybe after update)

Hello, i'm kinda new to arch linux and just got my system broke, i think it happened due to a system upgrade with pacman -Syu but i'm not sure, the system was working perfectly but after i rebooted it i get an error that says:

[FAILED] Failed to mount /efi
See 'systemctl status efi.mount' for details.
[DEPEND] Dependency failed for Local File Systems. 

but logging in with a live iso and manually mounting /mnt and /mnt/efi work perfectly without errors, i've ran smartctl tests to check for issues but it says test status PASSED and the systemctl status doesn't seem to work when chrooted into /mnt. I tried using genfstab again, but the fstab generated is identical to the one i already have (minus /dev/sdb1 which i commented out just in case to see if it helps) i also ran pacman -Syu when chrooted to see if it helped but it still doesn't work.

fstab: https://pastebin.com/6BEm91Jm
journalctl -b output: https://pastebin.com/H48ysDjb
pacman.log: https://pastebin.com/57t86mqE

any help is appreciated, thanks

edit: to clarify, the last command i run on pacman.log before rebooting and noticing the break was at 14:59:12-0300 'pacman -S fcitx5-configtool', everything after that i ran while booted into the live iso and chrooted to /mnt

Last edited by h1ru (2021-09-11 01:59:34)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,302

Re: [SOLVED] System broke (maybe after update)

Your fstab is the pacman log again and the journal from the live disk rather than the installed system.

This normally happens if you aren't booting the kernel you think you are booting, given the information so far I'm assuming during the installation you had your current /efi mounted to /boot and installed the kernel there and configured the boot loader to boot the kernel from there. If you changed that to /efi as part of your fstab then the update will have installed to 5.14 kernel to /boot which is on your root partition and not referenced by your boot loader.  Maybe post

file /boot/vmlinuz-linux
file /efi/vmlinuz-linux

and your boot loader config if you use one.

h1ru

Member

Registered: 2021-09-10

Posts: 12

Re: [SOLVED] System broke (maybe after update)

oops sorry, here's the actual fstab: https://pastebin.com/6BEm91Jm (also edited the original post)

here's the vmlinuz files:
efi: https://pastebin.com/pz2G6hcF
boot: https://pastebin.com/fdhE1fgd

it appears the boot one is updated but the efi one is not, should i have copied it from /boot to /efi ?

i only use efibootmgr to manage boot, outpoot of efibootmgr is:

BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0002,0003
Boot0000* Linux Boot Manager
Boot0002* UEFI OS
Boot0003* UEFI: KingstonDataTraveler 2.00000

...given the information so far I'm assuming during the installation you had your current /efi mounted to /boot and installed the kernel there and configured the boot loader to boot the kernel from there. If you changed that to /efi as part of your fstab then the update will have installed to 5.14 kernel to /boot which is on your root partition and not referenced by your boot loader.

it appears that's exactly what happened, although i don't remember if a had /efi partition mounted to /boot during install i don't doubt it lol

thanks

Last edited by h1ru (2021-09-10 22:46:27)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,302

Re: [SOLVED] System broke (maybe after update)

Yes you should copy/move it (and the accompanying initramfs-linux.img) over, and to avoid this in the future, just directly  mount your ESP to /boot instead of /efi. The post installation hooks that generate the initial kernel images put these into /boot by default so mounting your ESP to /boot is the easiest way to guarantee that.

Last edited by V1del (2021-09-10 23:24:21)

h1ru

Member

Registered: 2021-09-10

Posts: 12

Re: [SOLVED] System broke (maybe after update)

Sorry for the late reply, but the issue is solved!

I did as you said and copied vmlinuz-linux and the initramfs-linux.img to /efi then changed my fstab to mount /dev/sda1 to /boot

thank you so much!