Read-only file system error

English Install/Boot/Login
1

Hi all,
An issue that previously plagued me on Fedora is now plaguing me on Opensuse. For no apparent reason my file system reverts to read only which obviously makes things pretty unusable. This is on an SSD with no other OS installed (no dual boot) and is a different SSD from when I was using Fedora. I have no idea what keeps causing this problem for me. The problem usually goes away for a bit after restarting but then eventually comes back.

This is what I have been able to find:
BTRFS critical (device nvme0n1p2): corrupt leaf: root=262 block=89704595456 slot=184, unexpected item end, have 10272 expect 8224
[16754.356185] BTRFS error (device nvme0n1p2): block=89704595456 write time tree block corruption detected
[16754.572884] BTRFS warning (device nvme0n1p2): Skipping commit of aborted transaction.
[16754.572905] BTRFS: error (device nvme0n1p2: state A) in cleanup_transaction:1997: errno=-5 IO failure
[16754.572917] BTRFS info (device nvme0n1p2: state EA): forced readonly

These bits came from dmesg when I tried to run a remounting command.

2

Is it on the same system though?

10272 == 0x2820
8224  == 0x2020

It is exactly one bit flip which usually suggests bad memory.

1 Like
4

It is the same laptop - do you think it could be that there’s soldered RAM and a SODIMM I bought aftermarket?

5

Run a dedicated memtester for several hours, e.g. overnight, or at least more than two complete passes. Among possibles: memtest86 from its author’s website, or memtest86+ from standard repos and Grub’s “Advanced” menu after installation, or run from an installation media boot. On newer PCs (post-DDR3) I only use the free version of memtest86 from its author’s website. If you get any error, try removing the SODIMM and then run again.