Hi guys,

 

I just replaced a faulty Drive 4 in my array and it rebuilt successfully with no errors that I could see. I precleared the replacement disk first before rebuilding the array. About a day later after a reboot I'm now getting an error message in Fix Common Problems:

 

disk4 (ST2000NM0023_Z1X1ABP0_35000c50057a9c313) has file system errors (No file system (32))    If the disk if XFS / REISERFS, stop the array, restart the Array in Maintenance mode, and run the file system checks. If the disk is BTRFS, then see this post. If the disk is listed as being unmountable, and it has data on it, whatever you do do not hit the format button. Seek assistance HERE

 

Now Disk 4 is showing as unmountable. If I go into the disk settings and run a filesystem check this is the output that I get from the window:

 

Phase 1 - find and verify superblock...
couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!!
attempting to find secondary superblock...
found candidate secondary superblock...
unable to verify superblock, continuing...
Sorry, could not find valid secondary superblock
Exiting now.

My question is where do I go from here? I've only had unRAID for a couple of months and this is my first build so I'm still trying to crash course everything. This is my first issue where I do not know what to do and I'm afraid to proceed solo.

 

Doens't look good... was the disk unmountable during rebuild or only after? Post your diagnostics.

Here you go.

 

The rebuild went smoothly. The disk went unmountable a day later. Parity still shows as valid and I have an extra 2TB disk on hand also.

diagnostics-20171111-1010.zip

The result should be the same but run xfs_repair from the console/SSH just to make sure you get the same error:

 

-stop the array

-start the array in maintenance mode

-using the console or SSH into your server and type

 

xfs_repair -v /dev/md4

 

Post the output

Output is exactly the same:

 

Phase 1 - find and verify superblock...
couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!!
attempting to find secondary superblock...
found candidate secondary superblock...
unable to verify superblock, continuing...
Sorry, could not find valid secondary superblock
Exiting now.

 

26 minutes ago, Neurotic said:

Output is exactly the same:

 

That's expected, just wanted to make sure since there were issues before with the GUI filesystem check and looking at the syslog it appears to find the superblock, it just mentions metadata corruption, which is usually fixable.

 

Your options are limited here, it looks OK but run an extended SMART test on the disk to make sure it's good and not causing issues, if it's good your options will be to restore from a backup, restore from the old disk if available or using a file recovery utility like UFS explorer.

Disk shows as unavailable under the Self Test section of the Disk Settings page. Clicking the spin up button doesn't change the disk's status after a page refresh. Bad disk perhaps?

 

Seems odd because the drive activity light was blinking during the file system repair.

GUI probably doesn't support SMART testing on SAS disks, try doing it on the console/SSH

SMART results attached.

 

The old disk is still available. I pulled it before it could fail because it was starting to throw SMART errors (current pending sector count/offline uncorrectable count). I was in the middle of the process of backing up this array's contents to an offsite provider so I do not have a decent backup there. I am unfamiliar with UFS Explorer but I'm sure I could figure it out with enough time to read.

 

Which of these options seems the most logical given the situation?

ST2000NM0023_Z1X1ABP0_35000c50057a9c313-20171112-0043.txt

Disk looks good, if old disk is still available you can mount it with the Unassigned devices plugin, format current disk4 and copy everything over from the old disk.