I sometimes don't look forward to restarting my OMV server as it's the best time for alert you of errors :p.
I am getting a few "Multiply-claimed block" for my Raid during boot even though the GUI says it is clean. I pasted my log as I don't see much discussion about this here. It suggests a manual scan, any recommendations as fsck has many arguments and I don't want to chance it and lose data?
Code
fsck from util-linux 2.20.1
RaidArray3 contains a file system with errors, check forced.
RaidArray3: Duplicate or bad block in use!
RaidArray3: Multiply-claimed block(s) in inode 47513811: 380144016
RaidArray3: Multiply-claimed block(s) in inode 47513814: 380144018
RaidArray3: Multiply-claimed block(s) in inode 47513815: 380144019
RaidArray3: Multiply-claimed block(s) in inode 47514245: 380144016
RaidArray3: Multiply-claimed block(s) in inode 47514248: 380144018
RaidArray3: Multiply-claimed block(s) in inode 47514250: 380144019
RaidArray3: (There are 6 inodes containing multiply-claimed blocks.)
RaidArray3: File /plexmediaserver/Library/Application Support/Plex Media Server/Plug-in Support/Caches/com.plexapp.agents.thetvdb/HTTP.system/e1/4b0bdf5f10fcd3d8763352d93319d3a6e4ca06_attributes (inode #47513811, mod time Tue May 26 21:19:11 2015)
has 1 multiply-claimed block(s), shared with 1 file(s):
RaidArray3: ... (inode #47514245, mod time Sat Mar 28 13:52:23 2015)
RaidArray3:
RaidArray3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
1Drive: clean, 211592/61054976 files, 86147191/244190121 blocks
fsck died with exit status 4