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

Thread: Can only boot to rescue mode

  1. #1

    Post Can only boot to rescue mode

    Let me start off by saying that I normally do not post on forums in search of help. I'd rather waste hours of my own time than that of someone else's. However, I've exhausted all of my resources with this recent issue and my Google-fu has let me down. I will say up front that I have learned a major lesson from this in terms of keeping a backup of the root system. I also learned while reading around that snapper works with ext4 (oh how I wish I would have made a snapshot of my system). I really hope that I don't have to reformat since I will lose many configurations in the main system and it will probably take me at least a week to reinstall software and reconfigure anything not saved in /home (but that will be the price I pay for my incompetence and oversight). So with that said, let me begin by describing the problem and providing as much information as I can.

    The problem started this past Saturday, 9/29, after a `zypper dup`. Not encountering any blatantly obvious issues, I rebooted as I usually do after updating. The update upgraded my kernel to 4.18.8 and all looked like things were fine, until the boot just sorta stopped... as in it didn't reach either the KDE login screen or get thrown to emergency mode. I can't access any of the tty environments to login either. Instead I just have the boot output showing [ OK ] Started Update system wide CA certificates as the last successful output. Reviewing the prior output, I can see that the root filesystem was mounted successfully and then my /home partition on a separate drive was mounted after it was unencrypted. I originally noticed warnings for the wicked service failing to start and my NFS shares failed to mount (for obvious reasons), however I believe I've fixed this since. Using Alt + F1, I can see the following:
    • a few mce [Hardware Error] entries (I've had these from before and I believe the CPU is correcting them before boot)
    • an entry for [FAILED] Failed to start Setup Virtual Console (I think this is related to /etc/vconsole.conf)
    • an entry for Starting Show Plymouth Boot Screen...


    So not having any clue where to start, I started with the basics. First, I tried to boot into the recovery/fallback kernel by going into the Advanced options in grub. I also tried the other kernel options that were available to me and their respective recovery/fallback option (4.18.5 and 4.17.9). I even tried editing the grub for each boot and removing extra kernel options and enabling debug. I had absolutely no luck with any of these things, so my next thought was to make myself a new live USB and try an upgrade. After installing some new files, removing some obsolete, and rebooting, I returned to the same scenario. At this point I let the system sit for a while, I wondered if it was just taking a really long time for some unknown reason. Needless to say, that didn't help.

    Next thing on the list was repair the bootloader and check the filesystem. I booted off the live USB again, ran fsck on the system drive, then mounted the system, chrooted in and rebuilt grub with `grub2-mkconfig -o /boot/grub2/grub.cfg` and `grub2-install /dev/sda`. File system came back fine, and the grub rebuild didn't improve my situation. So at this point I decided to boot into the main system and pass the rescue kernel option to force my way into rescue mode natively. I started poking around in the systemd journals for any error I could find and started researching each and every possible one.

    Here's the output of `journalctl -xrb -1` for anyone who wants to take the time to read through it.
    https://pastebin.com/jd62ayEG

    Some things I noticed looking through systemd logs:
    • NVRM entries related to the Nvidia probe routine (I've tried removing and reinstalling the Nvidia proprietary drivers as well as blacklisting nouveau and using the nomodeset kernel option)
    • /usr/bin/loadkeys failed with exit status 1 (I believe this is related to the console keyboard layout)
    • Invalid rule /etc/udev/rules.d/50-brother-brscan4-libsane-type1.rules:9: unknown key 'SYSFS{idVendor}' (Related to my Brother printer, I think this is safe to ignore)
    • EDAC sbridge: Couldn't find mci handler ... ECC is disabled (I've had this since I started using linux, appears to be related to my chipset)
    • Process 236 (haveged) of user 0 dumped core (this seems to be related to system entropy and I assume the core dumps since the system is hanging at the end and not proceeding to a login)


    And here is some other various information that may or may not be useful.

    The output of `mkinitrd`:
    https://pastebin.com/cSqzFzFH

    Zypper history from 9/29:
    https://pastebin.com/wKSrVk1K

    System:
    • Tumbleweed x86_64
    • i7 5820K
    • Geforce GTX 1050 2GB
    • 16GB DDR4


    Please let me know if there is anything else I can provide and thanks ahead of time for any assistance. My fate is in the communities' hands.

  2. #2
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    700

    Default Re: Can only boot to rescue mode

    If you have Plymouth installed, try removing it:
    https://bugzilla.opensuse.org/show_bug.cgi?id=1090451
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2) & 42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,others on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,GT218 &&&&

  3. #3
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,474

    Default Re: Can only boot to rescue mode

    similar experience on laptop with Tumbleweed 32bit KDE install, ext4 disk

    in rescue mode the command

    fsck

    was run, this found errors and ask if they should be corrected

    after accepting, on reboot all was back to normal

    hth

    for disk identification command

    df

    was used to get boot disk details (e.g. /dev/sda2)

  4. #4

    Default Re: Can only boot to rescue mode

    Quote Originally Posted by mrmazda View Post
    If you have Plymouth installed, try removing it:
    https://bugzilla.opensuse.org/show_bug.cgi?id=1090451
    According to bug 1047225, I added omit_dracutmodules+="plymouth" to a file in /etc/dracut.conf.d/ and rebuilt the initramfs. Tried booting with splash=silent for all three kernels with no luck. This did resolve all of the warnings/errors I saw related to nouveau in the mkinitrd output and the NVRM entries related to Nvidia in my systemd logs, so that's a plus.

    Quote Originally Posted by keellambert View Post
    similar experience on laptop with Tumbleweed 32bit KDE install, ext4 disk

    in rescue mode the command

    fsck

    was run, this found errors and ask if they should be corrected

    after accepting, on reboot all was back to normal

    hth

    for disk identification command

    df

    was used to get boot disk details (e.g. /dev/sda2)
    Tried running fsck from a live USB again. `fsck /dev/sda1` clean, 373828/3637248 files, 4904928/14525440 blocks


    Thanks for the suggestions. I'm willing to try anything to get my system back up and running.

  5. #5
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,474

    Default Re: Can only boot to rescue mode

    Next suggestion

    Do an upgrade from the original installation DVD or most recent DVD

    When asked for deletion of existing repositories change as required to enable or disable
    (try to replicate what was there before)

    On the next menu accept all proposed new repositories
    (this most probably will mean some duplication which can be corrected later)

    At the accept menu have a look at all proposed changes and alter if necessary
    (this should lead to a minimal update, dependent upon last status)

    Then accept and sit back and wait for completion and hope a reboot is successful

    If the installed os is not recognised by the updater then there is not must hope of recovery

    cheers

  6. #6
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    700

    Default Re: Can only boot to rescue mode

    After removing the Nvidia proprietary driver, did you try rebooting, with nomodeset absent from kernel cmdline, and with rebuilt initrds that lack proprietary NVidia specifics, before reinstalling the proprietary driver?
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2) & 42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,others on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,GT218 &&&&

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

    Default Re: Can only boot to rescue mode

    Quote Originally Posted by mrmazda View Post
    If you have Plymouth installed, try removing it:
    https://bugzilla.opensuse.org/show_bug.cgi?id=1090451
    Felix, please stop propagating this as a solution. The forums already have a couple of threads where a patch was provided.

    @OP: Welcome to these forums,
    There already is a patch to solve the vconsole error message:
    - Create a file systemd-vconsole-setup-race-fix.patch in your homedir with the following content:
    Code:
    diff --git a/modules.d/98dracut-systemd/dracut-cmdline-ask.service b/modules.d/98dracut-systemd/dracut-cmdline-ask.service
    index 1685479a..3d233143 100644
    --- a/modules.d/98dracut-systemd/dracut-cmdline-ask.service
    +++ b/modules.d/98dracut-systemd/dracut-cmdline-ask.service
    @@ -12,6 +12,8 @@ Description=dracut ask for additional cmdline parameters
     DefaultDependencies=no
     Before=dracut-cmdline.service
     After=systemd-journald.socket
    +After=systemd-vconsole-setup.service
    +Requires=systemd-vconsole-setup.service
     Wants=systemd-journald.socket
     ConditionPathExists=/usr/lib/initrd-release
     ConditionKernelCommandLine=|rd.cmdline=ask
    and save it in your homedir
    Next do
    Code:
    su
    cd /usr/lib/dracut
    patch -p1 < /home/YOUR_USERNAME/systemd-vconsole-setup-race-fix.patch
    Reboot and the message will be gone. An upstream patch is supposed to be on the way, haven't seen it yet
    ° 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
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    700

    Default Re: Can only boot to rescue mode

    Have you tried cleaning up the kernel cmdline:
    Code:
    BOOT_IMAGE=/boot/vmlinuz-4.18.8-1-default root=UUID=e47d1d02-9700-49c4-a118-0985296aa51d nomodeset nosplash quiet showopts intel_iommu=on iommu=pt
    1-showopts is a noop unless using Gfxboot and Grub Legacy
    2-why are intel_iommu=on and iommu=pt included? My Haswell doesn't need them. kernel-parameters.txt doesn't list them.
    3-"" is the default splash. IOW, if you wish no splash, splash needs no cmdline mention. Splash is also absent from kernel-parameters.txt.
    4-Don't forget, nomodeset blocks use of all competent FOSS X drivers (ie: modesetting & nouveau; if booting without proprietary driver installed).
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2) & 42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,others on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,GT218 &&&&

  9. #9
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    700

    Default Re: Can only boot to rescue mode

    Quote Originally Posted by Knurpht View Post
    a patch was provided.
    Does that equate to on the mirrors in oss, non-oss or updates?
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2) & 42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,others on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,GT218 &&&&

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

    Default Re: Can only boot to rescue mode

    Quote Originally Posted by mrmazda View Post
    Does that equate to on the mirrors in oss, non-oss or updates?
    If such was the case, posting the patch here would be useless. I already wrote that upstream needs to incorporate the patch.
    But my point was that uninstalling plymouth is not a solution, not even a workaround.
    ° 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
  •