[opensuse-factory] Boot problem: Failed to start Setup Virtual Console
For some of you this is old news, as it is discussed in https://bugzilla.opensuse.org/show_bug.cgi?id=1169783 And I finally found that link in an email response "Re: [opensuse-factory] New Tumbleweed snapshot 20200417 released!" So, people with encrypted partitions may face this problem and are unable to boot TW. I did zypper dup yesterday evening and wanted to start my computer now - bun now I'm rather writing this email on my Leap15.1 notebook. Cheers, Michael PS: what I wanted to say is that it would be useful to alert people with a meaningful subject on this mailing list (I find a "can not boot" problem important). Not, that it would have stopped me from zypper dup. But, discussion and solutions would have helped me. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Le samedi 25 avril 2020 à 09:19:44, Michael Born a écrit :
For some of you this is old news, as it is discussed in https://bugzilla.opensuse.org/show_bug.cgi?id=1169783
And I finally found that link in an email response "Re: [opensuse-factory] New Tumbleweed snapshot 20200417 released!"
So, people with encrypted partitions may face this problem and are unable to boot TW.
I did zypper dup yesterday evening and wanted to start my computer now - bun now I'm rather writing this email on my Leap15.1 notebook.
Cheers, Michael
PS: what I wanted to say is that it would be useful to alert people with a meaningful subject on this mailing list (I find a "can not boot" problem important). Not, that it would have stopped me from zypper dup. But, discussion and solutions would have helped me.
It has been reported here https://lists.opensuse.org/opensuse-factory/2020-04/msg00388.html I encountered the same problem and was able to solve thanks to: https://bugzilla.redhat.com/show_bug.cgi?id=1807771#c6 I added an override to all 'plymouth*.service' units with RemainAfterExit=yes and I was able to boot correctly again. Hope this helps. -- 'When there is no more room at school, the dumb will walk the Earth.' Sébastien 'sogal' Poher -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Yes, I found the link to the bug report in the email you pointed to. In every "snapshot xyz released" email on this list is written "Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org." I think, it also would be useful to have a "boot problem" email on this list. Concerning the bug https://bugzilla.opensuse.org/show_bug.cgi?id=1169783 I still can not start my TW. I don't get a rescue login. Starting older entries of the grub menu seems not to change anything. Starting an older snapshot lets me use TW, but "zypper dup" fails with error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Read-only file system). Because, / is now the old snapshot? What can I do to get a working TW back? Cheers, Michael -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le dimanche 26 avril 2020 à 10:42:18, Michael Born a écrit :
Yes, I found the link to the bug report in the email you pointed to.
In every "snapshot xyz released" email on this list is written "Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org."
I think, it also would be useful to have a "boot problem" email on this list.
Concerning the bug https://bugzilla.opensuse.org/show_bug.cgi?id=1169783 I still can not start my TW. I don't get a rescue login. Starting older entries of the grub menu seems not to change anything.
Starting an older snapshot lets me use TW, but "zypper dup" fails with error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Read-only file system). Because, / is now the old snapshot?
The snapshot you selected and boot on is a read only snapshot.
What can I do to get a working TW back?
Check snapper list To get a list of available snapshot and make a snapper rollback XXX with XXX being the last good snapshot (I assume you want to use the snapshot made before the `zypper dup` that broke your boot). After that, just `reboot`. The snapshot XXX will be promoted as default snapshot and you should be able to boot it successfully. Regards, -- 'When there is no more room at school, the dumb will walk the Earth.' Sébastien 'sogal' Poher -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thank you. I can boot TW again. When I do zypper dup, I'm again stuck in the boot process without being able to enter my /home encryption password. I'm fine with using the old snapshot for now. Cheers, Michael Am 26.04.20 um 23:13 schrieb sogal:
The snapshot you selected and boot on is a read only snapshot.
What can I do to get a working TW back?
Check
snapper list
To get a list of available snapshot and make a
snapper rollback XXX
with XXX being the last good snapshot (I assume you want to use the snapshot made before the `zypper dup` that broke your boot).
After that, just `reboot`. The snapshot XXX will be promoted as default snapshot and you should be able to boot it successfully.
Regards,
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le lundi 27 avril 2020 à 11:00:45, Michael Born a écrit :
Thank you. I can boot TW again. When I do zypper dup, I'm again stuck in the boot process without being able to enter my /home encryption password.
I'm fine with using the old snapshot for now.
Cheers, Michael
Am 26.04.20 um 23:13 schrieb sogal:
The snapshot you selected and boot on is a read only snapshot.
What can I do to get a working TW back?
Check
snapper list
To get a list of available snapshot and make a
snapper rollback XXX
with XXX being the last good snapshot (I assume you want to use the snapshot made before the `zypper dup` that broke your boot).
After that, just `reboot`. The snapshot XXX will be promoted as default snapshot and you should be able to boot it successfully.
Regards,
Of course do not `zypper dup` again after rollback :) At least unless you have locked *plymouth* packages until the bug is fixed. -- 'When there is no more room at school, the dumb will walk the Earth.' Sébastien 'sogal' Poher -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Michael Born -
sgl -
sogal