Today when I started the array (rebooted to try the 6.7.0rc2 from 6.6.6; think if anything is wrong it was the reboot, not the new version that caused this) I see this:

 

If I do `ls /mnt/` I see all my discs except for `disk2` which is just missing.

 

- Does this mean my array is emulating disc2 via parity, or is it out and I'm going to find out once I go to watch a movie to find it's randomly not there?

- Is this a disc issue, or filesystem issue?

 

... I used to deal with things like this all the time when I was on reiserfs, but in the last few years I've forgotten what this is like! 😛 

 

From my syslog: 
 

Jan 29 08:46:12 Tower emhttpd: shcmd (4051): mkdir -p /mnt/disk2
Jan 29 08:46:12 Tower emhttpd: shcmd (4052): mount -t xfs -o noatime,nodiratime /dev/md2 /mnt/disk2
Jan 29 08:46:12 Tower kernel: XFS (md2): Mounting V5 Filesystem
Jan 29 08:46:13 Tower kernel: XFS (md2): Corruption warning: Metadata has LSN (1:741158) ahead of current LSN (1:741150). Please unmount and run xfs_repair (>= v4.3) to resolve.
Jan 29 08:46:13 Tower kernel: XFS (md2): log mount/recovery failed: error -22
Jan 29 08:46:13 Tower kernel: XFS (md2): log mount failed
Jan 29 08:46:13 Tower root: mount: /mnt/disk2: wrong fs type, bad option, bad superblock on /dev/md2, missing codepage or helper program, or other error.
Jan 29 08:46:13 Tower emhttpd: shcmd (4052): exit status: 32
Jan 29 08:46:13 Tower emhttpd: /mnt/disk2 mount error: No file system
Jan 29 08:46:13 Tower emhttpd: shcmd (4053): umount /mnt/disk2
Jan 29 08:46:13 Tower root: umount: /mnt/disk2: not mounted.
Jan 29 08:46:13 Tower emhttpd: shcmd (4053): exit status: 32
Jan 29 08:46:13 Tower emhttpd: shcmd (4054): rmdir /mnt/disk2

 

Seems likely that I should do what it says and run `xfs_repair`, but before I mess with 8TB of data thought I'd better check here....

Check filesystem on disk2:

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

or

https://wiki.unraid.net/Check_Disk_Filesystems#Drives_formatted_with_XFS

8 seconds to finish running `xfs_repair -v /dev/md2` and I'm back to all green.. thanks @johnnie.black!