We had a power outage earlier today and after it came back on i tried to power on my unraid server and ended up with unmountable disk3. 

On boot it mounted the array in normal mode and was doing a parity check, which i cancelled and put into maintenance mode. and tried the check filesystem option for xfsrepair with the -n option. It returned the following logs pasted belore. Can someone advise my next steps so I don't lose data? thanks

 

 

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 1128855849, counted 1152691800 - 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 inode 7140111386 - bad extent starting block number 4503567550787390, offset 0 correcting nextents for inode 7140111386 bad data fork in inode 7140111386 would have cleared inode 7140111386 - agno = 4 - 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 = 2 - agno = 5 - agno = 7 - agno = 6 - agno = 4 - agno = 1 entry "Version-0.apversion" in shortform directory 7129804360 references free inode 7140111386 would have junked entry "Version-0.apversion" in directory inode 7129804360 would have corrected i8 count in directory 7129804360 from 3 to 2 inode 7140111386 - bad extent starting block number 4503567550787390, offset 0 correcting nextents for inode 7140111386 bad data fork in inode 7140111386 would have cleared inode 7140111386 - 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 "Version-0.apversion" in shortform directory inode 7129804360 points to free inode 7140111386 would junk entry would fix i8count in inode 7129804360 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.

 

Quote

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 1128855849, counted 1152691800 - 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 inode 7140111386 - bad extent starting block number 4503567550787390, offset 0 correcting nextents for inode 7140111386 bad data fork in inode 7140111386 would have cleared inode 7140111386 - agno = 4 - 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 = 2 - agno = 5 - agno = 7 - agno = 6 - agno = 4 - agno = 1 entry "Version-0.apversion" in shortform directory 7129804360 references free inode 7140111386 would have junked entry "Version-0.apversion" in directory inode 7129804360 would have corrected i8 count in directory 7129804360 from 3 to 2 inode 7140111386 - bad extent starting block number 4503567550787390, offset 0 correcting nextents for inode 7140111386 bad data fork in inode 7140111386 would have cleared inode 7140111386 - 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 "Version-0.apversion" in shortform directory inode 7129804360 points to free inode 7140111386 would junk entry would fix i8count in inode 7129804360 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.

 

Are you doing this from webUI or command line?

Attach diagnostics to your NEXT post in this thread.

Do you have a USB drive(s) in your array?

 

MrGrey.

8 hours ago, metatron said:

Can someone advise my next steps

Next step is to run it again without -n or nothing will be done, and if it asks for it use -L.