Last week after an update my system did not boot any more (After Reached target Initrd File Systems, the boot was stuck on the start job for the root partition…)
I had to boot my system using an older TW version 20240801 to get the system running again. I then did sudo snapper rollback to make the booted system workable. Now there are these snapshots:
# │ Type │ Pre # │ Date │ User │ Cleanup │ Description │ Userdata
──────┼────────┼───────┼──────────────────────────────────┼──────┼─────────┼────────────────────────┼──────────────
0 │ single │ │ │ root │ │ current │
3745- │ pre │ │ Mon 05 Aug 2024 09:07:46 PM CEST │ root │ number │ zypp(zypper) │ important=yes
3746 │ post │ 3745 │ Mon 05 Aug 2024 09:16:30 PM CEST │ root │ number │ │ important=yes
3747 │ pre │ │ Mon 05 Aug 2024 09:18:10 PM CEST │ root │ number │ zypp(zypper) │ important=yes
3748 │ post │ 3747 │ Mon 05 Aug 2024 09:18:51 PM CEST │ root │ number │ │ important=yes
3757 │ single │ │ Wed 07 Aug 2024 07:38:49 AM CEST │ root │ number │ rollback backup of #1 │ important=yes
3758+ │ single │ │ Wed 07 Aug 2024 07:38:49 AM CEST │ root │ │ writable copy of #3745 │
3759 │ pre │ │ Tue 13 Aug 2024 08:34:14 AM CEST │ root │ number │ zypp(zypper) │ important=no
3760 │ pre │ │ Tue 13 Aug 2024 08:45:30 AM CEST │ root │ number │ zypp(zypper) │ important=yes
3761 │ pre │ │ Tue 13 Aug 2024 09:46:34 AM CEST │ root │ number │ zypp(zypper) │ important=yes
When I now try to upgrade the system again, to check if the bug is fixed, I get this error for any package to install:
error: can't create transaction lock on /usr/lib/sysimage/rpm/.rpm.lock (Read-only file system)
How can I continue using and upgrading the system?
According to mount, the only read-only mounts are /run/credentials/systemd-*, /var/lib/snapd/snaps/* and /run/credentials/*
