Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: Boot has failed after hard restart

  1. #1

    Default Boot has failed after hard restart

    Hi guys,

    I work on computer with openSUSE 42.1 (I know, after all I'll upgrade the system to 42.3). When I stuck a charge of my phone to the USB port, the machine froze immediately. It sometimes happened in the past, so nothing new for me. Only hard restart helped me. But today, after that, something went wrong and I see the following warning on the black screen:

    Code:
    Boot has failed. To debug this issue add rd.shell rd.debug to the kernel command line
    I did what the command suggests and I see another message:

    Code:
    can't find command esetparams
    Do you have any idea how to solve this bug? Of course I used Google but there is no information about that. When the last message disappeared the terminal showed up. I typed journalclt but there was too much information to rewrite it.

    Benek

  2. #2

    Default Re: Boot has failed after hard restart

    I made further investigation and I copied the rdsosreport.txt: https://paste.opensuse.org/e73b1fa0

  3. #3
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,563

    Default Re: Boot has failed after hard restart

    Quote Originally Posted by Benek View Post
    I made further investigation and I copied the rdsosreport.txt: https://paste.opensuse.org/e73b1fa0
    Looks like you've got a corrupted file system...

    Code:
    [    2.960922] user systemd[1]: Starting File System Check on /dev/disk/by-uuid/45feac9e-ab14-4508-b0ae-da3d4ab896ef...
    [    3.011657] user systemd-fsck[337]: /dev/sda1 contains a file system with errors, check forced.
    ...
    ...
    [    6.023529] user systemd-fsck[337]: /dev/sda1: Inodes that were part of a corrupted orphan linked list found.
    [    6.023718] user systemd-fsck[337]: /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    [    6.023868] user systemd-fsck[337]: (i.e., without -a or -p options)
    [    6.060216] user systemd-fsck[337]: fsck failed with error code 4.
    Regards, Paul

    2x Tumbleweed (Snapshot: 20201021) KDE Plasma 5
    2x Leap 15.2 KDE Plasma 5

  4. #4

    Default Re: Boot has failed after hard restart

    What do you suggest? Is any solution or I have to install the newest version of openSUSE?

  5. #5
    Join Date
    Sep 2012
    Posts
    5,907

    Default Re: Boot has failed after hard restart

    Quote Originally Posted by Benek View Post
    What do you suggest?
    Do as error output says - run fsck on this device manually. As you have rdsosreport, you already are in initrd shell.

  6. #6
    Join Date
    Aug 2008
    Location
    Brazil
    Posts
    3,050

    Default Re: Boot has failed after hard restart

    Quote Originally Posted by Benek View Post
    When I stuck a charge of my phone to the USB port, the machine froze immediately. It sometimes happened in the past, so nothing new for me. Only hard restart helped me.
    However, this is indicative of a hardware problem that you should investigate. It seems to be power-related, like faulty usb port isolation, current leak or earthing problems (do you get a small electric shock when touching the case?) or possibly a defective USB port (I've seen a few of those).

  7. #7
    Join Date
    Aug 2008
    Location
    Brazil
    Posts
    3,050

    Default Re: Boot has failed after hard restart

    If you're on a desktop, you could try using one of the motherboard ports in the back instead of the USB port(s) in the front of the case. IME these case ports are not always of good quality, and in time stop working correctly - which is worse than not working at all, as it may damage your device or short-circuit the motherboard power circuitry that feeds the USB extension headers.

    When I have to use a motherboard port in the back, a good-quality usb extension cable is a good help.

  8. #8

    Default Re: Boot has failed after hard restart

    Quote Originally Posted by arvidjaar View Post
    Do as error output says - run fsck on this device manually.
    I will do in a few hours. The PC is in my work.

    Quote Originally Posted by brunomcl View Post
    If you're on a desktop, you could try using one of the motherboard ports in the back instead of the USB port(s) in the front of the case.
    Yes, you're right. Thanks for the advice. As I wrote before there were problems with the USBs and indeed I used the front ports. I also got a small electric shock when touching the case. If fsck helps, I will upgrade my system to 42.3 and won't use the front USB ports. Whatever happens we'll be in touch. I always leave a solution for others.

    Benek

  9. #9
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,563

    Default Re: Boot has failed after hard restart

    Additionally, it may be worth a quick look at the smartctrl data for that drive.

    Code:
    sudo smartctl -data -A /dev/sdX
    Although in this case I suspect the FS corruption was more likely due to the hard reset that was necessitated.


    Also, and I apologise if I'm telling you something that you already know, and indeed may have done.

    Prior to a hard reset it's worth trying the "Magic SysRq" key sequence to try to recover from a crash with a proper shutdown:

    Press and hold Alt + SysRq (Prt Scr), then in sequence r, e, i, s, u, b. Allow a few seconds after each key press, longer (90secs or so) after e.

    Which should, if it's successful:

    r - Release the keyboard from the X-server
    e - Shutdown processes (SIGTERM)
    i - Forcibly shutdown any remaining processes (SIGKILL)
    s - Sync the file system
    u - Unmount the file system(s)
    b - Reboot

    If the system reboots then it's worked, if not... then use the hard reset option.
    Regards, Paul

    2x Tumbleweed (Snapshot: 20201021) KDE Plasma 5
    2x Leap 15.2 KDE Plasma 5

  10. #10

    Thumbs down Re: Boot has failed after hard restart

    I made fsck manually and the program has fixed some bugs. The message disappeared but the emergency mode showed up:
    Code:
    Welcome to emergency mode! After logging in, type "journalctl -xb" to view
    system logs, "systemctl reboot" to reboot, "systemctl default" to try again
    to boot into default mode.
    Give root password for maintenance
    (or press Control-D to continue):
    Control-D, jorunalctl reboot and default don't work. Journalctl -xb prints a log and I can log in as root. I read Google again and finally I used DVD with 42.1 to make upgrade. During mounting partitions the installer tells me that cannot find a specific UUID. The installer propose me mounting a new partition as /home2. I have two additional disks in my PC mounted as /home2 and /home3 without system but before fixing I plugged out both. I see I can continue mounting disk on /home4. I don't know why it is impossible on /home. What I should to do? I want to restore the current system and make upgrade to 42.3.

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

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