You are not logged in.
- Topics: Active | Unanswered
#1 2026-08-12 11:23:44
- SteamLuki
- Member
- Registered: 2025-07-30
- Posts: 3
Failed To Mount Boot After -Syu And Restart
Hello
I have a recurring issue with Boot not mounting after updating with -Syu and restarting.
This has been going on since i started linux(1 to 1.5 years ago).
I was complety new to linux and i did alot of mistakes, i do feel more comfortable now but im still not good enough.
I found my own solution to this problem but even then it doesnt always work, so im asking here for help.
///////////////////////
Important Errors:
Aug 12 11:43:17 ArchLukas systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.
Aug 12 11:43:17 ArchLukas systemd[1]: Mounting /boot...
Aug 12 11:43:17 ArchLukas mount[746]: mount: /boot: unknown filesystem type 'vfat'.
Aug 12 11:43:17 ArchLukas systemd[1]: boot.mount: Mount process exited, code=exited, status=32/n/a
Aug 12 11:43:17 ArchLukas systemd[1]: boot.mount: Failed with result 'exit-code'.
Aug 12 11:43:17 ArchLukas systemd[1]: Failed to mount /boot.
///////////////////////
-------------------------
///////////////////////
My Solution:
Boot into live usb
Connect to wifi, iwctl
Mounting:
mount /dev/nvme0n1p3 /mnt
mount /dev/nvme0n1p1 /mnt/boot/efi
mount /dev/nvme0n1p4 /mnt/home
arch-chroot /mnt
sudo pacman -S linux linux-headers
exit
umount -R /mnt
reboot
!Works!
///////////////////////
-------------------------
I hope this is enough information and im not exposing something sensitive from my system 
Since im updating only biweekly, this is nothing critical and my muscle memory is already imprinted on fixing this issue each time.
-------------------------
p1 == boot
p2 == swap
p3 == root
p4 == home
○ → sudo fdisk -x
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: Samsung SSD 970 PRO 1TB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 5C13BA11-51AD-46AF-80A2-EF526DFC3101
First usable LBA: 34
Last usable LBA: 2000409230
Alternative LBA: 2000409263
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33
Device Start End Sectors Type-UUID UUID Name Attrs
/dev/nvme0n1p1 2048 4196351 4194304 C12A7328-F81F-11D2-BA4B-00A0C93EC93B A6B7E178-9083-4A23-B64C-8CADCCC07F72 EFI system partition
/dev/nvme0n1p2 4196352 104859647 100663296 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F FC00330D-9EEE-4107-BE59-574A8E4129AE Linux swap
/dev/nvme0n1p3 104859648 209717247 104857600 0FC63DAF-8483-4772-8E79-3D69D8477DE4 3ED1C8DE-5E15-4BFE-A854-37CD826A89F5 Linux filesystem
/dev/nvme0n1p4 209717248 2000408575 1790691328 0FC63DAF-8483-4772-8E79-3D69D8477DE4 8F59FE44-E6BD-4CA5-A4C4-EEE6224B264E Linux filesystem---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
○ → lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
└─sda1 exfat 1.0 9C33-6BBD
sdb iso9660 Joliet Extension ARCH_202508 2025-08-01-13-39-26-00
├─sdb1 iso9660 Joliet Extension ARCH_202508 2025-08-01-13-39-26-00
└─sdb2 vfat FAT32 ARCHISO_EFI 688C-C38E
nvme1n1
└─nvme1n1p1 ext4 1.0 vault 18197137-e6f4-43c4-a06f-8d12b03c7d84 421G 49% /mnt/vault
nvme0n1
├─nvme0n1p1 vfat FAT32 -D87D 1.9G 5% /boot
├─nvme0n1p2 swap 1 1c3aef1e-c453-4ab8-a7ee-1ea35224f896 [SWAP]
├─nvme0n1p3 ext4 1.0 5d89e712-d6bc-45ad-a848-efd2496d804b 1.7G 91% /
└─nvme0n1p4 ext4 1.0 be6c0853-2a09-4385-b03f-16d87e0e0f21 273.1G 62% /home---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p3
UUID=5d89e712-d6bc-45ad-a848-efd2496d804b / ext4 rw,relatime 0 1
# /dev/nvme0n1p4
UUID=be6c0853-2a09-4385-b03f-16d87e0e0f21 /home ext4 rw,relatime 0 2
# /dev/nvme0n1p1
UUID=D410-D87D /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
# /dev/nvme0n1p2
UUID=1c3aef1e-c453-4ab8-a7ee-1ea35224f896 none swap defaults 0 0
# dev/nvme1n1p1
UUID=18197137-e6f4-43c4-a06f-8d12b03c7d84 /mnt/vault ext4 defaults,noatime 0 2---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
!Last Shutdown!
○ → journalctl --catalog --since="2026-8-12" --grep="boot"
2026-08-12 13:00:43 ⌚ ArchLukas in ~
○ → journalctl --catalog --since="2026-8-12" --grep="boot"
Aug 12 01:09:23 ArchLukas systemd[1]: Stopping Record System Boot/Shutdown in UTMP...
░░ Subject: A stop job for unit systemd-update-utmp.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit systemd-update-utmp.service has begun execution.
░░
░░ The job identifier is 12007.
Aug 12 01:09:23 ArchLukas systemd[1]: Stopped Record System Boot/Shutdown in UTMP.
░░ Subject: A stop job for unit systemd-update-utmp.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit systemd-update-utmp.service has finished.
░░
░░ The job identifier is 12007 and the job result is done.
Aug 12 01:09:23 ArchLukas systemd[1]: Unmounting /boot...
░░ Subject: A stop job for unit boot.mount has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit boot.mount has begun execution.
░░
░░ The job identifier is 11891.
Aug 12 01:09:24 ArchLukas systemd[1]: boot.mount: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit boot.mount has successfully entered the 'dead' state.
Aug 12 01:09:24 ArchLukas systemd[1]: Unmounted /boot.
░░ Subject: A stop job for unit boot.mount has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit boot.mount has finished.-------------------------
First boot failed, cant be mounted!
Second boot i selected the wrong usb and it booted back into the error!
Third i used the live usb and after that i was able to boot back into arch!
The job identifier is 11891 and the job result is done.
-- Boot 51b6c3ed6dc247adad49e6ab1e78492c --
Aug 12 11:37:23 archlinux kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5d89e712-d6bc-45ad-a848-efd2496d804b rw nowatchdog
Aug 12 11:37:23 archlinux kernel: Secure boot disabled
Aug 12 11:37:23 archlinux kernel: Booting paravirtualized kernel on bare hardware
Aug 12 11:37:23 archlinux kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5d89e712-d6bc-45ad-a848-efd2496d804b rw nowatchdog
Aug 12 11:37:23 archlinux kernel: smpboot: CPU0: Intel(R) Core(TM) i7-14700K (family: 0x6, model: 0xb7, stepping: 0x1)
Aug 12 11:37:23 archlinux kernel: smpboot: x86: Booting SMP configuration:
Aug 12 11:37:23 archlinux kernel: smpboot: Total of 28 processors activated (191385.60 BogoMIPS)
Aug 12 11:37:23 archlinux kernel: efi: Freeing EFI boot services memory: 118584K
Aug 12 11:37:23 archlinux kernel: pci 0000:03:00.0: vgaarb: setting as boot VGA device
Aug 12 11:37:23 archlinux systemd[1]: Started Display Boot-Time Emergency Messages In Full Screen.
Aug 12 11:37:24 archlinux systemd[1]: Stopping Display Boot-Time Emergency Messages In Full Screen...
░░ Subject: A stop job for unit systemd-bsod.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit systemd-bsod.service has begun execution.
░░
░░ The job identifier is 98.
Aug 12 11:37:24 archlinux systemd[1]: Stopped Display Boot-Time Emergency Messages In Full Screen.
░░ Subject: A stop job for unit systemd-bsod.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit systemd-bsod.service has finished.
░░
░░ The job identifier is 98 and the job result is done.
-- Boot a92ac86e28d5422e9b9d4f106ab7bdeb --
Aug 12 11:43:06 archlinux kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5d89e712-d6bc-45ad-a848-efd2496d804b rw nowatchdog
Aug 12 11:43:06 archlinux kernel: Secure boot disabled
Aug 12 11:43:06 archlinux kernel: Booting paravirtualized kernel on bare hardware
Aug 12 11:43:06 archlinux kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5d89e712-d6bc-45ad-a848-efd2496d804b rw nowatchdog
Aug 12 11:43:06 archlinux kernel: smpboot: CPU0: Intel(R) Core(TM) i7-14700K (family: 0x6, model: 0xb7, stepping: 0x1)
Aug 12 11:43:06 archlinux kernel: smpboot: x86: Booting SMP configuration:
Aug 12 11:43:06 archlinux kernel: smpboot: Total of 28 processors activated (191385.60 BogoMIPS)
Aug 12 11:43:06 archlinux kernel: efi: Freeing EFI boot services memory: 113096K
Aug 12 11:43:06 archlinux kernel: pci 0000:03:00.0: vgaarb: setting as boot VGA device
Aug 12 11:43:06 archlinux systemd[1]: Started Display Boot-Time Emergency Messages In Full Screen.
Aug 12 11:43:07 archlinux systemd[1]: Stopping Display Boot-Time Emergency Messages In Full Screen...
░░ Subject: A stop job for unit systemd-bsod.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit systemd-bsod.service has begun execution.
░░
░░ The job identifier is 101.
Aug 12 11:43:07 archlinux systemd[1]: Stopped Display Boot-Time Emergency Messages In Full Screen.
░░ Subject: A stop job for unit systemd-bsod.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit systemd-bsod.service has finished.
░░
░░ The job identifier is 101 and the job result is done.
Aug 12 11:43:17 ArchLukas systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.
░░ Subject: Mount point is not empty
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The directory /boot is specified as the mount point (second field in
░░ /etc/fstab or Where= field in systemd unit file) and is not empty.
░░ This does not interfere with mounting, but the pre-existing files in
░░ this directory become inaccessible. To see those over-mounted files,
░░ please manually mount the underlying file system to a secondary
░░ location.
Aug 12 11:43:17 ArchLukas systemd[1]: Mounting /boot...
░░ Subject: A start job for unit boot.mount has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit boot.mount has begun execution.
░░
░░ The job identifier is 195.
Aug 12 11:43:17 ArchLukas mount[746]: mount: /boot: unknown filesystem type 'vfat'.
Aug 12 11:43:17 ArchLukas 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 ExecMount= process belonging to unit boot.mount has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 32.
Aug 12 11:43:17 ArchLukas 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'.
Aug 12 11:43:17 ArchLukas 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 195 and the job result is failed.
Aug 12 11:43:17 ArchLukas systemd[1]: Listening on Boot Loader Control Service Socket.
░░ Subject: A start job for unit systemd-bootctl.socket has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-bootctl.socket has finished successfully.
░░
░░ The job identifier is 270.
Aug 12 11:43:17 ArchLukas systemd[1]: Update Boot Loader Random Seed skipped, no trigger condition checks were met.
░░ Subject: A start job for unit systemd-boot-random-seed.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-boot-random-seed.service has finished successfully.
░░
░░ The job identifier is 169.
Aug 12 11:43:17 ArchLukas systemd[1]: Initial Setup skipped, unmet condition check ConditionFirstBoot=yes
░░ Subject: A start job for unit systemd-firstboot.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-firstboot.service has finished successfully.
░░
░░ The job identifier is 178.
Aug 12 11:43:17 ArchLukas systemd[1]: First Boot Complete skipped, unmet condition check ConditionFirstBoot=yes
░░ Subject: A start job for unit first-boot-complete.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit first-boot-complete.target has finished successfully.
░░
░░ The job identifier is 179.
Aug 12 11:43:17 ArchLukas systemd[1]: Starting Record System Boot/Shutdown in UTMP...
░░ Subject: A start job for unit systemd-update-utmp.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-update-utmp.service has begun execution.
░░
░░ The job identifier is 156.
Aug 12 11:43:17 ArchLukas systemd[1]: Finished Record System Boot/Shutdown in UTMP.
░░ Subject: A start job for unit systemd-update-utmp.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-update-utmp.service has finished successfully.
░░
░░ The job identifier is 156.
-- Boot b1fa88222e374bf8a3e32abca62adec1 --
Aug 12 11:55:38 archlinux kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5d89e712-d6bc-45ad-a848-efd2496d804b rw nowatchdog
Aug 12 11:55:38 archlinux kernel: Secure boot disabled
Aug 12 11:55:38 archlinux kernel: Booting paravirtualized kernel on bare hardware
Aug 12 11:55:38 archlinux kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5d89e712-d6bc-45ad-a848-efd2496d804b rw nowatchdog
Aug 12 11:55:38 archlinux kernel: smpboot: CPU0: Intel(R) Core(TM) i7-14700K (family: 0x6, model: 0xb7, stepping: 0x1)
Aug 12 11:55:38 archlinux kernel: smpboot: x86: Booting SMP configuration:
Aug 12 11:55:38 archlinux kernel: smpboot: Total of 28 processors activated (191385.60 BogoMIPS)
Aug 12 11:55:38 archlinux kernel: efi: Freeing EFI boot services memory: 118576K
Aug 12 11:55:38 archlinux kernel: pci 0000:03:00.0: vgaarb: setting as boot VGA device
Aug 12 11:55:38 archlinux systemd[1]: Started Display Boot-Time Emergency Messages In Full Screen.
Aug 12 11:55:39 archlinux systemd[1]: Stopping Display Boot-Time Emergency Messages In Full Screen...
░░ Subject: A stop job for unit systemd-bsod.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit systemd-bsod.service has begun execution.
░░
░░ The job identifier is 99.
Aug 12 11:55:39 archlinux systemd[1]: Stopped Display Boot-Time Emergency Messages In Full Screen.
░░ Subject: A stop job for unit systemd-bsod.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit systemd-bsod.service has finished.
░░
░░ The job identifier is 99 and the job result is done.
Aug 12 11:55:48 ArchLukas kernel: Bluetooth: hci0: Secure boot is enabled
Aug 12 11:55:48 ArchLukas kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
Aug 12 11:55:48 ArchLukas kernel: Bluetooth: hci0: Boot Address: 0x100800
Aug 12 11:55:48 ArchLukas systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.
░░ Subject: Mount point is not empty
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The directory /boot is specified as the mount point (second field in
░░ /etc/fstab or Where= field in systemd unit file) and is not empty.
░░ This does not interfere with mounting, but the pre-existing files in
░░ this directory become inaccessible. To see those over-mounted files,
░░ please manually mount the underlying file system to a secondary
░░ location.
Aug 12 11:55:48 ArchLukas systemd[1]: Mounting /boot...
░░ Subject: A start job for unit boot.mount has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit boot.mount has begun execution.
░░
░░ The job identifier is 204.
Aug 12 11:55:48 ArchLukas systemd[1]: Mounted /boot.
░░ Subject: A start job for unit boot.mount has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit boot.mount has finished successfully.
░░
░░ The job identifier is 204.
Aug 12 11:55:48 ArchLukas systemd[1]: Listening on Boot Loader Control Service Socket.
░░ Subject: A start job for unit systemd-bootctl.socket has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-bootctl.socket has finished successfully.
░░
░░ The job identifier is 250.
Aug 12 11:55:48 ArchLukas systemd[1]: Update Boot Loader Random Seed skipped, no trigger condition checks were met.
░░ Subject: A start job for unit systemd-boot-random-seed.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-boot-random-seed.service has finished successfully.
░░
░░ The job identifier is 176.
Aug 12 11:55:49 ArchLukas systemd[1]: Initial Setup skipped, unmet condition check ConditionFirstBoot=yes
░░ Subject: A start job for unit systemd-firstboot.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-firstboot.service has finished successfully.
░░
░░ The job identifier is 213.
Aug 12 11:55:49 ArchLukas systemd[1]: First Boot Complete skipped, unmet condition check ConditionFirstBoot=yes
░░ Subject: A start job for unit first-boot-complete.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit first-boot-complete.target has finished successfully.
░░
░░ The job identifier is 140.
Aug 12 11:55:49 ArchLukas systemd[1]: Starting Record System Boot/Shutdown in UTMP...
░░ Subject: A start job for unit systemd-update-utmp.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-update-utmp.service has begun execution.
░░
░░ The job identifier is 217.
Aug 12 11:55:49 ArchLukas systemd[1]: Finished Record System Boot/Shutdown in UTMP.
░░ Subject: A start job for unit systemd-update-utmp.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-update-utmp.service has finished successfully.
░░
░░ The job identifier is 217.
Aug 12 11:55:49 ArchLukas NetworkManager[883]: <info> [1786528549.5051] NetworkManager (version 1.58.0-1) is starting... (boot:b1fa8822-2e37-4bf8-a3e3-2abca62adec1)
Aug 12 11:55:49 ArchLukas kernel: Bluetooth: hci0: Waiting for device to boot
Aug 12 11:55:49 ArchLukas kernel: Bluetooth: hci0: Device booted in 15605 usecs
Aug 12 11:56:17 ArchLukas systemd[1114]: Starting Splash screen shown during boot...
░░ Subject: A start job for unit UNIT has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has begun execution.
░░
░░ The job identifier is 127.
Aug 12 11:56:20 ArchLukas systemd[1114]: Finished Splash screen shown during boot.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 127.
Aug 12 12:10:31 ArchLukas sudo[5560]: Lukas : TTY=pts/0 ; PWD=/boot/EFI ; USER=root ; COMMAND=/usr/bin/mv dev proc run sys tmp /home/Lukas/BootFilesMoved
Aug 12 12:10:41 ArchLukas sudo[5615]: Lukas : TTY=pts/0 ; PWD=/boot/EFI ; USER=root ; COMMAND=/usr/bin/mv dev proc run sys tmp /home/Lukas/Lukas/BootFilesMoved
Aug 12 12:10:51 ArchLukas sudo[5705]: Lukas : TTY=pts/0 ; PWD=/boot ; USER=root ; COMMAND=/usr/bin/mv dev proc run sys tmp /home/Lukas/Lukas/BootFilesMoved
Aug 12 12:16:34 ArchLukas dolphin[6107]: Multiple items found with the URL QUrl("file:///boot/grub/grubenv")
Aug 12 12:16:34 ArchLukas dolphin[6107]: index 143 : [KFileItem for QUrl("file:///boot/grub/grubenv")]
Aug 12 12:16:34 ArchLukas dolphin[6107]: index 7 : [KFileItem for QUrl("file:///boot/grub/grubenv")]
Aug 12 12:16:34 ArchLukas dolphin[6107]: parent [KFileItem for QUrl("file:///boot/grub")]
Aug 12 12:16:34 ArchLukas dolphin[6107]: Multiple items found with the URL QUrl("file:///boot/grub/grub.cfg")
Aug 12 12:16:34 ArchLukas dolphin[6107]: index 15 : [KFileItem for QUrl("file:///boot/grub/grub.cfg")]
Aug 12 12:16:34 ArchLukas dolphin[6107]: index 6 : [KFileItem for QUrl("file:///boot/grub/grub.cfg")]
Aug 12 12:16:34 ArchLukas dolphin[6107]: parent [KFileItem for QUrl("file:///boot/grub")]
lines 274-317/317 (END)Offline
#2 2026-08-12 11:26:46
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 77,550
Re: Failed To Mount Boot After -Syu And Restart
Aug 12 11:43:17 ArchLukas mount[746]: mount: /boot: unknown filesystem type 'vfat'.
Aug 12 11:37:23 archlinux kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5d89e712-d6bc-45ad-a848-efd2496d804b rw nowatchdogYou're trying to mount a boot partition (and fail) but are actually booting from the root partition.
When you set the system to a point where the bogus boot partition mounts, you'll end up installing kernel and initramfs there - but it's the wrong location.
Either migrate the bootloader to the boot partition or remove the /boot entry from your fstab
Offline
#3 2026-08-12 14:33:10
- SteamLuki
- Member
- Registered: 2025-07-30
- Posts: 3
Re: Failed To Mount Boot After -Syu And Restart
Thank you for answering.
Why does the boot partition fail to mount ?
It says unknown filesystem type vfat but why would it be unknown ?
About: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5d89e712-d6bc-45ad-a848-efd2496d804b rw nowatchdog
5d89e is the root partition, so it searches the root partition for the linux file, even though it should search in the boot partition?
Is this all related to grub ?
I found this in the grub.cfg:
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-5d89e712-d6bc-45ad-a848-efd2496d804b' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod fat
search --no-floppy --fs-uuid --set=root D410-D87D
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=5d89e712-d6bc-45ad-a848-efd2496d804b rw amdgpu.ppfeaturemask=0xffffffff
echo 'Loading initial ramdisk ...'
initrd /intel-ucode.img /initramfs-linux.img
}
As i understood, probably wrong, it sets the dir to D410-D87D which is the boot partition.
This part: linux /vmlinuz-linux root=UUID=5d89e, apparantly sets the linux root folder to the root partition?
Again, very new to this stuff, sorry.
Offline
#4 2026-08-12 14:43:59
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 77,550
Re: Failed To Mount Boot After -Syu And Restart
The booting kernel is older than the installed kernel, there's literally no longer a vfat module on disk for that version.
The "problem" is "BOOT_IMAGE=/boot/vmlinuz-linux", the leading "/boot/" means the kernel is searched in the /boot directory of the root partition, if you'd use the boot partition it would be "BOOT_IMAGE=/vmlinuz-linux" (DON'T JUST CHANGE THAT!!)
Is this all related to grub ?
Yes, but what you posted is from the grub.cfg on the boot partition, which is not relevant because you're not booting from there.
If you want to change the boot partition, boot the system, make sure the /boot partition is mounted and re-install grub (grub-install …) and update the grub config.
Reboot, if things worked out "cat /proc/cmdline" will say "BOOT_IMAGE=/vmlinuz-linux"
You should then umount /boot and clean the mountpoint, then re-mount /boot
Offline
#5 2026-08-12 15:17:54
- SteamLuki
- Member
- Registered: 2025-07-30
- Posts: 3
Re: Failed To Mount Boot After -Syu And Restart
The command returned the correct value and i unmounted and remounted.
I will wait a week, update arch and all its packages and see if any other errors happens.
I did actualy move everything from root/boot into a safe folder and rebooted.
System immediately booted into the live usb and from there i installed everything again, like linux, linux headers, grub and then i ran grub install.
Guess that fixed it but i had no idea at that point, your explanation now makes alot more sense what needed to happen and happend.
Thank you very much for your help
Offline