Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

The attempt to mount a file system with type vfat at /boot/efi failed.

Ask for help with issues regarding the Installations of the Debian O/S.
Post Reply
Message
Author
imwacc0
Posts: 7
Joined: 2021-01-22 14:42

The attempt to mount a file system with type vfat at /boot/efi failed.

#1 Post by imwacc0 »

So, I have my disks set up.
sda: 1 EFI, 2 RAID 0 for ROOT, 3 LVM for HOME & SWAP
sdb: 1 RAID 0 for ROOT, 2 LVM for HOME & SWAP

But I keep getting:

Code: Select all

The attempt to mount a file system with type vfat in SCSI1 (0,0,0), partition #1 (sda) at /boot/efi failed.
I've done quite a few instals of Linux, and way too many Windblows. This one I don't know, why is Debian using VFAT? I'll admit I don't know much about UEFI.

Anyone have a clue as to how to do this instal?



P.S. Yes, I know about RAID 0. Not what I'm asking about. Logs and Forum Server will be on home and backed up. I need the speed for TeamSpeak.

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 462 times

Re: The attempt to mount a file system with type vfat at /boot/efi failed.

#2 Post by sunrat »

ESP is common to all systems which use UEFI including Windows, hence VFAT.
Compare the UUID of ESP shown in /etc/fstab with the one in output of

Code: Select all

lsblk -f
Not sure if that will show your issue but is a good place to start with boot mount fails.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: The attempt to mount a file system with type vfat at /boot/efi failed.

#3 Post by p.H »

I guess you get this error message at installation. AFAIK lsblk is not available in the installer.
The EFI partition requires FAT because it is read by the UEFI firmware for booting.
Was the EFI partition created before the installation (how ?) or by the installer ?
You can check for fat errors in the installer logs in console tty4 (Alt+F4, +Ctrl from graphic installer) or via the shell in console tty2 and tty3 in /var/log/syslog

Code: Select all

tail -n 100 /var/log/syslog | more
or the kernel logs with dmesg

Code: Select all

dmesg | grep -ie fat -e sda1
You can also check that the partition contains a FAT filesystem with blkid

Code: Select all

blkid /dev/sda1
You can also try to mount the partition by hand and see what happens.

Code: Select all

mount -t vfat /dev/sda1/target/boot/efi
dmesg | tail

imwacc0
Posts: 7
Joined: 2021-01-22 14:42

Re: The attempt to mount a file system with type vfat at /boot/efi failed.

#4 Post by imwacc0 »

New info, I did not know Alt+F4, +Ctrl worked in install. I'm going to try to type out the error, but I'm dyslexic and may not come out 100% right.

Code: Select all

EXT4-fs (md0) mounted filesystem with ordered data mode. Opts: errors=remount-ro
However, I don't have a prompt. I can read error messages, but no input.

p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: The attempt to mount a file system with type vfat at /boot/efi failed.

#5 Post by p.H »

This is not an error message, only the indication that the ext4 filesystem in /dev/md0 (RAID array) was successfully mounted. "errors=remount-ro" is a standard mount option for the root filesystem, meaning to remount read-only on error.
Nothing to do with FAT or the EFI partition (sda1).

You have a prompt in tty2 or tty3.

superzerg
Posts: 1
Joined: 2023-11-14 18:23

Re: The attempt to mount a file system with type vfat at /boot/efi failed.

#6 Post by superzerg »

Hello, I just got the same error during a new Debian installation over Windows.
The problem was that I was trying to reuse the existing EFI partition from Windows (even after reformatting it).
Deleting the existing EFI partion and recreating one from scratch solved the problem.

Post Reply