TheFinalJohn

running 6.12.10 and XFS drives My unraid server had an unclean shutdown. When it came back it started a parity check like normal. I notices that one of the drives was listed as "Unmountable: Unsupported or no file system" where the size and useage are normally displayed. Per the documentation, I ran the check disk with option -n. However other than the name I know nothing about xfs or the xfs_repair tool. I am unsure how to interpret these results or the best way to resolve the issue with out data loss. I assume it is as simple as updating the flags in the webgui and running it again. But the docs also said to bring questions here. check results: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_fdblocks 1364236085, counted 1388072036 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 inode 8591151962 - bad extent starting block number 4503567550846459, offset 0 correcting nextents for inode 8591151962 bad data fork in inode 8591151962 would have cleared inode 8591151962 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 1 - agno = 2 - agno = 4 - agno = 5 entry "IMG_1351.JPG" at block 5 offset 264 in directory inode 8590286505 references free inode 8591151962 would clear inode number in entry at offset 264... - agno = 6 inode 8591151962 - bad extent starting block number 4503567550846459, offset 0 correcting nextents for inode 8591151962 bad data fork in inode 8591151962 would have cleared inode 8591151962 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... entry "IMG_1351.JPG" in directory inode 8590286505 points to free inode 8591151962, would junk entry would rebuild directory inode 8590286505 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. thanks in advance, slartibartfast-diagnostics-20240820-1647.zip