Re: Locked in emergency mode

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

 



Thanks, Roger! You can find below the output of the two commands.

Paul
-----------------------------------
13.843s dnf-makecache.service
 4.961s NetworkManager-wait-online.service
 2.047s systemd-udev-settle.service
 1.506s akmods.service
 1.257s firewalld.service
  996ms sssd.service
  994ms initrd-switch-root.service
  947ms plymouth-read-write.service
  884ms lvm2-monitor.service
  876ms systemd-logind.service
  849ms dracut-initqueue.service
  771ms udisks2.service
  599ms vboxdrv.service
  551ms accounts-daemon.service
  451ms systemd-udevd.service
  402ms ModemManager.service
  399ms polkit.service
  397ms abrtd.service
  297ms NetworkManager.service
  296ms systemd-fsck@dev-mapper-fedora_localhost\x2d\x2dlive\x2dhome.service
  293ms upower.service
  257ms systemd-journal-flush.service
  246ms systemd-journald.service
  219ms lvm2-pvscan@8:2.service
  200ms gssproxy.service
  152ms chronyd.service
  136ms initrd-parse-etc.service
  126ms user@1000.service
  110ms avahi-daemon.service
   92ms systemd-udev-trigger.service
   80ms systemd-vconsole-setup.service
   75ms dbus-broker.service
   64ms lm_sensors.service
   55ms systemd-tmpfiles-setup-dev.service
   53ms auditd.service
   51ms cups.service
   50ms boot.mount
   46ms rtkit-daemon.service
   45ms dmraid-activation.service
   45ms switcheroo-control.service
   44ms systemd-tmpfiles-setup.service
   43ms dracut-cmdline.service
   34ms dev-mapper-fedora_localhost\x2d\x2dlive\x2dswap.swap
   34ms systemd-fsck@dev-disk-by\x2duuid-e0d64aea\x2d45b9\x2d4662\x2d9a09\x2d50c1c1568713.service
   34ms var-lib-nfs-rpc_pipefs.mount
   31ms systemd-tmpfiles-clean.service
   30ms vboxweb-service.service
   28ms import-state.service
   26ms home.mount
   24ms nfs-convert.service
   24ms systemd-random-seed.service
   24ms dracut-pre-pivot.service
   23ms systemd-sysctl.service
   22ms plymouth-switch-root.service
   21ms sssd-kcm.service
   19ms user-runtime-dir@1000.service
   15ms systemd-fsck-root.service
   15ms initrd-cleanup.service
   14ms lightdm.service
   13ms dracut-pre-udev.service
   13ms plymouth-start.service
   13ms dev-hugepages.mount
   13ms vboxautostart-service.service
   13ms vboxballoonctrl-service.service
   13ms sys-fs-fuse-connections.mount
   12ms dev-mqueue.mount
   12ms sys-kernel-debug.mount
   12ms livesys.service
   12ms kmod-static-nodes.service
   11ms systemd-update-utmp.service
   10ms systemd-modules-load.service
   10ms systemd-update-utmp-runlevel.service
    9ms sysroot.mount
    9ms systemd-user-sessions.service
    9ms systemd-remount-fs.service
    9ms livesys-late.service
    9ms rpc-statd-notify.service
    4ms initrd-udevadm-cleanup-db.service
    3ms dracut-shutdown.service
    2ms tmp.mount
    1ms plymouth-quit-wait.service
    1ms sys-kernel-config.mount
   32us iscsi-shutdown.service
-----------------------------------
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

home.mount +26ms
└─local-fs-pre.target @2.989s
  └─lvm2-monitor.service @807ms +884ms
    └─dm-event.socket @799ms
      └─system.slice
        └─-.slice



