Looks like my Slo Roll install has blown itself up?? Today was supposed to be Slow Roll day, had run a few zypper dup -l in the last few weeks, no problems were showing up in those upgrades.
This morning the Slo Roll listing in grub booted to dmesg data, showing OK, then at bottom there was something like, “NVIDIA taints kernel” then went to black screen. Used the power button to shut down and reboot, second timeI went to “advanced options” in grub and picked the bottom line of kernels of 8 lines. That time it went to “finished virtual console setup” and then hung there for several minutes.
Repeated the shutdown and went to advanced options and picked the third line item from the top,had the sam data about “virtual console setup” but this time I went away to feed the animals. When I came back there was a TTY with a bunch of dracut lines, that said, “Dracut Emergency shell” with the line to “enter password to log in” . . . trying that failed to do anything. Hitting return did not bring a cursor. I again shut down and rebooted this time to a functional Deb trixie install . . . tomorrows system, but working today.
Could not get to a TTY and log in that way, in one of the lists of data was something saying, “could not find sdb8” which is where the / files are located, and it could not find the bootloader partition, naming it by UUID.
I didn’t have time to update the repos to the very latest repos, after I had updated them right after the fresh install a few weeks back, but again, no errors showed in the zypper ref . . . packages were upgraded and the system was running in GUI as of last Thursday, the last time I tried to boot into it; ran any upgrades then shut it down.
Today, nichts aber die schwarze or the “dracut emergency shell” is all that Slow Roll is coming up with for itself??
Maybe. It’ll be tomorrow morning 12 hours plus from now before I will be back to that machine. Will have to take a cell phone shot and email it, and then what, attach it to a post?? Bit of a pain, but, have not seen a “dracut emergency shell” before this one.
It just looks like any other emergency shell, except this one didn’t let me log in or do anything.
Checking the downloads page for Slow Roll, it looks like the last version goes back to November some time. Doesn’t seem worth it to try to reinstall from something that far back, as somewhere in the recent zypper something was introduced that caused the / to implode on itself??
Nothing to be concerned about obviously, there must be a bug report in it, but what to file it against . . . ?? A “rhetorical question” . . . asked to no one in particular . . . because, with Slow Roll we “have time” . . . nothing is happening quickly with it, etc. It’s the Sloth Rolling edition. Nothing to see here, move along please . . . move along.
IMHO there is no general problem with Slowroll. Me and other users have it running without issues. But it is remarkable that nearly all of your installations, Slowroll, Leap and so on are broken. So you either find special bugs or you have a “special hand” to break your installations…
Well, yes, both Leap 15.6 and Slow Roll installs are having problems, but today I’m in TW and TW now is running fine on the same machine. Because I have a number of bare metal installs I don’t “fiddle” with any one of them. I just run zypper once a week. The last 6 months or so have been a “trial” as far as my open SUSE installs go . . . essentially moving from one problem to the next.
Contrasting that with my installs of Debian, trixie and Sid, my Manjaro, and a Lubuntu mantic . . . on the same machine, sometimes in the same drive, running just about without any problems. I think sometime a few months back there was a hiccup with Manjaro . . . forum gave me the solution quickly and back to smooth sailing . . . .
Slow Roll now essentially logs to emergency shell, just running zypper once a week. Leap 15.6 boots OK, but won’t revive from suspend. TW working just fine.
