I installed a new parity disk and began the process to rebuild the parity disk. While the parity was rebuilding, I noticed a Docker container that would not start. So I rebooted my Unraid tower with parity rebuild still going. After reboot, one of my data disks reports the "Unmountable: No filesystem"

 

I have tried the `xfs_repair /dev/sde` command as mentioned elsewhere but this command reported

`Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!! `

I have never gotten any CRC errors on the disk.

 

Any ideas how to repair the disk?

 

tower-diagnostics-20190913-0034.zip

Edited September 13, 20196 yr by runithome

31 minutes ago, runithome said:

I have tried the `xfs_repair /dev/sde` command as mentioned elsewhere but this command reported

Not exactly sure where you found this command, but that specific use of it is incorrect.

 

Stop the array and start it in Maintenance Mode. Click on the disk and you can run the filesystem check from the webUI, which will insure that you do the command correctly. Capture the results so you can post them.

 

 

42 minutes ago, runithome said:

new parity disk

199 UDMA_CRC_Error_Count    -O--CK   200   195   000    -    29

As an aside, 29 CRC errors over 1 hour of use isn't good.  The cabling more than likely isn't sitting quite right, and you probably also jarred slightly loose the cabling to disk 1

Thanks @trurl for the suggestions. Using the Check disk command from the Unraid UI repaired the file system! I was able to mount the disk again.

 

And thanks to @Squidfor the tip to check cabling connections because of CRC errors. It is likely that I accidentally jostled the other disks when installing new parity disk. I will re-seat them after the parity read finishes.