Hi everyone, apologies if I'm missing something obvious here.

 

I had a disk fail in the array, and it was in an 'emulated' state. I replaced the disk with another of the same size and begun the rebuild process. However, now that this is done, I still get the message 'unmountable: wrong or no file system', and the original data from that disk no longer shows up in the array.

 

I started looking at tutorials and also tried the Check FIlesystem Status, but that didn't seem to change anything.

 

Any advice would be gratefully received!

tower-diagnostics-20250302-1154.zip

28 minutes ago, leo.sutton said:

I started looking at tutorials and also tried the Check FIlesystem Status, but that didn't seem to change anything.

This is the normal way to clear an Unmountable status.    It could be worth posting the outlay you get when trying this to see it provides a clue as to what is wrong.

Thanks!

 

I ran once and the output was absolutely huge, and it suggested running again, and this is the new outut I have:

Phase 1 - find and verify superblock... sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

I'm assuming the best option is 'Zero Log'?

Use -L, also, keep the old disk intact for now.

 

 

Thanks, I had one good run, but now it seems to be stuck in a bit of a loop:

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 Metadata CRC error detected at 0x468c38, xfs_dir3_block block 0xd36200/0x1000 bad directory block magic # 0x766a6d1d in block 0 for directory inode 13852979 entry "." at block 0 offset 64 in directory inode 13852979 references invalid inode 7018689594968465715 bad . entry in directory inode 13852979, was 7018689594968465715: correcting bad bestfree table in block 0 in directory inode 13852979: repairing table corrupt directory block 0 for inode 13852979 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 2 - agno = 3 - agno = 1 - agno = 0 bad directory block magic # 0x766a6d1d in block 0 for directory inode 13852979 bad bestfree table in block 0 in directory inode 13852979: repairing table Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... bad directory block magic # 0x766a6d1d for directory inode 13852979 block 0: fixing magic # to 0x58444233 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Metadata corruption detected at 0x468ac8, xfs_dir3_block block 0xd36200/0x1000 libxfs_bwrite: write verifier failed on xfs_dir3_block bno 0xd36200/0x8 xfs_repair: Releasing dirty buffer to free list! xfs_repair: Refusing to write a corrupt buffer to the data device! xfs_repair: Lost a write to the data device! fatal error -- File system metadata writeout failed, err=117. Re-run xfs_repair.

Running again gives the same result.

Try running on the CLI to confirm it's same, start the array in maintenance mode and type:

 

xfs_repair -vL /dev/mdXp1

 

Replace X with correct disk#, and post the outoput

I think I'm picking the right drive, but I'm getting:

 

Phase 1 - find and verify superblock...
superblock read failed, offset 0, size 524288, ag 0, rval -1

fatal error -- Input/output error

 

Do you know what I might be doing wrong?

Post the command you are using and the diagnostics after attempting to run it.