Page 1 of 3 123 LastLast
Results 1 to 10 of 23

Thread: Reboot after update ends in "Emergency mode" - Logs of no help...

  1. #1

    Exclamation Reboot after update ends in "Emergency mode" - Logs of no help...

    Hi again!

    Have a TW 64bit install (plain vanilla with multimedia) doing fine for more than 2 years, was updated 2-3 weeks ago without problems, but after yesterdays "zypper dup" the reboot ends always in "emergency mode" (after seeing the arrows hunt on the infinity symbol, normally the mouse cursor arrow would appear next and then the login screen, so apparently the graphical system crashes).

    What I have done so far:

    - Tried to boot in GRUB2 the older kernel and/or recovery mode of both kernels shown. Always ends in "emergency mode".

    - Updated a second TW install on the same computer (different HDD), worked fine, so no hardware issue, apparently. - Mounted the HDD with the problematic install on another TW computer, without any problems I could access all partitions, so apparently no problem with the HDD (dual-boot form this HDD with Win7 also working fine).

    - Screened the log (systemctl ...., as proposed at the emergency promp), ends with lots of "start-up result is RESULT", but no apparent errors. . "journalctl -b | grep -i "fail" or "error" finds no hint in my opinion, as "fail" is only for ASPM and for "usr/bin/setfont" (exit status 71) and "error" for ASPM, PIO_UNIMAPPCLR: Input/output error" and for setting fonts.

    I have no idea how to debug this, where to start...
    Kind regards

    raspu

  2. #2

    Default Re: Reboot after update ends in "Emergency mode" - Logs of no help...

    Hi,

    I usually encounter the emergency mode when something's wrong with mounts. Do you have any network dependent mounts in /etc/fstab? Try to mount only the devices required by the system at boot time and then mount the rest manually, see if that works. Are you using LVM? Maybe something's wrong there?

    Regards

  3. #3

    Default Re: Reboot after update ends in "Emergency mode" - Logs of no help...

    Just checked (again): No, nothing in fstab besides swap, / and /home...

    No LVM in use here...

    Is there any way to read the systemd logs (/var/lg/journal....) when the HDD is mounted on a different computer?
    Kind regards

    raspu

  4. #4

    Default Re: Reboot after update ends in "Emergency mode" - Logs of no help...

    PS: Fogot to mention: / is EXT4, /home is XFS... So no BTRFS involved here.
    Kind regards

    raspu

  5. #5
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    18,153
    Blog Entries
    14

    Default Re: Reboot after update ends in "Emergency mode" - Logs of no help...

    The system always "says" something when entering emergency mode. Like "one or more filesystems could not be mounted" or something like that. Can you show that message?
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  6. #6

    Default Re: Reboot after update ends in "Emergency mode" - Logs of no help...

    Hi!

    To my total surprise there is no such error message:

    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):

    I have real problems to extract some info from the booted system in such a "vegetative state"... Could take a photo, but how to insert here? Have no pic hoster currently in use.

    PS: If I try to boot to default mode, the infinity symbol hunting the arrows appear, after LONG time, the arrows dissapear, the infinity symbol changes colour from white to blue and "Tumbleweed" appears underneath the infinity symbol. I let it sit there for hours but nothing will happen in this state.

    I can't switch to any text console, btw...

    Thanks for reading...
    Kind regards

    raspu

  7. #7
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    18,153
    Blog Entries
    14

    Default Re: Reboot after update ends in "Emergency mode" - Logs of no help...

    Quote Originally Posted by suse_rasputin View Post
    Hi!

    To my total surprise there is no such error message. I have real problems to extract some info from the booted system in such a "vegetative state"... Could take a photo, but how to insert here? Have no pic hoster currently in use.

    Thanks for reading...
    paste.opensuse.org , no need to login, the top right has an Image button, click it, upload your image, and post the link here.
    A thing to try if possible: connect the drive to a different SATA port. The drive itself seems OK, since mounting on another machine works.
    Another option to try, is to run YaST's bootloader module in single user mode, if you can login / access the system that way.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  8. #8

    Default Re: Reboot after update ends in "Emergency mode" - Logs of no help...

    Quote Originally Posted by Knurpht View Post
    paste.opensuse.org , no need to login, the top right has an Image button, click it, upload your image, and post the link here.
    Works! http://paste.opensuse.org/73306d10
    Quote Originally Posted by Knurpht View Post
    A thing to try if possible: connect the drive to a different SATA port. The drive itself seems OK, since mounting on another machine works. Another option to try, is to run YaST's bootloader module in single user mode, if you can login / access the system that way.
    I tried different SATA adaptors and ports (eSATA, USB,...) makes no difference. The HDD (WD red 1 TB 2.5") is only 2.5 years old and only booted from time to time. SMART throws no errors or signs of deprecation
    Kind regards

    raspu

  9. #9

    Default Re: Reboot after update ends in "Emergency mode" - Logs of no help...

    https://www.cyberciti.biz/faq/grub-b...gle-user-mode/ ...would this "Append "S" to the kernel parameters" work with TW and Grub2 to enter single user mode?
    Kind regards

    raspu

  10. #10
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    18,153
    Blog Entries
    14

    Default Re: Reboot after update ends in "Emergency mode" - Logs of no help...

    Quote Originally Posted by suse_rasputin View Post
    https://www.cyberciti.biz/faq/grub-b...gle-user-mode/ ...would this "Append "S" to the kernel parameters" work with TW and Grub2 to enter single user mode?
    Yes. You can also use " 1 " the number. If you don't manage that way, it can still be done from an install medium
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •