Results 1 to 9 of 9

Thread: Cannot boot, Cannot login to recovery (where it says control-d)

  1. #1

    Default Cannot boot, Cannot login to recovery (where it says control-d)

    hi,

    I am pretty sure its not hardware related, as I can run a live iso, (and am posting now from it ) and can mount and view all drives and contents.

    I am using ssd as sda boot. I have 175g free space on /

    I have not performed updates recently, it has been booting normally for a the past few days. now it boots to a green screen with 3 square dots. I press escape to see the console.

    I cannot login to where it says to enter root password, it locks up at that point, will not accept any keystrokes, tried ctrl-d and waiting a few minutes- nothing, rebooted and tried my root password, and waiting, nothing.

    I found a guide to help troubleshoot boot issues but I cannot boot to the point of a console. (https://doc.opensuse.org/documentati...c.trouble.boot)

    I really do not know where to start, any help is appreciated.

    thanks

    JOhn

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,670
    Blog Entries
    3

    Default Re: Cannot boot, Cannot login to recovery (where it says control-d)

    What you describe sounds like the plymouth screen.

    At the grub prompt, hit 'e'. That should put you into an edit mode.

    Scroll down to the line beginning "linux" (or, maybe, "linuxefi").
    In that line, delete the "splash=silent" part. Then CTRL-X to continue booting.

    That should boot without the plymouth splash screen. I don't know if it will get you to the desktop, but it is worth trying. And maybe look at messages on screen during boot. The last few lines of message might be relevant to the problem.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  3. #3

    Default Re: Cannot boot, Cannot login to recovery (where it says control-d)

    Thank you for the help!
    Oddly, it booted after that, though I can not think of a reason why..
    Hopefully it continues I will know tomorrow. :/
    Is there a way to save that config (without the boot quiet) so I can always see the boot process...?


    Looks like it was doing a filesystem check maybe at last successful boot, just prior to shutdown?

    last sucessful boot (end of log) (no logs fro last 3 partial boots)

    Code:
    Mar 01 00:00:17 localhost systemd[1]: Started Rotate log files.
    Mar 01 00:00:17 localhost btrfs-scrub.sh[28606]: Running scrub on /
    Mar 01 00:00:17 localhost dbus-daemon[1019]: [system] Successfully activated service 'org.opensuse.Snapper'
    Mar 01 00:01:33 localhost btrfs-scrub.sh[28606]: scrub device /dev/sda3 (id 1) done
    Mar 01 00:01:33 localhost btrfs-scrub.sh[28606]:         scrub started at Thu Mar  1 00:00:17 2018 and finished after 00:01:16
    Mar 01 00:01:33 localhost btrfs-scrub.sh[28606]:         total bytes scrubbed: 35.25GiB with 0 errors
    Mar 01 00:01:33 localhost systemd[1]: Started Scrub btrfs filesystem, verify block checksums.
    Mar 01 00:01:33 localhost systemd[1]: Starting Balance block groups on a btrfs filesystem...
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: Before balance of /
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: Data, single: total=34.01GiB, used=32.43GiB
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: System, single: total=64.00MiB, used=16.00KiB
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: Metadata, single: total=4.01GiB, used=2.81GiB
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: GlobalReserve, single: total=131.34MiB, used=0.00B
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: Filesystem      Size  Used Avail Use% Mounted on
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: /dev/sda3       215G   38G  176G  18% /
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: Done, had to relocate 0 out of 42 chunks
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: Dumping filters: flags 0x1, state 0x0, force is off
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]:   DATA (flags 0x2): balancing, usage=1
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: Done, had to relocate 0 out of 42 chunks
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: Dumping filters: flags 0x1, state 0x0, force is off
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]:   DATA (flags 0x2): balancing, usage=5
    Mar 01 00:01:33 localhost btrfs-balance.sh[28664]: Done, had to relocate 0 out of 42 chunks
    Mar 01 00:01:34 localhost kernel: BTRFS info (device sda3): relocating block group 39917191168 flags data
    Mar 01 00:01:34 localhost kernel: BTRFS info (device sda3): found 2 extents
    Mar 01 00:05:38 localhost smartd[1009]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 75 to 74
    Mar 01 00:31:01 localhost polkitd[1106]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.30, object path /org/kde/PolicyKit1/AuthenticationAgent,
    Mar 01 00:31:03 localhost systemd-logind[1128]: System is powering down.
    Mar 01 00:31:03 localhost systemd[1]: Stopping Session 2 of user root.
    Mar 01 00:31:03 localhost systemd[1]: Removed slice system-systemd\x2dhibernate\x2dresume.slice.
    Mar 01 00:31:03 localhost systemd[1]: Stopped target Graphical Interface.
    Mar 01 00:31:03 localhost systemd[1]: Stopping User Manager for UID 1000...

    JOhn

  4. #4

    Default Re: Cannot boot, Cannot login to recovery (where it says control-d)

    You can also indicate that DE is used and also the login manager
    Computer hardware
    If using the Proprietary Drivers
    If it happened after an update etc.

  5. #5
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,670
    Blog Entries
    3

    Default Re: Cannot boot, Cannot login to recovery (where it says control-d)

    Quote Originally Posted by kilbert View Post
    Is there a way to save that config (without the boot quiet) so I can always see the boot process...?
    Yes. Edit "/etc/default/grub" and look for GRUB_CMDLINE_LINUX_DEFAULT

    After editing, run:
    Code:
    grub2-mkconfig -o /boot/grub2/grub.cfg
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  6. #6

    Default Re: Cannot boot, Cannot login to recovery (where it says control-d)

    You can also indicate that DE is used and also the login manager
    Computer hardware
    If using the Proprietary Drivers
    If it happened after an update etc.

    Sorry- my setup is all stock.
    The only changes are multimedia codecs from packman.
    Desktop: KDE
    No proprietary drivers
    no updates in last 3-4 boots (I am intentionally not updating as often),

    hardware is amd64 8350/ on a asrock motherboard/ 16gb ram & r7-250 redeon video. 500gb samsung evo.for primary drive.

    thnaks JOhn

  7. #7
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,925
    Blog Entries
    14

    Default Re: Cannot boot, Cannot login to recovery (where it says control-d)

    From the output I read that you have a btrfs file system. If things worked correctly before you should be able to boot a previous snapshot,
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  8. #8

    Default Re: Cannot boot, Cannot login to recovery (where it says control-d)

    Quote Originally Posted by nrickert View Post
    Yes. Edit "/etc/default/grub" and look for GRUB_CMDLINE_LINUX_DEFAULT

    After editing, run:
    Code:
    grub2-mkconfig -o /boot/grub2/grub.cfg

    Appreciate the assistance - Thank you

  9. #9

    Default Re: Cannot boot, Cannot login to recovery (where it says control-d)

    Perhaps BTFRS maintenance/ balance kicked in to do some work. There is an issue on bugzilla that BTRFS maintenance renders your system unresponsive. I haven't experienced it anymore in this extend, but had quite a similar issue in the past. The issue was/ is related to the snapshots.

    See:
    https://bugzilla.opensuse.org/show_bug.cgi?id=1017461
    https://bugzilla.opensuse.org/show_bug.cgi?id=1063638
    Main: openSUSE Tumbleweed | KDE | AMD A8-7600 R7 | 32GB | Xonar Essence STX
    Laptop: openSUSE Leap 15.3 | KDE | Intel i5-2520M | 8GB | Intel HD

Posting Permissions

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