The grub boot hang did not help me much. I tried to “Edit entry”. Then I got some grub configuration, but there was no option for quiet.
> In grub, edit your kernel command line, remove both quiet and splash=whatever options and replace them with debug and initcall_debug. https://en.opensuse.org/SDB:Debugging_boot_hang
Somehow now I managed to get a maintenance console as root.
I have no Internet, or I would have tried to run an update.
Tried to start network, but then it restarted the maintenance console with login
After some troubleshooting, and debugging, I could not find the problem, nor a solution.
I created an OpenSUSE Leap 15.2 USB drive, and are in the process or performing an upgrade.
Hopefully it will get my box up and running again.
Edit:
Grub still had option for the older kernel that was with Leap 15.1
I choose that kernel, and the boot process did show up. It did not so with the new kernel.
With the old kernel all I get after boot is after several OK lines.
Give root password for maintenance
(or press Control-D to continue):
Providing the root password gives me a prompt.
Pressing Control-D
sulogin: cannot read /dev/tty1: Operation not permitted
I perfectly understand that. On a different occasion I spent hours on trying to avoid the fresh install. Later I had to admit to myself the immediate fresh install would have saved me (exactly these) many hours. It wasn’t that bad after deciding to move to a new ssd having everything still available and /home on it’s own partition.
I’d try to run a life system - you should be able to create one as you could create the media for the update, right? If it works it would
a) confirm it wasn’t your processor getting damaged but “only” your OS and
b) give you the chance to save any settings in /etc or /home.
Edit: Well, and then go for the fresh install. :rolleyes:
I was afraid of that. The last thing I want is to disassemble my computer.
I have one NVME M.2 drive which runs my Linux. One additional SSD SATA for Steam.
If a fresh install doesn’t work I see no other option than to disassemble my computer, and then reassemble.
I removed my secondary SSD drive, but the problem still persist.
It now only boots up in “emergency mode”.
I then removed the secondary drive from my /etc/fstab, and my computer booted up in KDE. Yay!
How come a single drive should cause so much trouble booting up. If the drive did not work, it should have just ignored it and logged in, then continued booting up.