Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

rebornKidz · 2026-01-22 07:46:19

the last change is on deployed on p1, right?
I am not sure how to answer the question sir.

but here is a lib and lib64 folder which contain kenel forlder, which contain couple of files.
I already try to use `ls -lR` and a screenshoot, but the folder cannot be accessed via windows.

seth · 2026-01-22 09:35:38

You can check the contents from the life distro

mount /dev/nvme0n1p1 /mnt
ls -l /mnt

If there's a vmlinuz-linux file you might actually be booting from that partition, having it double as root and boot partition.

rebornKidz · 2026-01-22 09:46:53

it seems yes, i should installed on p4 right. but what is there is still the old one.
But why i still mising the vfat module? it so confusing, i maybe do some mistake back then.

seth · 2026-01-22 10:03:39

Stop paraphrasing, post the contents of /dev/nvme0n1p1
IFF

mount /dev/nvme0n1p1 /mnt
stat /dev/nvme0n1p1 /mnt/vmlinuz-linux

shows such file

mount /dev/nvme0n1p1 /mnt/boot
arch-chroot /mnt
pacman -S linux

*would* allow you to reboot but the setup is completely bonkers, what you likely want to do instead is either
a) just boot from the root partition, w/o a dedicated boot partition
b) use nvme0n1p4 as boot partition

Either will require to re-run grub-install and grub-mkconfig with the desired configuration.

rebornKidz · 2026-01-25 14:08:15

What i want is b for sure, but I am too reckless.
I will try the grub-install followed by grub-mkconfig, i shall do it in chroot env right sir?
thanks for staying with me.

seth · 2026-01-25 14:49:35

i shall do it in chroot env right sir?

Yes. Nb. that in preparation you'll have to correctly mount /dev/nvme0n1p1 into /mnt and /dev/nvme0n1p4 into /mnt/boot before chrooting and fixing the grub installation and config

rebornKidz · 2026-01-25 15:08:23

nah, already did, but it cannot be done.
somehow i cannot remember the exact command when installing arch the for the first time.

grub-install --target=x86_64-efi --efi-directory=ESP --bootloader-id=Arch

Error: usr/lib/grub/x86_efi/modinfo.sh not exist, please specify --target --directory

seth · 2026-01-25 15:21:27

https://wiki.archlinux.org/title/GRUB#Installation
The "ESP" in your line is a placeholder - you're not supposed to have multiple, but since nvme0n1p4 is tagged as ESP, --efi-directory=/boot will do.
But

Error: usr/lib/grub/x86_efi/modinfo.sh not exist, please specify --target --directory

You also seem to not have chrooted into the installed system?

rebornKidz · 2026-01-25 17:47:20

Which one i do multiple sir?
I sure it was on chrooted /mnt.

with '--efi-directory=/boot'

/boot doesnot look like an EFI partition

with --directory instead efi-directory yield

/boot/modinfo.sh not exist

given `ls -lR /boot`

boot/:
total 60204
-rw-r--r-- 1 root root   204800 Nov 11 23:31 amd-ucode.img
drwxr-xr-x 2 root root     4096 Jan 26 00:34 grub
-rw------- 1 root root 44817878 Jan 26 00:33 initramfs-linux.img
-rw-r--r-- 1 root root 16613568 Jan 26 00:33 vmlinuz-linux

boot/grub:
total 0

given `stat boot/vmlinuz-linux`

  File: boot/vmlinuz-linux
  Size: 16613568  	Blocks: 32456      IO Block: 4096   regular file
Device: 259,1	Inode: 3969537     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2026-01-26 00:33:22.894767990 +0700
Modify: 2026-01-26 00:33:22.868767756 +0700
Change: 2026-01-26 00:33:22.868767756 +0700
 Birth: 2026-01-26 00:33:22.860767685 +0700

seth · 2026-01-25 21:12:22

From the install iso

mkdir /tmp/sda1
mount /dev/sda1 /tmp/sda1
mkdir /tmp/nvme0n1p4
mount /dev/nvme0n1p4 /tmp/nvme0n1p4
ls -lR /tmp/sda1 /tmp/nvme0n1p4 | curl -F 'file=@-' 0x0.st

though I'm almost inclined to say that you should probably re-install archlinux, this time actually following https://wiki.archlinux.org/title/Installation_guide - instead of probably some youtuber - to get a basic understanding of the system in front of you.

