System Update Issues: "unable to open /var/lib/sudo/ts/1000: Read-only file system"

English Install/Boot/Login
1

Very recently (the past two days), I’ve been unable to update my system. The KDE Discover store keeps erroring when trying to update anything, and Myrlyn closes itself instantly after I give it authentication. Trying to manually update through the terminal with Zypper gives me this error:

unable to open /var/lib/sudo/ts/1000: Read-only file system

Checking to see what could be wrong, I stumbled upon, " How to Fix ‘Read-Only File System’ Errors ". The last thing I did before writing this was check which filesystems are read-only.

mount | grep -E '(^/dev|type (ext4|xfs|btrfs))'
/dev/mapper/system-root on / type btrfs (ro,relatime,seclabel,ssd,space_cache=v2,subvolid=350,subvol=/@/.snapshots/90/snapshot)
/dev/mapper/system-root on /opt type btrfs (ro,relatime,seclabel,ssd,space_cache=v2,subvolid=261,subvol=/@/opt)
/dev/mapper/system-root on /.snapshots type btrfs (ro,relatime,seclabel,ssd,space_cache=v2,subvolid=262,subvol=/@/.snapshots)
/dev/mapper/system-root on /srv type btrfs (ro,relatime,seclabel,ssd,space_cache=v2,subvolid=259,subvol=/@/srv)
/dev/mapper/system-root on /root type btrfs (ro,relatime,seclabel,ssd,space_cache=v2,subvolid=260,subvol=/@/root)
/dev/mapper/system-root on /var type btrfs (ro,relatime,seclabel,ssd,space_cache=v2,subvolid=257,subvol=/@/var)
/dev/mapper/system-root on /usr/local type btrfs (ro,relatime,seclabel,ssd,space_cache=v2,subvolid=258,subvol=/@/usr/local)
/dev/nvme0n1p3 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/mapper/system-home on /home type btrfs (rw,relatime,seclabel,ssd,space_cache=v2,subvolid=5,subvol=/)

This is where I ended up, and I wanted to ask the forum if this article is reliable to follow. I also wanted to check with the forum regarding if there are other filesystem which should not be read-only normally.

2

Did you make sure that you have choosen a read-write snapshot from the grub/systmd boot menu?

3

No, the output shows that everything is mounted rw except /home. @ExesCarnival0891 If you want it read-write, try sudo snapper rollback and reboot.

4

Nope. The output shows that everything is read-only except /home and /boot/efi

That’s why i asked if the TO bootet into a read-wright snapshot. Only if there is no read-write snapshot, a rollback from a read-only snapshout is required.

5

Stupid me, that is what I meant to write.

6

So I did not check every snapshot, however I have checked enough to say that I don’t know if rolling back is possible. Each time I try to load one, I get a variation of this screen

18781
187811920×1080 157 KB

7

That means nothing. The journal cannot be written because the snapshot you are on is read only. To make whatever snapshot read-write you have to do sudo snapper rollback and reboot.

8

My bad, I did not know I could still log in from that screen. Trying to do sudo snapper rollback results in this message:

18784
187844032×790 465 KB