You are not logged in.

Pages: 1

#1 2020-03-14 16:36:44

ibu
Member
Registered: 2020-03-14
Posts: 2

/boot failed to mount: unknown filesystem type 'vfat'

Apologies for posting what I have seen is a quite common problem for newbies such as myself- I have had a look through the Wiki and over some previous posts but I'm a little bit stuck as to what to do.

I believe what has happened is that I have performed a full update with pacman -Syu and then failed to do a full reboot. When attempting a normal boot the /boot partition fails to mount: using systemctl status boot.mount the output is as follows:

* boot.mount - /boot
	Loaded: loaded (/etc/fstab; generated)
	Active: failed (Result: exit-code)
	 Where: /boot
	 What: /dev/disk/by-uuid/D826-F120

Mar 14 12:59:45 ArchPC systemd[1]: Mounting /boot...
Mar 14 12:59:45 ArchPC mount[382]: mount: /boot: unknown filesystem type 'vfat'.
Mar 14 12:59:45 ArchPC systemd[1]: boot.mount: Mount process exited, code=exited, status=32/n/a
Mar 14 12:59:45 ArchPC systemd[1]: boot.mount: Failed with result 'exit-code'.
Mar 14 12:59:45 ArchPC systemd[1]: Failed to mount /boot.

When using modprobe vfat the output is 

modprobe: FATAL: Module vfat not found in directory /lib/modules/5.4.15-arch1-1

When checking uname -r the output is 

5.4.15-arch1-1

whereas checking pacman -Q linux it shows 

linux 5.5.8.arch1-1

I have attempted booting using my liveUSB, mounting the root and boot partitions, chrooting into /mnt and running a full update again with pacman -Syu, though this hasn't been successful in solving the problem. I have seen the suggestion that one downgrades to the earlier version; in a bold and wise move, I cleared the cache having misdiagnosed the problem earlier.

fstab file is as follows:

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mmcblk1p7
UUID= 95b17740-bb1e-4cc3-ae90-908362ec1469		/		ext4		rw,relatime	0 1

# /dev/mmcblk1p8
UUID=0a95b42a-e6c9-49d0-9949-33b626187a84		/home		ext4		rw,relatime	0 2

# /dev/mmcblk1p7
UUID= 95b17740-bb1e-4cc3-ae90-908362ec1469		/		ext4		rw,relatime	0 1

# /dev/mmcblk1p8
UUID=0a95b42a-e6c9-49d0-9949-33b626187a84		/home		ext4		rw,relatime	0 2

# /dev/mmcblk1p7
UUID= 95b17740-bb1e-4cc3-ae90-908362ec1469		/		ext4		rw,relatime	0 1

# /dev/mmcblk1p1 LABEL=SYSTEM_DRV
UUID=D826-F120		/boot		vfat		rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/mmcblk1p8
UUID=0a95b42a-e6c9-49d0-9949-33b626187a84		/home		ext4		rw,relatime	0 2

# /dev/mmcblk1p7
UUID= 95b17740-bb1e-4cc3-ae90-908362ec1469		/mt		ext4		rw,relatime	0 2

# /dev/mmcblk1p7
UUID= 95b17740-bb1e-4cc3-ae90-908362ec1469		/		ext4		rw,relatime	0 1

# /dev/mmcblk1p7
UUID= 95b17740-bb1e-4cc3-ae90-908362ec1469		/		ext4		rw,relatime	0 1

# /dev/mmcblk1p1 LABEL=SYSTEM_DRV
UUID=D826-F120		/boot		vfat		rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/mmcblk1p6
UUID=2ad6c47d-2448-49e9-b397-38e3524a50c9		none		swap		defaults	0 0

I saw elsewhere that someone had an issue with two drives sharing a UUID, which I don't think is the problem here from running lsblk -f:

NAME	FSTYPE	LABEL		UUID					MOUNTPOINT
mmcblk0                                                                 
├─mmcblk0p1	vfat	SYSTEM_DRV	D826-F120				/boot
├─mmcblk0p2		
├─mmcblk0p3	ntfs	Windows		CCBE33ABBE338CC8
├─mmcblk0p5	ntfs	WINRE_DRV	462A34B32A32A23B
├─mmcblk0p6	swap			2ad6c47d-2448-49e9-b397-38e3524a50c9		
├─mmcblk0p7	ext4			95b17740-bb1e-4cc3-ae90-908362ec1469	/mnt
└─mmcblk0p8	ext4			0a95b42a-e6c9-49d0-9949-33b626187a84