rebornKidz · 2026-01-26 06:53:26

Sadly i follow that one tho, i just so reckless backthen.
I thought I know what i am doing, i am youtuber my self

Do you think installing grub https://archlinux.org/packages/?name=grub will make any different?

https://0x0.st/PZ5-.txt

seth · 2026-01-26 07:48:14

I thought I know what i am doing, i am youtuber my self

Hopefully not the kind who shows others to install archlinux…

/tmp/nvme0n1p4/EFI:
total 8
drwxr-xr-x 2 root root 4096 Jun 25  2025 Arch
drwxr-xr-x 3 root root 4096 Nov 18 16:08 EFI

/tmp/nvme0n1p4/EFI/Arch:
total 148
-rwxr-xr-x 1 root root 151552 Jul  1  2025 grubx64.efi

/tmp/nvme0n1p4/EFI/EFI:
total 4
drwxr-xr-x 2 root root 4096 Nov 18 16:08 Arch

/tmp/nvme0n1p4/EFI/EFI/Arch:
total 156
-rwxr-xr-x 1 root root 159744 Nov 18 16:08 grubx64.efi
…
/tmp/sda1/EFI:
total 2
drwxr-xr-x 2 root root 1024 Mar 10  2022 Boot
drwxr-xr-x 4 root root 1024 Jan 26  2026 Microsoft

/tmp/sda1/EFI/Boot:
total 2789
-rwxr-xr-x 1 root root 2855368 Sep 10 17:08 bootx64.efi

nvme0n1p4 and sda1 have both EFIs (grub and MS respectively) and apparently you nested an EFI on nvme0n1p4 and labeled both Arch

mount /dev/nvme0n1p1 /mnt
mount /dev/nvme0n1p4 /mnt/boot
arch-chroot /mnt
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=Arch
pacman -S linux # just re-install, don't try to update anything
grub-mkconfig -o /boot/grub/grub.cfg
exit
reboot

rebornKidz · 2026-01-26 09:25:19

I will be the one who glorifies arch, Say "I use arch btw".
I think i have done it, but let me try again.

That was my old mistake, using wrong option and does not aware of the implication.
Strangely enough set, it was unable to boot use the default option grub provided.
Under the advance i see the LTS version are listed, I chose it, and I can boot from it.

but why i cant do

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=Arch

earlier?

At this stage, i have no idea. Just want to see your advice.

Last edited by rebornKidz (2026-01-26 09:26:01)

seth · 2026-01-26 13:36:16

but why i cant do
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=Arch
earlier?

I've no idea but all indications are that you were not operating from the chroot, worst case you'll have to

grub-install --target=x86_64-efi --efi-directory=/mnt/boot --bootloader-id=Arch

outside the chroot.

What is the status quo? Did you run into any errors follwoing #37?

rebornKidz · 2026-01-26 14:21:17

no error, as described sir.
the bootable on is on lts kernel, the default is still the old kernel 6.15.3 if I remember correctly.

Thank you sir

seth · 2026-01-26 15:15:16

If you can boot the LTS kernel please post

sudo journalctl -b | curl -F 'file=@-' 0x0.st

(cat /proc/cmdline; lsblk -f; ls -lR /boot) | curl -F 'file=@-' 0x0.st

rebornKidz · 2026-01-26 19:05:17

gladly sir:
http://0x0.st/PN-t.txt

http://0x0.st/PN-w.txt

Jan 27 08:41:54 narayana.search systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.
Jan 27 08:41:54 narayana.search systemd[1]: Mounting /boot...
Jan 27 08:41:54 narayana.search systemd[1]: Mounting /home...
Jan 27 08:41:54 narayana.search systemd[1]: Virtual Machine and Container Storage (Compatibility) was skipped because of an unmet condition check (ConditionPathExists=/var/lib/machines.raw).
Jan 27 08:41:54 narayana.search systemd[1]: Listening on Disk Image Download Service Socket.
Jan 27 08:41:54 narayana.search kernel: iwlwifi 0000:07:00.0: base HW address: c8:58:b3:79:6d:8c
Jan 27 08:41:54 narayana.search systemd[1]: Mounted /boot.

hmm in aproper setup , what /boot looks like at this stage?

