Fedora 39 won’t boot.
I tried using older kernels at bootup : F39 still won’t boot.
Emergency mode didn’t work either :
Cannot open access to console. The root command is locked
When I press “Enter” I get multiple error messages. The first one is
[FAILED] Failed to mount boot-efi.mount - /boot/efi
I’m currently using btrfs. Any help appreciated.
Skoubidou74
In GRUB, edit the current boot entry, remove rhgb quiet, and boot it using ctrl+x. Then use your phone to create a photo of your screen containing the failures and post it here.
I’m using a live usb drive now. How can I edit my grub entry ?
Check the status of the storage device by booting from a “Live” USB key or other linux boot drive. You can view the partitions and check the drive “health” using Gnome disks. Some history may help us understand the issue – a power failure can result in corrupted filesystems.
Other potential causes require physical inspection. If your system is a desktop with drives connected by cables you could have a cable problem (some cheap cables loose connector spring tension in the contacts over time and can fall off ). SSD’s in M.2 slots that aren’t properly secured with a screw or post can come loose.
My drive is a pretty new SATA SSD (not M.2 because it was more expensive / not NVMe because my laptop is pretty old), properly screwed. Gnome disks tells my drive is fine.
I eventually found the edit prompt on startup and removed the rhgb and quiet options.
Here is a photo of my screen with the errors.
For some reason my laptop booted after pressing enter…
?
With Disks you can try mounting each partition of the SSD to see if there are errors. I have an old Imac with SATA SSD as /dev/sdb, Yours is probably /dev/sda. If you are able mount the partitions, you can check the space and filesystem type. Here:
% df -lHT | grep '/dev/sdb'
/dev/sdb3 btrfs 120G 33G 85G 28% /
/dev/sdb3 btrfs 120G 33G 85G 28% /home
/dev/sdb2 ext4 1.1G 313M 639M 33% /boot
/dev/sdb1 hfsplus 630M 37M 593M 6% /boot/efi
Note that hfsplus is an Apple thing, most PC’s will use a Microsoft format (FAT32?).
Errors that aren’t reproducible can indicate overheating, a poor connection, unreliable RAM, or power system failure. Check your cooling fan and fins for dust (you can use “canned air” to blow off dust. Check the system board for bulging capacitors.
Auto parts stores sell “contact enhancer” due the number cables connecting all the computers in modern cars (a friendly auto mechanic may have some – I would apply it to the SSD connector). With older computers it is a good idea to run memtest86+ overnight for several nights.
There have been times when upgrading that I encountered an abnormally long boot time. Yours shows the system waiting for the plymouth-quit-wait.service/start to complete.
I am betting that future boots will not take the abnormally long time since for me that apparent hang seemed to be related to the system performing background configs with the update that was just performed, and future boots were normal.
Well, when I first managed to start Fedora, I upgraded the system. It didn’t work any better first, but I edited grub once again and deleted the 2 options. Fedora started slowly first, but now my PC restarts properly.
Thanks to all of you for your help. I don’t know what happened, but F39 is fine and running.
Skoubidou