Woke up this morning to Plex being offline, when to restart it via gui but docker failed to start (not sure if there was a power outage.

I looks like Cache_B went into read-only mode according to Fix Common Problems and I can't seem to get it out.

I've tried following

 but i get this error:

mount: /temp: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.

 

I've been able to make a copy of appdata, some other folder and docker.img, but still stuck on read only.

Any help would be appreciated.

tower-diagnostics-20240229-1911.zip

Syslog is completely spammed with these:

 

Feb 29 19:12:01 Tower emhttpd: error: malloc_share_locations, 7197: Operation not supported (95): getxattr: /mnt/user/mount_mergerfs
Feb 29 19:12:01 Tower emhttpd: error: malloc_share_locations, 7197: Operation not supported (95): getxattr: /mnt/user/mount_rclone
Feb 29 19:12:02 Tower emhttpd: error: malloc_share_locations, 7197: Operation not supported (95): getxattr: /mnt/user/appdata
Feb 29 19:12:02 Tower emhttpd: error: malloc_share_locations, 7197: Operation not supported (95): getxattr: /mnt/user/local

 

Reboot and post new diags after array start.

4 hours ago, JorgeB said:

Syslog is completely spammed with these:

 

Feb 29 19:12:01 Tower emhttpd: error: malloc_share_locations, 7197: Operation not supported (95): getxattr: /mnt/user/mount_mergerfs
Feb 29 19:12:01 Tower emhttpd: error: malloc_share_locations, 7197: Operation not supported (95): getxattr: /mnt/user/mount_rclone
Feb 29 19:12:02 Tower emhttpd: error: malloc_share_locations, 7197: Operation not supported (95): getxattr: /mnt/user/appdata
Feb 29 19:12:02 Tower emhttpd: error: malloc_share_locations, 7197: Operation not supported (95): getxattr: /mnt/user/local

 

Reboot and post new diags after array start.

Here you go.

Rebooted with array started.

tower-diagnostics-20240301-0905.zip

Corruption is being detected and the pool is going read-only, with btrfs recommend backing up what you can and reformatting.

 

P.S. data corruption was also detected on the other pool, recommend running memtest, then a correcting scrub.