On Sun, 16 Jan 2022 21:07:29 -0500 Fulko Hew <fulko.hew@xxxxxxxxx> wrote: > I decided to log out and log back in to my X11 based KDE session just > now, and I saw that 'Discover' was telling me I had updates available. > So I said 'go ahead'. > Eventually, it said I needed to reboot, so I did. > After 4 (or 5) reboots that the machine drove itself through, > the last reboot failed to start up to a GUI session. Suspicious that this is not deterministic. It should either fail identically every time or restart every time (in my opinion). > As a matter of fact, it dropped me down and told me it needed to > enter an emergency boot > and asked for my root password. > The message also told me to look at 'journalctl -xb' > After a few thousand lines of info, I saw nothing of significance > other than it hadn't finished. You could try journalctl -rxb so that the last messages are presented first. It is likely that that is where the error will be. > The other suggestion was 'systemctl default'. > That resulted in the following: > > Failed to mount /boot/efi > Dependency failed for Local File System > Dependency failed for Mark the need to relabel after reboot > Failed to mount RPC File System > Dependency failed for rpc-pipefs.target > Dependency failed for RPC security service for NFS client and server > Failed to start Load Kernel Modules > Failed to mount Arbitrary Executable File Formats File System > Failed to mount Arbitrary Executable File Formats File System > Failed to mount Arbitrary Executable File Formats File System > Failed to mount Arbitrary Executable File Formats File System > Failed to mount Arbitrary Executable File Formats File System > Failed to start Set Up Additional Binary Formats > > ... and then nothing. I had to cold start It seems like a hardware error to me from the symptoms. How can the kernel not mount /boot/efi unless the drive has either power issues or seek errors / bad sectors. This is really basic. > and that brings me back to the same issues. > Trying to reboot a previous kernel doesn't even result in any boot > messages. > > I now have a 'non-working' machine. > Suggestions are welcome (and needed)! Long shots. It might be software, but it could be just a coincidence that it chose this time for a hardware error to expose itself. Do you have a list of what was updated? It would be good to see if there are any updates that might have caused this to happen via software. I'm not sure what would stop /boot/efi from being mounted. Did you power down completely at any point? That will allow components to lose any retained state. You could, while completely powered down, try reseating internal components, especially drive connectors. If you can reach the BIOS menu, look at the power supply numbers. Are they at or near spec? Can you boot a livecd / usb so you can do checks of the drives to see if they are still functioning properly, maybe a smartctl (smartctl -a /dev/[drive designation])? If a live image boots and runs, it will indicate that your memory is (probably) not the issue as well. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
