CupOfTee

OMFG, thank you, mate! You saved me from days of anxieties! Mount successful. Shared folders are back online. Verifying files now, but spot checking they're back. Looks like my dockers wonkey but I reather rebuild those than lose my files. Will be sending you appreciation soon.

Interesting. Didn't realize there was this option. Ran the Check Filesystem. Output below. Message "File system corruption detected." received with a Fix button active. Didn't press it bc I'm too new at this and know better. 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... agi unlinked bucket 53 is 295964853 in ag 9 (inode=19623317685) agi unlinked bucket 54 is 295964854 in ag 9 (inode=19623317686) agi unlinked bucket 60 is 250272188 in ag 9 (inode=19577625020) agi unlinked bucket 57 is 9709625 in ag 8 (inode=17189578809) agi unlinked bucket 58 is 372999674 in ag 8 (inode=17552868858) agi unlinked bucket 59 is 372999675 in ag 8 (inode=17552868859) agi unlinked bucket 60 is 372999676 in ag 8 (inode=17552868860) agi unlinked bucket 61 is 372999677 in ag 8 (inode=17552868861) agi unlinked bucket 62 is 372999678 in ag 8 (inode=17552868862) agi unlinked bucket 63 is 372960831 in ag 8 (inode=17552830015) sb_ifree 381, counted 582 sb_fdblocks 375012556, counted 431105891 - 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 - agno = 5 - agno = 6 - agno = 7 - agno = 8 imap claims in-use inode 17189578807 is free, would correct imap Metadata corruption detected at 0x46c248, xfs_dir3_leafn block 0x419f7be60/0x1000 corrupt directory leafn block 8388610 for inode 17548883125 - agno = 9 data fork in ino 19577625021 claims free block 2444335180 - agno = 10 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... unknown block state, ag 9, blocks 28415906-28416041 - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 8 - agno = 6 - agno = 5 - agno = 7 - agno = 9 - agno = 4 - agno = 10 Would clear next_unlinked in inode 17189570106 Would clear next_unlinked in inode 17189578810 Would clear next_unlinked in inode 17334349886 Would clear next_unlinked in inode 17334349887 Would clear next_unlinked in inode 17337819838 Would clear next_unlinked in inode 17337819839 Would clear next_unlinked in inode 17548886779 Would clear next_unlinked in inode 17548886780 Would clear next_unlinked in inode 17549853566 Would clear next_unlinked in inode 17552830011 Would clear next_unlinked in inode 17552830015 Would clear next_unlinked in inode 17552868858 Would clear next_unlinked in inode 17552868859 Would clear next_unlinked in inode 17552868860 Would clear next_unlinked in inode 17552868861 Would clear next_unlinked in inode 17552868862 Incorrect reverse-mapping: saw (9/28415906) len 136 owner 19577625021 off 0; should be (9/28416076) len 136 owner 19577625021 off 0 No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 No modify flag set, skipping filesystem flush and exiting.

Array started in normal. Diagnostic logs attached. kc-diagnostics-20250304-1352.zip

Diagnostic logs attached. Fingers crossed. Will be super appreciative if there is a solution. kc-diagnostics-20250304-1327.zip

I'll probably will get a lot of flak for this. I'm a rookie with NAS and Unraid, so I deserve it. Recently had a corrupt JellyFin docker and kept trying to uninstall/reinstall it, but with no success. It was a local db issue for JF. I thought I could go into the appdata folder and just delete the JellyFin folder in it. After doing that, my drive was unmounted and it's not recognizing anything. It's asking to format the drive when mounting, but I know not to do that. I rebooted so I don't have the logs anymore. I don't know where to go anymore. Thinking of pulling the drive out and trying to recover undeleted files but that's going to take days. Any suggestions or advice is very much appreciated. Again new guy so asking for patience and grateful for any help.