Hi
for a couple of weeks I have now had the following problem:
if I do any update from 20200409 Kernel 5.6.4-1 the reboot hangs just after the line “Finished Remount Root and Kernel file system” and stays there. It does not even ask me for the key of the encrypted /home partition so I suspect I am not even getting to mounting /home. There is one Failed entry: Failed to start Setup Virtual Console telling me to look at systemctl status systemd-vconsole-setup.service
I can restore the last snapshot without a problem.
Happens every time I update either via zypper or yast.
Tried looking at the systemd but oviously the part between the shutdown after the update and the rollback is always missing. Where do I start looking?
Ciao
Alex
I doubt you can update Tumbleweed using YaST. Use
zypper dup
(or equivalent).
you can. But it does not make any difference.
meaning I tried zypper up, zypper dup and yast. Always the same.
I do not understand what you mean with this. But people here expect and trust you have updated your Tumbleweed in the correct way, else it will be very difficult to help.
I thought I made that pretty clear: that I have tried all ways, the correct and the alternative ways. Anyway I did mention zypper in my original post, didn’t I? So, can you help? Where do I start looking?
When you can not confirm that your last trial to bring your Tumbleweed upto date was a
zypper dup
(and not just a vague “I mentioned zypper”), I am not going to dive in this problem.
Look, I am neither here to have an argument nor to be lectured by someone who does not properly read my initial thread and straight away assumes that I am a noob.
To the best of my knowledge I did supply the information both to your question and to what exactly my answer meant: that, yes, I did try zypper dup among other approaches. If you still rather nag than maybe answer my question “where do I start looking” then just stay away and I will happily wait for someone who is not just here to troll.
Here’s something to try.
At the grub menu, after moving to your boot entry, hit the ‘e’ key. That should give an edit screen.
Scroll down until you find the line that starts “linux” (or perhaps “linuxefi”).
Scroll to the right. You will probably see “splash=silent”. Replace that string with “plymouth.enable=0”.
Then hit CTRL-X to resume booting.
According to some reports, the problem you are having is due to plymouth, and disabling that might avoid the problem for now.
I should have added the bug information.
This appears to be Bug 1169783
Great! Switching plymouth off did the job.
Thanks
Alex
You can make that change “permanent” in Yast bootloader. Then monitor the bug report to see whether it is safe to revert back to using plymouth.
Did exactly that straight away. Now I just try again everytime plymouth upgrades. But then the text prompt is just fine.
Thanks again.
Alex
I can confirm the bug with the same circumstances.
After update on system where /home partition is encrypted, system does not ask for password on boot. Disabling Plymouth helps.
Should I create additional report on Bugzilla?
I would suggest that you add a comment to the bug report already mentioned (in reply #9 above). That will also add you to the mailing list for that bug report.
In my case replace “splash=silent” with “plymouth.enable=0” don’t solve the problem. Trying with recovery mode or with a read-only snapshot don’t work. With every option I try the system hangs. So I’m unable to get a prompt. This is unusable (and is the laptop of my brother :().
You appear to have a different problem, though the symptoms might look similar.
At present, you have not told us very much about your problem. If you can give more detail, then maybe start a new thread with those extra details.
Just update the system with “zypper dup” as always. And when I back, the screen is black with some characters “#$%” at top left corner. The system not responded after several minutes. So I reboot the machine and now I have this problem.
Please start a new thread with this. You have a different problem, and it is less confusing if you use your own thread.