OpenSUSE not refreshing or doing anything because of errors

[WhyAmIHere18]

I ran sudo zypper ref and got the following errors. I updated OpenSUSE earlier today and now I can’t even open YaST.

sudo: unable to open /var/lib/sudo/ts/1000: Read-only file system
[sudo] password for root: 
Error retrieving metadata for 'openSUSE-Tumbleweed-Non-Oss':
Can't create metadata cache directory.
Skipping repository 'openSUSE-Tumbleweed-Non-Oss' because of the above error.
Error retrieving metadata for 'Open H.264 Codec (openSUSE Tumbleweed)':
Can't create metadata cache directory.
Skipping repository 'Open H.264 Codec (openSUSE Tumbleweed)' because of the above error.
Error retrieving metadata for 'openSUSE-Tumbleweed-Oss':
Can't create metadata cache directory.
Skipping repository 'openSUSE-Tumbleweed-Oss' because of the above error.
Error retrieving metadata for 'openSUSE-Tumbleweed-Update':
Can't create metadata cache directory.
Skipping repository 'openSUSE-Tumbleweed-Update' because of the above error.
Could not refresh the repositories because of errors.

When trying to open YaST, I get the following error:

Configuration file "/root/.config/y2controlcenterrc" not writable.
Please contact your system administrator.

I will upload the output of dmesg to a pastebin, because there are a lot of errors that seem to be related to a corrupted journal file.

Pastebin link: dmesg opensuse output - Pastebin.com

Note: Running on Lenovo Thinkpad T480

[arvidjaar]

[  428.138719] [   T69] BTRFS error (device nvme0n1p3): block=842579968 write time tree block corruption detected
[  428.147113] [ T5979] BTRFS error (device nvme0n1p3 state A): Transaction aborted (error -5)
[  428.147123] [ T5979] BTRFS: error (device nvme0n1p3 state A) in __btrfs_run_delayed_items:1176: errno=-5 IO failure
[  428.147128] [ T5979] BTRFS info (device nvme0n1p3 state EA): forced readonly

Try booting from live image and running btrfs check on this device.

[WhyAmIHere18]

Pastebin output: btrfscheck_out - Pastebin.com I am not sure if it did anything, I did not run the --repair extension.

UPDATE: That did work. I did not realize that I could check the filesystem here.

[arvidjaar]

@WhyAmIHere18

That did work

What did work and what exactly “worked” means?

Anyway - btrfs check does not show any problem so it appears like kernel prevented the permanent filesystem corruption by refusing to write invalid values. Did you try to boot?

And please - when you are asked or decide to post a command output - always include the full command line and subsequent shell prompt. The output and its interpretation may well change depending on the command options and it makes it clear that the output is complete.