On Mon, Apr 20, 2020 at 3:30 PM Roger Heflin <rogerheflin@xxxxxxxxx> wrote:
>
> So home mounted eventually.
>
> Run these 2 commands and return the output:
>
>  systemd-analyze blame
> systemd-analyze critical-chain home.mount
>
> if the 2nd one returns nothing do this:
> systemctl list-units | grep home
> and use the name of the .mount unit it reports that home is using.
>
> On Mon, Apr 20, 2020 at 9:12 AM Paul Smith <phhs80@xxxxxxxxx> wrote:
> >
> > Thanks, Roger. After having edited fstab according to your guidelines,
> > I issued the command
> >
> > # exit
> >
> > on the root prompt and I was led to my usual graphical login panel.
> >
> > I did the following after having logged in:
> >
> > # mount /home
> > mount: /home: /dev/mapper/fedora_localhost--live-home already mounted on /home.
> > #
> >
> > Paul
> >
> > On Mon, Apr 20, 2020 at 2:56 PM Roger Heflin <rogerheflin@xxxxxxxxx> wrote:
> > >
> > > Edit your fstab and on the entry for /home were it says defaults
> > > change it to "defaults,nofail" and where it says "1 2" at then end
> > > change that to "0 0"   I am not sure if the last 2 entries are still
> > > used quite the same way but "0 0" will stop anything else looking for
> > > /home.
> > >
> > > That should get you out of emergency mode.  But there is something
> > > wrong with the home mount.  Once in do a mount /home  and see what the
> > > error is and see if you can figure out why it is failing.
> > >
> > > On Mon, Apr 20, 2020 at 8:47 AM Paul Smith <phhs80@xxxxxxxxx> wrote:
> > > >
> > > > Thanks again, Roger. Got them! Please, see them at:
> > > >
> > > > https://drive.google.com/drive/folders/158qtJIgB6WiEbnLu4oFShbSY1paWafj8?usp=sharing
> > > >
> > > > Thanks,
> > > >
> > > > Paul
> > > >
> > > > On Mon, Apr 20, 2020 at 2:26 PM Roger Heflin <rogerheflin@xxxxxxxxx> wrote:
> > > > >
> > > > > Hit shift-pageup/pagedown it will scroll that screen, it should scroll
> > > > > back 100's of lines or more.  Take pictures each pageup.
> > > > >
> > > > > On Mon, Apr 20, 2020 at 8:20 AM Paul Smith <phhs80@xxxxxxxxx> wrote:
> > > > > >
> > > > > > Thanks, Roger. But how can I get the error messages?
> > > > > >
> > > > > > Paul
> > > > > >
> > > > > > On Mon, Apr 20, 2020 at 2:13 PM Roger Heflin <rogerheflin@xxxxxxxxx> wrote:
> > > > > > >
> > > > > > > A screen shot of the fstab does not tell anyone anything as we have no
> > > > > > > way to know what is going on.
> > > > > > >
> > > > > > > Did you follow the instructions to use shift-pageup/down to page
> > > > > > > through the error messages (above the emergency mode prompt) and and
> > > > > > > see what it indicates is going wrong?   It is probably going to tell
> > > > > > > you something that will indicate where to look.
> > > > > > >
> > > > > > > On Mon, Apr 20, 2020 at 7:34 AM Paul Smith <phhs80@xxxxxxxxx> wrote:
> > > > > > > >
> > > > > > > > Please, see my fstab photo:
> > > > > > > >
> > > > > > > > https://drive.google.com/file/d/1fWv2h-CLt2ecoE2m5aCpAOsUr2aEhuvh/view?usp=sharing
> > > > > > > >
> > > > > > > > Paul
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Apr 20, 2020 at 1:22 PM Paul Smith <phhs80@xxxxxxxxx> wrote:
> > > > > > > > >
> > > > > > > > > Thanks, Roger and Ed. I did not touch fstab at all. It may have been
> > > > > > > > > VirtualBox by itself.
> > > > > > > > >
> > > > > > > > > I did enter my root password. And now, what should I do next?
> > > > > > > > >
> > > > > > > > > Thanks, Paul
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Mon, Apr 20, 2020 at 1:09 PM Roger Heflin <rogerheflin@xxxxxxxxx> wrote:
> > > > > > > > > >
> > > > > > > > > > You have to type your password and then figure out what is going wrong.
> > > > > > > > > >
> > > > > > > > > > Any number of things can be messed up.    Often if one adds a fstab
> > > > > > > > > > entry and does it wrong systemd will drop you to emergency mode.
> > > > > > > > > > Mountpoint mising, path to device wrong.   If you did mess with fstab
> > > > > > > > > > recently then add ",nofail" on the entries that aren't directly
> > > > > > > > > > related to the OS and that will at least get it up and on the network.
> > > > > > > > > >
> > > > > > > > > > You should read the screen, and use shift-pageup/shift-pagedown to
> > > > > > > > > > carefully go back and read the boot output and maybe it will tell you.
> > > > > > > > > >   If you have doubt on what your are reading then take photos of it.
> > > > > > > > > >
> > > > > > > > > > On Mon, Apr 20, 2020 at 6:24 AM 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?
> > > > > > > > > > >
> > > > > > > > > > > Thanks in advance,
> > > > > > > > > > >
> > > > > > > > > > > Paul
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > > 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
> > > > > > _______________________________________________
> > > > > > 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
> > _______________________________________________
> > 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