Last edited by rebornKidz (2026-01-26 19:12:07)

seth · 2026-01-26 21:18:51

BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=759f6fc2-0535-4342-9f93-5f6bb1486fb3 rw loglevel=3 quiet
NAME        FSTYPE FSVER LABEL         UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                        
|-sda1      vfat   FAT32               30C5-ACC5                                           
|-sda2                                                                                     
|-sda3      ntfs         System        4A60D16C60D15F6F                                    
`-sda4      ntfs                       DAA40FCEA40FAC57                                    
nvme0n1                                                                                    
|-nvme0n1p1 ext4   1.0   /             759f6fc2-0535-4342-9f93-5f6bb1486fb3   28.9G    48% /
|-nvme0n1p2 ntfs         /cross-system 68DFD0FE55198462                       41.1G    80% /run/media/plasma/_cross-system
|-nvme0n1p3 ext4   1.0   /arch-media   1256b93c-8d3d-44cd-b630-13dbf8a0bcbb  191.5G     0% /home
`-nvme0n1p4 vfat   FAT32 ESP           0F5A-6664                             709.3M    31% /boot
/boot:
total 304004
drwxr-xr-x 2 root root      4096 Nov 29 22:07 $RECYCLE.BIN
drwxr-xr-x 4 root root      4096 Nov 18 23:08 EFI
drwxr-xr-x 2 root root      4096 Jun 22  2025 System Volume Information
-rwxr-xr-x 1 root root    307200 Jan 11 10:52 amd-ucode.img
drwxr-xr-x 6 root root      4096 Jan 26 16:05 grub
-rwxr-xr-x 1 root root 193619211 Oct  5 13:50 initramfs-linux-fallback.img
-rwxr-xr-x 1 root root  41998722 Jan 19 11:59 initramfs-linux-lts.img
-rwxr-xr-x 1 root root  44817878 Jan 26 16:04 initramfs-linux.img
-rwxr-xr-x 1 root root  16613568 Jan 26 16:04 vmlinuz-linux
-rwxr-xr-x 1 root root  13914624 Jan 19 11:59 vmlinuz-linux-lts

actually looks plausible enough (nb. the timestamps of the kernels)

file -s /boot/vmlinuz-linux
pacman -Q linux

The initramfs-linux-fallback.img is stale (since i think the default preset chnged?), so don't try to boot that.
Other than that, are you sure the main kernel doesn't boot now? What kind of error do you face?

rebornKidz · 2026-01-27 11:48:25

Unable to mount unknown file system 'vfat', the same error. I haven't checked the details yet.
I don't remember changing any preset, oh Lord, did I change it when enabling dkms, or something else when install KDE plasma.

After carefully testing both default kernel and the first fallback, it have same error, Sir.

Same exact error, and I believe that is causing the failure to mount boot at the later log. Kindly remind me if I was wrong in judging the state of the problem.

Seth, do you mind assisting me in giving the forensic proof on this? I mean that still worth doing.

file -s /boot/vmlinuz-linux

/boot/vmlinuz-linux: Linux kernel x86 boot executable, bzImage, version 6.18.5-arch1-1 (linux@archlinux) #1 SMP PREEMPT_DYNAMIC 
Sun, 11 Jan 2026 17:10:53 +0000, RO-rootFS, Normal VGA, setup size 512*39, syssize 0xf6800, jump 0x26c 0x8cd88ec0fc8cd239 instruction, protocol 2.15, from protected-mode code at offset 0x2cc 0xf2f6d9
 bytes ZST compressed, relocatable, handover offset 0xf5ba00, legacy 64-bit entry point, can be above 4G, 32-bit EFI handoff entry point

pacman -Q linux, give exact match.

Here is the active preset from the bootable kernel lts.

# on /etc/mkinitcpio.d/linux.preset
ALL_kver="/boot/vmlinuz-linux"
PRESETS=('default')
default_image="/boot/initramfs-linux.img"


# on /etc/mkinitcpio.conf
MODULES=(amdgpu radeon vfat)
BINARIES=()
FILES=()
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck modconf)

vfat is supposed to be there right. On the right configuration?

seth · 2026-01-27 12:57:28

You don't have to a dd vfat to the initramfs - however this suggests you're (still) not booting from nvme0n1p4
Boot the lts kernel,

