October 4, 20241 yr Hello Friends, Forgive me for i have sinned. My USB drive died and I never set up back ups I have made a new USB drive and I was trying to mount my drives to see if maybe by chance I made a back up on my array. When i was tying to figure out what drive was my parity drive I noticed that I was seeing two drives that were unmountable when I only had one parity drive. Is there a way to tell which was my parity drive and which was my data drive? Disk 6 and Disk 12 are the ones that are unmountable, Diag attached. tower-diagnostics-20241003-2133.zip
October 4, 20241 yr Community Expert Start the array in maintenance mode and post the output from: xfs_repair -v /dev/md6p1 xfs_repair -v /dev/md12p1
October 4, 20241 yr Author root@Tower:~# xfs_repair -v /dev/md6p1 Phase 1 - find and verify superblock... - block cache size set to 6138208 entries Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) empty log check failed zero_log: cannot find log head/tail (xlog_find_tail=5) ERROR: The log head and/or tail cannot be discovered. Attempt to mount the filesystem to replay the log or use the -L option to destroy the log and attempt a repair. root@Tower:~# xfs_repair -v /dev/md12p1 Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... ............................................ I assume this will take a while as its a 6tb drive I did run the repair in the webui last night before i saw your reply and the logs are a tad different Disk6 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) empty log check failed zero_log: cannot find log head/tail (xlog_find_tail=5) - scan filesystem freespace and inode maps... sb_fdblocks 592256559, counted 593723577 - 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 = 5 - agno = 2 - agno = 3 - agno = 4 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (1:1945069) is ahead of log (0:0). Would format log to cycle 4. No modify flag set, skipping filesystem flush and exiting. Disk12 Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... ............................................. Exiting now.
October 4, 20241 yr Community Expert 1 minute ago, Kablazn said: I did run the repair in the webui last night before i saw your reply and the logs are a tad differen Look like you ran with the -n (no modify) option so it was a check only and no repair was done.
October 4, 20241 yr Author I was just doing that to be safe? Since the output of disk 6 says to run the command with -L its safe to attempt that?
October 4, 20241 yr Community Expert Solution Use -L it's the only option, and usually OK, disk12 is likely parity, but you can confirm after fixing and mounting disk6.
October 4, 20241 yr Author Yup you were right. After the repair disk 6 came back so 12 has to be the parity drive. I appreciate the help!
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.