During a normal cold boot, the system failed to locate the root partition by its UUID (bf913fe9-...) and dropped into emergency mode (initramfs). The emergency console displayed: “Warning: /dev/disk/by-uuid/bf913fe9-… does not exist
Generating “/run/initramfs/rdsosreport.txt”
Entering emergency mode. Exit the shell to continue.
Cannot open access to console, the root account is locked.”
Access to the maintenance shell was denied because the root account is locked (default Fedora behavior). After a simple reboot, the system started normally without any further intervention. The issue has not reoccurred so far.
No system updates (dnf upgrade) or new software installations were performed in the session prior to the failure. Only Firefox was used for browsing. No unusual system behavior was noticed beforehand.
Since the failure was transient and resolved by a reboot, the most likely cause is a race condition during boot. The kernel or initramfs may have attempted to mount the root filesystem before the NVMe/SATA disk driver or the device subsystem was fully ready. This kind of failure is sporadic and hard to reproduce, especially on modern hardware with fast boot.
The use of btrfs as the root filesystem is not directly related to the UUID error, though it could affect device detection timing.
This you can change easy when you have a sudo/wheel user.
sudo passwd root #follow the instructions
# To lock the root user again.
sudo passwd root -d
I could reproduce your error, alias when I switched fast-boot on on my older computer I just got a white cursor on the top left screen while not much happened. The computer is from 2013 and the hard-drive is a bit younger. Booting with the external disk worked. So I could enter into the bios and switch fast-boot off.
I saw your first topic in Spanish and think you should decide for the English section. You have better chances to get help because of the bigger audience here. From the topic it seams to be a duplicated request. Please consider to delete the Spanish topic.
If you have a Live USB installer, you can mount the system drive, e.g., using Gnome Disks, and then use journalctl with the —directoryoption to view the system journal. This won’t help if the root drive wasn’t detected, but is often useful for other emergency mode situations, and if you suspect a drive problem you can run tests, e.g., using Gnome Disks in the Live system.
Problem description