/home is suddenly mounted as read-only during operations

Help
1

Related to Why does my root mount suddenly remount as read-only after a while? - #11 by eyeinsky

I have a similar issue, where my home partition as of a sudden is readonly

sudo fdisk -l
[sudo] password for papanito: 
Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 990 PRO 1TB                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C453446F-B330-6543-8D55-F52775A16D19

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       4096    1052671    1048576   512M EFI System
/dev/nvme0n1p2    1052672 1809217567 1808164896 862.2G Linux filesystem
/dev/nvme0n1p3 1809217568 1953520064  144302497  68.8G Linux filesystem


Disk /dev/nvme1n1: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: CT4000P3PSSD8                           
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 288C0A78-239F-497D-AC30-9878D79D283F

Device         Start        End    Sectors  Size Type
/dev/nvme1n1p1    34 7814037134 7814037101  3.6T Linux filesystem


Disk /dev/mapper/luks-266811b8-953c-4007-9bbd-ed9a009f72ed: 862.2 GiB, 925778329600 bytes, 1808160800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/luks-361b9e74-4d96-49fa-9243-1676586caed0: 3.64 TiB, 4000770218496 bytes, 7814004333 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/luks-7f34b0ef-aa8a-412a-933c-a42414371fad: 68.81 GiB, 73880781312 bytes, 144298401 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
2

While the symptom is similar, my issue with read-only remounting happened when having high sustained load on an USB connected SSD with an ZFS filesystem. This didn’t happen when the filesystem was Ext4 (if I remember correctly).

If for you it is the main drive, I’d suspect it’s something else.

3

its actually the homendrive (ssd, btrfs) but not the root (ssd, also btrfs). Did happen only once in the past 2 weeks

4

Is it the same main volume or a separate volume?

5

It’s a separate volumen and btrfs. There are periodo where it’s fine and periods where it happens. I also ran some LLMs to analyze my logs but so far I have not found the root cause

6

Maybe you have errors=remount-ro set and the system found evidence of FS corruption?