Vfat issues on Fedora 43

Ask Fedora
1

L.S.,

lately my Fedora 43 is playing up. Sometimes it won’t boot. Examing the logs, it complains about 2 things:

  1. it can’t find the zram (and that is correct, I do not have virtual memory as the system is installed with enogh on its own:-)
  2. it complains that it can’t load /boot/efi as vfat is an unknown filesystem type (and before there is a warning about fuse.
    Funny thing is Switching of the computer and booting it up (again) usually means that after 2 or 3 times trying, it comes through…

The bootmenu (do not know how capture it exactly) contains at the top 3 similar Fedora 43 boot options (defaulting to the first, and then followed by some Fedora 42 and even an ancient 35 (which could go).

kenel options that are passed to the 43 version in grub.cfg are

set kernelopts="root=UUID=d2c5089b-1c00-416e-8fd7-a7d0a96dda43 ro rhgb quiet "

and the kernel itself is : 6.19.12-200.fc43.x86_64. (installed April 12th)

with previous kernels (6.18.9 and 6.18.12) we never observed this one.

For the rest, there are 2 separate / partitions on separate disks (so I can always boot into the other system if issues occur with one disk or / partition (or issues occur after an upgrade

/dev/sda1 2048 8390655 8388608 4G EFI System
/dev/sda2 8390656 142608383 134217728 64G Linux filesystem (root voor fedora 42)
/dev/sda3 142608384 276826111 134217728 64G Linux root (x86-64) (rootfor Fedora 43)
/dev/sda4 276826112 976773119 699947008 333.8G Linux filesystem

Note that besides the linux entries there are no other entires in the boot menu (i.e. no windows..)

Any suggestions?

Regards

Frans

2

Could you show the actual lines from the logs?

3

Maybe a next time when redirecting the journactl when it fails..

right now with the system booted, journalctl -b shows me the boot from 11:04 (which went OK), journal ctl -b -1 shows me the boot from april 17th.

I.e seemingly the failed boot from 10:45 on the 20th is not stored..

If it happens again I’ll try to see whether i can redirect the journalctl -b output to a file so we can view it after boot…

If someone knows how to do this when in the emergency mode, appreciated, could save me some time trying to find the command (and not having a working machine at hand to look it up:-)

1 Like
4

This sounds like Fedora’s normal number of retained kernel versions (retained in case there is a regression in a newer version). The last entry is probably the rescue kernel, which was generated when you initially installed the machine wit F35. See Update rescue kernel for how to update this.

But I don’t think your issues are related to these kernels, I only wanted to provide an explanation of what you are seeing.