ReadyNAS 214 volume is set to Read Only, please help.

Bencool:

Some of the logs have rotated, but I also am not seeing any disk issues on the data volume.  I am seeing issues with the btrfs metadata being corrupted.

Oct 07 00:15:20 bliao-readynas kernel: BTRFS error (device md127): cleaner transaction attach returned -30
Oct 07 00:29:35 bliao-readynas kernel: BTRFS error (device md127): parent transid verify failed on 23853767229440 wanted 2956556 found 4714624
Oct 07 00:29:35 bliao-readynas kernel: BTRFS warning (device md127): Skipping commit of aborted transaction.
Oct 07 00:29:35 bliao-readynas kernel: BTRFS: error (device md127) in cleanup_transaction:1864: errno=-5 IO failure
Oct 07 00:29:35 bliao-readynas kernel: BTRFS info (device md127): forced readonly
Oct 12 09:59:28 bliao-readynas kernel: BTRFS error (device md127): cleaner transaction attach returned -30
Oct 12 10:07:21 bliao-readynas kernel: BTRFS error (device md127): parent transid verify failed on 88637440 wanted 4714626 found 4714625

 There are a lot of other transid verify errors, but most are duplicative (identical).

Best option here is to back up the data and then do a factory default.  After that, reconfigure the NAS, restore the data, reinstall apps.  While this is a lot of work, it ensures that you get a clean file system.

Since most of the errors are identical, it might be possible to repair.  But this is risky, so making a full backup first is important.

Although I am not seeing errors on the data volume drives, I am seeing errors on two usb drives:

Oct 06 22:17:38 bliao-readynas kernel: blk_update_request: I/O error, dev sdf, sector 15099759872
Oct 07 00:29:46 bliao-readynas kernel: EXT4-fs (sdf1): warning: mounting fs with errors, running e2fsck is recommended
Oct 07 00:34:47 bliao-readynas kernel: EXT4-fs (sdf1): error count since last fsck: 824
Oct 07 00:34:47 bliao-readynas kernel: EXT4-fs (sdf1): initial error at time 1438131903: ext4_lookup:1051: inode 151724033
Oct 07 00:34:47 bliao-readynas kernel: EXT4-fs (sdf1): last error at time 1691675655: ext4_mb_generate_buddy:759
Oct 07 13:10:03 bliao-readynas kernel: EXT4-fs error (device sdf1): ext4_mb_generate_buddy:759: group 37096, block bitmap and bg descriptor inconsistent: 1574 vs 1576 free clusters
Oct 07 13:10:03 bliao-readynas kernel: JBD2: Spotted dirty metadata buffer (dev = sdf1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.

and

Oct 12 10:09:52 bliao-readynas kernel: EXT4-fs (sdc1): error count since last fsck: 825
Oct 12 10:09:52 bliao-readynas kernel: EXT4-fs (sdc1): initial error at time 1438131903: ext4_lookup:1051: inode 151724033
Oct 12 10:09:52 bliao-readynas kernel: EXT4-fs (sdc1): last error at time 1696695003: ext4_mb_generate_buddy:759

It's possible this is the same drive (with a different drive letter).

Finally, the OS partiton appears to be fuller than usual.  Not yet dangerous, but still something to take a look at after the main issues are resolved.

=== df -h ===
Filesystem      Size  Used Avail Use% Mounted on
/dev/md0        3.7G  2.0G  1.6G  57% /

Normally the OS is about 25% full.