Friday Night I had something happen to one of my data drives and it became un-mountable. Assuming is was a bad drive, I

1) swapped it out

2) had the new one rebuild.

3) Stopped the Array

4) rebooted

5) Started the Array

6) new rebuilt drive would still not mount

7) ran "xfs_repair -L /dev/sdd" and it failed "could not find secondary superblock"

 

I still have the old drive originally as it came out the server.

 

 

 

Any suggestions are welcome?

epcot-diagnostics-20160925-0550.zip

Rebuilding drives does just that, rebuilds a drive exactly back to what it was.  If the file system was corrupted, it is still corrupted.

 

The error you saw in #7 above is what you usually see if you run xfs_repair on the drive, not on the file system.  The drive could be known as /dev/sdh or /dev/sdb, the file system would be on the first partitions on those drives, at /dev/sdh1 or /dev/sdb1 or the array disks at possibly /mnt/md1 or /mnt/md2.  xfs_repair never works on drives, it work on file systems.  Please see Check Disk File systems for more info.

Sorry I corrected my first post. I did run "xfs_repair -L /dev/sdd" not sure what I typed "xfs_rebuild" originally.

Sorry I corrected my first post. I did run "xfs_repair -L /dev/sdd" not sure what I typed "xfs_rebuild" originally.

 

That's what Rob was pointing out, you can't run xfs_repair on the disk, it has to be on the partition, though you have to use the md* device to maintain parity, in this case for disk4, it should be:

 

xfs_repair /dev/md4

Thanks I noticed that too and just re ran it using "xfs_repair -L /dev/sdd1" and it looks like we are back in business.  Thanks to everyone for your patience and assistance.

Thanks I noticed that too and just re ran it using "xfs_repair -L /dev/sdd1" and it looks like we are back in business.  Thanks to everyone for your patience and assistance.

 

Then you need to do a correcting parity check, as parity was not updated.