You are not logged in.
After a basic sudo pacman -Syu execution, my Arch boots into an emergency mode and show this:
[FAILED] Failed mount /boot
[DEPEND] Dependency failed for Local File Systems
You are in emergency node. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, or "exit" to continue bootup.
Give root password for maintenance Cor press Control-D to continue):
The output of journalctl -xb is the following https://0x0.st/X-vW.txt. The bothering lines probably are:
░░ A start job for unit boot.mount has begun execution.
░░
░░ The job identifier is 43.
Apr 14 18:14:53 lpt mount[330]: mount: /boot: unknown filesystem type 'vfat'.
Apr 14 18:14:53 lpt mount[330]: dmesg(1) may have more information after failed mount system call.
Apr 14 18:14:53 lpt systemd[1]: boot.mount: Mount process exited, code=exited, status=32/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An n/a= process belonging to unit boot.mount has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 32.
Apr 14 18:14:53 lpt systemd[1]: boot.mount: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit boot.mount has entered the 'failed' state with result 'exit-code'.
Apr 14 18:14:53 lpt 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.
I've read threads on this topic and it seems like the issue lies on incorrect mountpoint of /boot or bad kernel most of the time. I've reinstalled linux linux-firmware numerious times both with pacstrap & through arch-chroot. And here are other data concerning mountpoints I should probably show...
fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/swapfile none swap defaults 0 0
# /dev/sda1
UUID=FC82-6CCC /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/sda2
UUID=d878152c-8459-4afd-acba-4be683f33242 / ext4 rw,relatime 0 1
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT32 FC82-6CCC
└─sda2 ext4 1.0 d878152c-8459-4afd-acba-4be683f33242 54.2G 83% /
sdb
├─sdb1 ntfs Восстановить E4DC958FDC955C9C
├─sdb2 vfat FAT32 DC96-85C0
├─sdb3
└─sdb4 ntfs 3882A013829FD3AA
Currently my wlan0 does not get recognized from the emergency mode, so I use Arch live USB to handle this issue.
I would appreciate any help, because right now, after a whole day of research, I'm definetely stuck with this issue.
Best regards,
Shura
Last edited by Schura (2024-04-15 13:39:15)
Offline
this thread essentially fixed my issue
https://bbs.archlinux.org/viewtopic.php?id=285144
Last edited by Schura (2024-04-27 19:55:59)
Offline