umount /boot
(lsblk -f; ls -lR /boot) | curl -F 'file=@-' 0x0.st

Go back to #37 but after the chroot first run

script -O /tmp/io.log

and after the "exit"

cat /tmp/io.log | curl -F 'file=@-' 0x0.st

Then "exit" again (the chroot) before rebooting.

rebornKidz · 2026-01-27 16:40:20

Do you mean add sir?

You don't have to add vfat to the initramfs

So it's worth trying to opt out vfat and see what happens? Let me hear your thoughts.

http://0x0.st/PN_D.txt

is better to chroot from live arch iso or from my current arch lts just fine?

seth · 2026-01-27 20:47:38

Do you mean add sir?

Yes, and please drop that "sir" stuff.

So it's worth trying to opt out vfat and see what happens?

It's presence will have no impact on the situation.

is better to chroot from live arch iso or from my current arch lts just fine?

When booting the LTS kernel you actually don't have to chroot at all, you're starting at the target system anyway.

-rw-r--r-- 1 root root   204800 Nov 11 23:31 amd-ucode.img
drwxr-xr-x 2 root root     4096 Jan 26 00:34 grub
-rw------- 1 root root 44817878 Jan 26 00:33 initramfs-linux.img
-rw-r--r-- 1 root root 16613568 Jan 26 00:33 vmlinuz-linux

Looks like you installed linux and grub into that path (nvme0n1p1/boot) as well?

rebornKidz · 2026-01-28 00:12:17

It's a honorifics, I shall stay polite. My bad, I should use sire instead.

That explains a lot, i do it by accident? ah it was just my excuse sire.
That was my crime, but i can't recall when and why i do it.

The proper setup is use nvme0n1p4, I dedicate it for the boot partition.
I do like to change the grub default option to be the bootable one, whichever kernel.

please verify below is the correct way to do so.

# boot from lts
mount /dev/nvme0n1p4 /boot
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=Arch
grub-mkconfig -o /boot/grub/grub.cfg
exit
script -O /tmp/io.log
cat /tmp/io.log | curl -F 'file=@-' 0x0.st
# reboot

Last edited by rebornKidz (2026-01-28 05:48:14)

seth · 2026-01-28 09:04:52

I should use sire instead.

If you don't stop this silliness you'll have to find yourself some else honourable (with an extra pointless U) to hold your hand going forward.

# boot from lts
mount | grep boot # check whether there's sth. already mounted there, do *not* conduct a second
mount /dev/nvme0n1p4 /boot
script -O /tmp/io.log # this here needs to happen first
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=Arch
pacman -S linux # also update/install the kernel
grub-mkconfig -o /boot/grub/grub.cfg
exit
cat /tmp/io.log | curl -F 'file=@-' 0x0.st
# reboot

rebornKidz · 2026-01-28 14:24:37

the mount

/dev/nvme0n1p4 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)

I step back, seeing the output of grub-install

grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p4.
grub-install: error: grub-core/kern/disk.c:grub_disk_open:240:disk `hostdisk//dev/nvme0n1p4' not found.

Arch Linux

#26 2026-01-22 07:46:19

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#27 2026-01-22 09:35:38

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#28 2026-01-22 09:46:53

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#29 2026-01-22 10:03:39

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#30 2026-01-25 14:08:15

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#31 2026-01-25 14:49:35

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#32 2026-01-25 15:08:23

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#33 2026-01-25 15:21:27

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#34 2026-01-25 17:47:20

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#35 2026-01-25 21:12:22

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#36 2026-01-26 06:53:26

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#37 2026-01-26 07:48:14

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#38 2026-01-26 09:25:19

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#39 2026-01-26 13:36:16

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#40 2026-01-26 14:21:17

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#41 2026-01-26 15:15:16

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#42 2026-01-26 19:05:17

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#43 2026-01-26 21:18:51

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#44 2026-01-27 11:48:25

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#45 2026-01-27 12:57:28

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#46 2026-01-27 16:40:20

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#47 2026-01-27 20:47:38

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#48 2026-01-28 00:12:17

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#49 2026-01-28 09:04:52

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

#50 2026-01-28 14:24:37

Re: Fail to boot due to vfat module,after upgrade.Strangely lts doing fine

Board footer