Unraid 6.9.2 - Cache drive read-only errors

[hypemnd]

Somehow my cache drive has become read-only, and I don't understand why.   I'm now getting a bunch of mover errors and I can't write to the array.  I see a bunch of posts related to BTRFS file system issues, but my drive is formatted XFS.  Diagnostics are attached.  Any help would be greatly appreciated!

tower-diagnostics-20210820-1548.zip

[trurl]

Aug 18 10:03:38 Tower kernel: REISERFS (device md1): Remounting filesystem read-only

 

https://wiki.unraid.net/Manual/Storage_Management#Running_the_Test_using_the_webGui

[trurl]

Note it is disk1 that is read-only and needs to be checked.

[hypemnd]

reiserfsck 3.6.27

Will read-only check consistency of the filesystem on /dev/md1
Will put log info to 'stdout'
###########
reiserfsck --check started at Fri Aug 20 17:58:37 2021
###########
Replaying journal: 
Replaying journal: Done.
Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..  finished
Comparing bitmaps..Checking Semantic tree:
finished
4 found corruptions can be fixed when running with --fix-fixable
###########
reiserfsck finished at Fri Aug 20 21:17:21 2021
###########
bad_indirect_item: block 2403926022: The item (2206 2209 0x1681001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (342) to the block (2403933964), which is in tree already
bad_indirect_item: block 2403926022: The item (2206 2209 0x1681001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (343) to the block (2403933955), which is in tree already
vpf-10640: The on-disk and the correct bitmaps differs.

 

 

 

[JorgeB]

3 hours ago, hypemnd said:

4 found corruptions can be fixed when running with --fix-fixable

Run it again the this option.