I've tried to read through the forums but nothing seems to be quite the same problem I have (maybe it is, idk). But I have a HDD that's giving me the error "Unmountable: not mounted" 

 

Running XFS Repair I get this response:

Quote

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

 

However, I can run an extended SMART report just fine. Comes back with no issues that I can tell. 

 

I'm not sure what to do to try to recover the drive, or if I should just replace it? It was recently a replacement of an older drive that failed. Probably hasn't been in the rack a full month. 

tower-diagnostics-20211117-1555.zip tower-smart-20211117-1535.zip

9 hours ago, keithwlandry said:

Running XFS Repair I get this response:

Please post the command you used to run xfs_repair.

I just ran it in the GUI with

-nv

I believe. 

That's strange as that would suggest there's no valid filesystem, syslog suggests otherwise, please disable array auto-start, reboot, start the array in maintenance mode and post the output of:

 

xfs_repair -v /dev/md9

 

/dev/md9: No such file or directory
/dev/md9: No such file or directory

fatal error -- couldn't initialize XFS library

 

Is what I got back

 

(Sorry for the slow reply, been on the road) 

On 11/19/2021 at 12:20 PM, JorgeB said:

start the array in maintenance mode and post the output of:

 

Duh, sorry. That was dumb. 

 

Same response as the GUI: 
 

Phase 1 - find and verify superblock...
couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!!

attempting to find secondary superblock...
...............................................
.........Sorry, could not find valid secondary superblock
Exiting now.

 

(except with a lot more dots)

I would suggest upgrading to v6.10-rc, it includes newer xfs-progs, then try repairing the fs again.

Updated to v6.10-rc and ran 

xfs_repair -v /dev/md9

again. Same results. 

Then it looks like a xfs_repair issue and if that's the case not much we can do, please post new diags after array start (in normal mode).

Here they are. 

tower-diagnostics-20211130-1149.zip

A valid xfs filesystem is still detected on mount:

 

Nov 30 11:49:00 Tower kernel: XFS (md9): Mounting V5 Filesystem
Nov 30 11:49:00 Tower kernel: XFS (md9): Internal error rhead->h_magicno != cpu_to_be32(XLOG_HEADER_MAGIC_NUM) at line 2886 of file fs/xfs/xfs_log_recover.c.  Caller xlog_valid_rec_header+0x17/0x11a [xfs]

 

Though it results in a crash, still find strange xfs_repair not finding a superblock, even if it wasn't 100% correct, but only solutions I see now are restoring from backups, if available, or try posting in the xfs mailing list and asking for help.

Well thanks for your help. 

 

What do you suggest doing next? I have a new HDD that's bigger than everything I have that I was going to use to replace my parity drive. But I probably shouldn't do that until this drive is fixed, huh? 

 

Should I just wipe it and try to rebuild it? 

 

Thanks again. 

1 hour ago, keithwlandry said:

Should I just wipe it and try to rebuild it? 

Format is NEVER part of rebuild, and rebuild won't fix corruption anyway.

1 hour ago, keithwlandry said:

What do you suggest doing next?

 

On 11/30/2021 at 6:03 PM, JorgeB said:

only solutions I see now are restoring from backups, if available, or try posting in the xfs mailing list and asking for help.