You are not logged in.
Pages: 1
Yesterday I updated my kernel and today arch couldn't boot. There are such entries in journal
Sep 09 16:41:36 arch systemd[1]: Mounting /home...
Sep 09 16:41:36 arch systemd[1]: Finished File System Check on /dev/disk/by-uuid/3BD5-EF23.
Sep 09 16:41:36 arch systemd[1]: Mounting /boot/efi...
Sep 09 16:41:36 arch mount[273]: mount: /boot/efi: unknown filesystem type 'vfat'.
Sep 09 16:41:36 arch systemd[1]: boot-efi.mount: Mount process exited, code=exited, status=32/n/a
Sep 09 16:41:36 arch systemd[1]: boot-efi.mount: Failed with result 'exit-code'.
Sep 09 16:41:36 arch systemd[1]: Failed to mount /boot/efi.
Sep 09 16:41:36 arch systemd[1]: Dependency failed for Local File Systems.
I tried to downgrade kernel to 5.8.6 but problem still remains.
I'll appreciate any help.
Offline
What bootloader?
This usually happens when you're loading an old kernel instead of the new one.
Offline
What bootloader?
GRUB. Can you clarify, how can I boot old kernel? I mean is there more than one kernel to boot?
Last edited by Euler-Maskerony (2020-09-09 14:45:08)
Offline
So if you look at grub.cfg, where is it loading the kernel from?
Offline
...where is it loading the kernel from?
/boot/vmlinuz-linux
Offline
Compare the kernel version:
file /boot/vmlinuz-linux
With the installed modules:
ls /usr/lib/modules
Either chroot in from the live ISO or just mount the relevant partition(s) and run the commands with the correct path.
"The nation-state domesticates the society in the name of capitalism and alienates the community from its natural foundations."
— Democratic Confederalism, Abdullah Öcalan.
Offline
I ran this commands from emergency mode and versions match (5.8.7-arch1-1). Is it a problem if I have only "5.8.7-arch1-1" entry as an output of
ls /usr/lib/modules
?
Offline
I ran this commands from emergency mode and versions match (5.8.7-arch1-1). Is it a problem if I have only "5.8.7-arch1-1" entry as an output of
ls /usr/lib/modules
?
No.
Provide more detail what you were doing before this happened, provide your grub.cfg, and explain whether you re-ran mkinitcpio -p linux and grub-mkconfig -o /boot/grub/grub.cfg. You have a "Dependency failed for Local File Systems". How long ago did you upgrade before this last time? Please explain the issue in detail if anyone is to help.
Last edited by zpg443 (2020-09-09 20:16:43)
Offline
Offline
**UPDATE**
To add that I booted off the latest AL USB ISO image to download and then arch-chroot /mnt to do the rest.
OK, I'm back in business. Had to go to AL Archive and downloaded:
linux-5.8.7.arch1-1-x86_64.pkg.tar.zst
linux-docs-5.8.7.arch1-1-x86_64.pkg.tar.zst
linux-headers-5.8.7.arch1-1-x86_64.pkg.tar.zst
# rm -rf /lib/modules/5.8.* # If I don't, mkinitcpio -p linux still uses 5.8.8 even if dir wasn't there
# cd <download_dir_path>
# pacman -U linux*
# mkinitcpio -p linux # Just to make sure I still didn't get the kernel mod errors
<rebooted>
Back in business.
Last edited by Cthulu201 (2020-09-11 13:00:53)
Offline
And since you are back in business did you mount the ESP to /boot and add a corresponding entry into your fstab so that you can properly update again?
Offline
And since you are back in business did you mount the ESP to /boot and add a corresponding entry into your fstab so that you can properly update again?
I forgot to add that I booted off of an AL USB drive - which I updated.
I didn't have to mount anything since my /etc/fstab was still good. I downgraded and everything worked fine.
Offline
Cthulu201 and Euler-Maskerony: to which Kernel version did you try boot? I'm curious since I'm just about to boot into 5.8.8, and I'm currently running 5.8.7. It is unlikely the Kernel package has a problem with vfat.
That being said, I believe you should be dropped into an emergency shell if the Kernel can not mount all filesystems in fstab.
Either way, the error mentioned in OP is probably caused because the Kernel can not find the VFAT module. VFAT_FS is compiled as a module in the default Arch linux kernel package. I'm not sure if it is included in the initramfs per default, but it is irrelevant AFAIK, as the bootloader will load the Kernel and the Kernel only needs to be able to load rootfs, which will contain rest of the modules to mount other filesystems.
Also, when asked for output of commands, paste the output here. There might be errors in your setup you have missed / have become blind for some reason.
Last edited by Wild Penguin (2020-09-11 13:07:18)
Offline
Cthulu201 and Euler-Maskerony: to which Kernel version did you try boot?
I was initially on 5.8.7 when I booted up this morning. I upgraded to 5.8.8, rebooted, and started getting EFI mount errors. I'm not looking forward to this afternoon when I update my laptop at home, but pacman.conf has the IgnorePkg function.
Offline
Wild Penguin wrote:Cthulu201 and Euler-Maskerony: to which Kernel version did you try boot?
I was initially on 5.8.7 when I booted up this morning. I upgraded to 5.8.8, rebooted, and started getting EFI mount errors. I'm not looking forward to this afternoon when I update my laptop at home, but pacman.conf has the IgnorePkg function.
IgnorePkg won't fix anything. This happens when you boot an old kernel, probably because /boot wasn't mounted when you updated. Fix it properly, don't ignore it.
Offline
There is nothing wrong with Linux-5.8.8 indeed, it can mount EFI partitions (vfat) as it should.
Some pointers to fix this: post contents of /etc/fstab and command 'sudo blkid' here. From those, someone here can probably say where things go wrong.
Last edited by Wild Penguin (2020-09-11 14:30:20)
Offline
I've never used systemd-boot, but reading the Wiki, this claim:
Looks like 5.8.8 is installing to the /boot directory and not the /efi directory like I setup per the wiki - I use systemd-boot.
is just wrong. Either 1) you need to mount efi partition to /boot or 2) mount EFI partition to /efi and use a boot loader which can load kernels in some other partition than the EFI partition (which systemd-boot can not do) or 3) use Unified kernel images or EFISTUB loaders. See: https://wiki.archlinux.org/index.php/Sy … figuration , https://wiki.archlinux.org/index.php/Sy … rnel_image and https://wiki.archlinux.org/index.php/EFISTUB and https://wiki.archlinux.org/index.php/Ar … oot_loader (especially the red box).
AFAIK all kernel packages will install to /boot.
Last edited by Wild Penguin (2020-09-14 20:07:06)
Offline
Pages: 1