Recently I have been getting notifications that the "Reported uncorrect" SMART attribute was increasing for one of my drives. It is a small (500GB) drive so I thought the best action is to free up some space on my array then use unBALANCE to move all the files off that disk to the rest of the array before removing it.

 

However, whilst running unBALANCE, the unBALANCE UI froze up and then when I looked at the drive in the Unraid UI, I was told that the drive was "Unmountable: Wrong or no file system". Looking in the syslog I was led to try an xfs_repair but that was unable to repair the drive.

 

My next step was to simply replace the drive and rebuild from parity which took around 3 hours. It completed without any obvious errors but to my surprise the new drive was also listed as "Unmountable: Wrong or no file system".

 

So, if parity can't help me do I just have to take the loss of the drive and its data? I have backups of anything important and the rest is just media that can be found again.

I have attached diagnostics in case there is something else I could try - thanks for any advice.

tower-diagnostics-20230510-0831.zip

Edited May 10, 20233 yr by writablevulture

Rebuild won't fix filesystem issues, run xfs_repair again, and make sure it's without -n or nothing will be done.

3 minutes ago, JorgeB said:

run xfs_repair again

 

Thanks. Can I repair the new disk that I rebuilt from parity? Or should I reintroduce the original disk that first reported problems?

You can do it with the rebuilt disk.

Trying run xfs_reapir without the -n flag gives the same message that it did with the -n flag:
 

Sorry, could not find valid secondary superblock
Exiting now.

 

...and it is still listed as unmountable. Is that the end of the road for this?

10 minutes ago, writablevulture said:

Sorry, could not find valid secondary superblock
Exiting now.

That's not good news, don't know why this happens sometimes, but you are not the first one, clearly there's an xfs filesystem on that disk:

 

May  9 22:55:38 Tower kernel: XFS (md4): Corruption detected. Unmount and run xfs_repair

 

But then it cannot find the superblock, possibly only by asking in the xfs mailing list would they be able to help, otherwise restore from a backup if available or use a file recovery util like UFS explorer to try and recover the data.