Re: Locked in emergency mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thank you very much indeed, Roger! Without your help, I would have not
fixed the problem.

I did remove both the nofail than the "0 0", and everything seems to
be working fine! I have already rebooted and no emergency mode
appeared.

Paul

On Mon, Apr 20, 2020 at 9:38 PM Roger Heflin <rogerheflin@xxxxxxxxx> wrote:
>
> remove the ,nofail and see if it goes to emergency mode still.
>
> If it does then remove these from the grub file
> rd.lvm.lv=fedora_localhost-live/root
> rd.lvm.lv=fedora_localhost-live/swap
>
> And add this in its place:
> rd.lvm.vg=fedora_localhost-live
>
> The above 2 options indicate that only those 2 lv are being turned on
> early on, but not home.   I just turn on the entire vg and then
> anything in that vg is available to be used without having to
> explicitly list each one, it is easier to deal with than listing each
> and every lv which is what anaconda does by default.  You could also
> add rd.lvm.lv=fedora_localhost-live/home
>
> If home tries to mount early on it will fail, but once all vg are
> turned on later in the boot it would then work. ,nofail would allow it
> to continue on and try later, otherwise it hangs for 90 seconds and
> fails and sends you to emergency mode.
>
> You could leave ,nofail on it, my practice is to get the machine up
> and on the network and avoid any emergency mode so anything not
> critical to boot I add ,nofail, the disadvantage is when you login you
> have to realize the mount is missing.
>
> On Mon, Apr 20, 2020 at 2:54 PM Paul Smith <phhs80@xxxxxxxxx> wrote:
> >
> > Thanks, Stan. After having run
> >
> > fsck /dev/mapper/fedora_localhost--live-home
> >
> > within emergency mode and rebooted, the problem seems to be resolved.
> >
> > Paul
> >
> > On Mon, Apr 20, 2020 at 7:28 PM stan via users
> > <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > >
> > > On Mon, 20 Apr 2020 12:23:35 +0100
> > > Paul Smith <phhs80@xxxxxxxxx> wrote:
> > >
> > > > Dear All,
> > > >
> > > > This morning, I tried to run VirtualBox, but it did not start. Then I
> > > > tried to do a reboot and while booting, I got into emergency mode. I
> > > > typed my root password and issued the command
> > > >
> > > > systemctl reboot
> > > >
> > > > It reboots, but again I got locked into emergency mode.
> > > >
> > > > How can I overcome this?
> > >
> > > What skills do you have?  Are you comfortable with examining logs,
> > > troubleshooting, editing a boot line, etc?  There can be many reasons
> > > for this to happen, so a person has to play detective to find out why
> > > and fix it. There are limited tools available at the emergency prompt.
> > > You can run
> > > ls /bin
> > > to see them.  If you have a live cd or usb  available, you can boot
> > > into it and mount the installed system, and do your forensic
> > > investigation from a more complete environment.
> > >
> > > What happened in the last hours that you used your system?  Did anything
> > > out of the usual occur?  Have you run the exact same command
> > > successfully in the past?  Is it possible there was a hardware error?
> > > _______________________________________________
> > > 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
> > _______________________________________________
> > 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
> _______________________________________________
> 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
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux