March 9, 20233 yr hello to make it short. i was moving some data, and cleaning and first, i got ghost files that i could not move files (was an rsync error). then everything how ever got worse. So at one point, I restarted the machine but had to attend to something else. But unraid does always a parity sync when starts, so when i came back to it a day later i found: Disk 2: Unmountable: Wrong or no file system and unraid told me it found sync errors that it hat fixed. Sadly i can´t just format it and rebuild, cause it turns out ther is data on that drive i don´t have a backup of. if anyone has an idea pls help i did not try anything else befor the error, i tried doing a backup but that gave me yet again a rsync error. Edited March 9, 20233 yr by lhw1221
March 9, 20233 yr Author 11 minutes ago, JorgeB said: Check filesystem on disk2. I just gona post te result her i did a the instruction recomendet for xfs using -nv Phase 1 - find and verify superblock... - block cache size set to 714080 entries Phase 2 - using internal log - zero log... zero_log: head block 1069105 tail block 1069083 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_icount 240128, counted 63040 sb_ifree 27898, counted 39218 sb_fdblocks 1201212561, counted 1405852858 - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 2 - agno = 4 - agno = 5 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Thu Mar 9 11:02:56 2023 Phase Start End Duration Phase 1: 03/09 11:02:49 03/09 11:02:49 Phase 2: 03/09 11:02:49 03/09 11:02:49 Phase 3: 03/09 11:02:49 03/09 11:02:53 4 seconds Phase 4: 03/09 11:02:53 03/09 11:02:53 Phase 5: Skipped Phase 6: 03/09 11:02:53 03/09 11:02:56 3 seconds Phase 7: 03/09 11:02:56 03/09 11:02:56 Total run time: 7 seconds
March 9, 20233 yr Community Expert You will need to run without -n before anything gets fixed, and also add -L if it is asked for. After that restarting the array in normal mode should mount the drive.
March 9, 20233 yr Author 7 minutes ago, itimpi said: You will need to run without -n before anything gets fixed, and also add -L if it is asked for. After that restarting the array in normal mode should mount the drive. it seems to have workt next step is to try monting again ?? 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 destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_icount 240128, counted 63040 sb_ifree 27898, counted 39218 sb_fdblocks 1201212561, counted 1405852858 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - 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 = 5 - agno = 2 - agno = 1 - agno = 4 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (3:1067419) is ahead of log (1:2). Format log to cycle 6. done
March 9, 20233 yr Community Expert 2 minutes ago, lhw1221 said: next step is to try monting again ?? Yes.
March 9, 20233 yr Author okay seems to be good but now i ownly got 12 tb of 13 tb i probebly lost some data but hey the drive is still ser and the most data seems to be back thnx for your help guys
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.