On Thu, Sep 03, Viktor Sævarsson wrote:
On Thu, Sep 3, 2020 at 7:40 AM Ignaz Forster <iforster@suse.de> wrote:
So after quite a bit of digging I found that there were newer snapshots they were just not showing up in the grub menu. This makes me a bit suspicious, as that happens when the root file system is not marked as read-only (see https://bugzilla.opensuse.org/show_bug.cgi?id=1174285). Do both btrfs property get / ro and findmnt / indicate that the current snapshot is a read-only snapshot?
"btrfs property get / ro" indicates that it is not read-only but
Ok, so the btrfs subvolume is not read-only, which means you system has to break. Did you install the transactional-server with YaST, or did you add the packages later? Or did you play with btrfs property on the subvolume?
"findmnt /" indicates that it is read-only. Should I run "btrfs property set / ro true"?
You can try it. But since you did run with a read-write btrfs subvolume, I'm not sure the system will recover from it.
No clue what caused the original issue though. But the system is working now and has been successfully updated to the latest version.
Excellent, good to hear!
Spoke too soon apparently. System auto updated again tonight and then failed to boot with the same message as originally.
That's expected if your btrfs subvolume is not ro. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org