I use rEFInd as a bootmanager, and I am dualbooting with Windows. refind_linux.conf file is as follows:

”Boot with standard options”   “archisobasedir=arch   archisolabel=ARCH_202001”
”Boot to single-user mode”   “archisobasedir=arch   archisolabel=ARCH_202001 single”
”Boot with minimal options”   “ro root=/dev/mmcblk0p7”

Checking efibootmgr -v I am given the following output:

BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0000,0012,0013,0014,0015,0016,0017,0018,001A,0019
Boot0000*	rEFInd Boot Manager	HD(1,GPT,67e3fd35-2047-432b-a51b-bd93a5aa30a8,0x800,0x82000)/File(\EFIzrefind\refind_x64.efi)
Boot0010 	Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011	Boot Menu	FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0012*	SATA SSD:	VenMsg(bc7838d2-0f82-4d60-8316c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
Boot0013*	eMMC Card:	SanDisk iNAND 128GB	PciRoot(0x0)/Pci(0x1c,0x0)/Ctrl(0x0)c.J8.p[H...S....
Boot0014*	SATA HDD:	VenMsg(bc7838d2-0f82-4d60-8316c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot0015*	ATAPI CD:	VenMsg(bc7838d2-0f82-4d60-8316c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot0016*	USB HDD:	VenMsg(bc7838d2-0f82-4d60-8316c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0017*	USB CD:		VenMsg(bc7838d2-0f82-4d60-8316c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0018*	PCI LAN:	VenMsg(bc7838d2-0f82-4d60-8316c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0019*	USB LAN:	VenMsg(bc7838d2-0f82-4d60-8316c068ee79d25b,e854bca4cae7704ca322b00da0376322)
Boot001A*	USG FDD:	VenMsg(bc7838d2-0f82-4d60-8316c068ee79d25b,6ff015a28830b543a8b8641009461e49)

Please let me know if there is anything I can add, and apologies for missing anything key out. Really appreciate your help!

Offline

#2 2020-03-14 17:30:02

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: /boot failed to mount: unknown filesystem type 'vfat'

Wow, that fstab is a mess. And you're mounting your root filesystem to two different place?

Write out an actual config for your bootloader so you know where it's getting the kernel from. The mount everything from USB, chroot in, and reinstall the kernel.

Offline

#3 2020-03-14 18:46:52

ibu
Member
Registered: 2020-03-14
Posts: 2

Re: /boot failed to mount: unknown filesystem type 'vfat'

Thank you very much for your reply, Scimmia.

Have rationalised the fstab in line with the Wiki:

# <file system> <dir> <type> <options> <dump> <pass>

# /dev/mmcblk1p1 LABEL=SYSTEM_DRV
UUID=D826-F120          /boot           vfat            defaults      0 2

# /dev/mmcblk1p8
UUID=0a95b42a-e6c9-49d0-9949-33b626187a84               /home           ext4            defaults     0 2

# /dev/mmcblk1p7
UUID= 95b17740-bb1e-4cc3-ae90-908362ec1469              /mnt             ext4            defaults     0 2

# /dev/mmcblk1p6
UUID=2ad6c47d-2448-49e9-b397-38e3524a50c9               none            swap            defaults        0 0

and have similarly cleaned up the config for rEFInd as per the example in the Wiki:

“Boot with standard options”		“root=PARTUUID=95b17740-bb1e-4cc3-ae90-908362ec1469 rw add_efi_memmap”
“Boot using fallback initramfs”	“root=PARTUUID=95b17740-bb1e-4cc3-ae90-908362ec1469 rw add_efi_memmap initrd=/boot/initramfs-linux-fallback.img”
“Boot to terminal”		“root=PARTUUID=95b17740-bb1e-4cc3-ae90-908362ec1469 rw add_efi_memmap systemd.unit=multi-user.target”

Then arch-chrooted in and reinstalled the kernel. No luck with mounting /boot on rebooting, though versions have updated: uname -r gives "5.4.6-arch3-1" and pacman -Q linux gives "5.5.9.arch1-2"

Many thanks again for looking at this!

Last edited by ibu (2020-03-14 18:47:19)

Offline

#4 2020-03-14 19:04:23

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: /boot failed to mount: unknown filesystem type 'vfat'

That's only a partial config that relies on refind autodetecting where things are. Don't do that, write it all out.

UUID= 95b17740-bb1e-4cc3-ae90-908362ec1469              /mnt             ext4            defaults     0 2

How is that rational?

Offline

Pages: 1

Board footer

Powered by FluxBB