On Thu, 09 May 2019 21:08:36 -0400 Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote: > Samuel Sieb writes: > > > On 5/9/19 3:50 PM, Ranjan Maitra wrote: > >> After a three successful upgrades to F30 from F29 under my belt, a cocky me > >> has been floored. Everything went through fine (or so it seemed) using dnf > >> upgrade --releasever 30 but I ended with, upon reboot: > >> > >> You are in emergency mode. After logging in, type "journalctl -xb" to > >> view system logs, "systemctl reboot" to reboot, "systemctl default" or > >> "exit" to boot into default mode. > >> Give root password for maintenance. > >> (or press Control-D to continue): > >> > >> One problem is that I do not have a root password. I have actually gone in > >> using a livecd and the devices (1 ext4 and 2 xfs) appear to be clean. > > > > Using the live boot, you can chroot to the installed system and set the root > > password. > > Also missing from this report is the actual reason for getting dropped into > emergency mode. > > Emergency mode is not the issue here. The real issue is what caused the > emergency mode. It's unlikely that anyone will be able to help you until you > determine, from boot messages, or whatnot, the reason the system boot fails. > Thanks, I get: a stop process (?) is running on some device with a huge name. It runs for 1m 30s and then drops into this message. There is nothing untoward before this. I will try and see if chrooting can be done using the livecd. Thanks, Ranjan _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
