November 17, 20241 yr Hi everyone, One data disk in my array needs replacement so I replaced it with a new one and initiated parity rebuild. Unfortunately, during that time my nephew (whom I have now disowned ) pushed my server by mistake and caused another data disk to redball. (I checked it and it is perfectly fine). Ideally, i want to reverse the "redballing", and restart the rebuild for the original faulty disk. Normally (if there was just a redballed disk), i would do that by creating a new configuration and accepting that parity is valid but now I cannot since the new disk was not rebuilt yet. Any suggestions are very welcome
November 17, 20241 yr Community Expert redball? is disk disabled? stop array start array rerun partiy... please post diag file... Edited November 17, 20241 yr by bmartino1
November 18, 20241 yr Author Thanks for your response. 11 hours ago, bmartino1 said: redball? is disk disabled? The disk is disabled but it is fine (a cable was moved but nothing was being written to it, I tested it and it is actually fine) 11 hours ago, bmartino1 said: stop array start array rerun partiy... My whole plan is to first find a way to reenable the redballed disk and then start parity rebuild for the actually faulty one that has been replaced with a new disk... Edited November 18, 20241 yr by papnikol
November 18, 20241 yr Community Expert Diags are after a reboot, were rebuilding you rebuilding diks1 or disk3?
November 18, 20241 yr Author 48 minutes ago, JorgeB said: Diags are after a reboot, were rebuilding you rebuilding diks1 or disk3? Yes, I had to reboot after the accident I mentioned. I was rebuilding disk 3. disk 1 seems fine
November 18, 20241 yr Community Expert Solution This will only work if parity is still valid: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including the new disk3 -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk3 -Start array (in normal mode now) and post new diags.
November 18, 20241 yr Author Thanks for all your help. I am attaching new diags. I have performed New Config previously to restore a single redballed drive but not for such a case. I am guessing that I can now: - start the array again with disk3 - stop it - assign the new disk3 - start the array again & allow for the rebuild (why did I not think of that?) towerp-diagnostics-20241118-1853.zip
November 18, 20241 yr Community Expert Were those diagnostics taken with the array started in Normal mode?
November 18, 20241 yr Author Oh, sorry, I took diagnostics before the last step for me to look and I send those by mistake. Sorry for wasting you time. I have attached the correct ones with Array started in normal mode, disk 3 removed. towerp-diagnostics-20241118-1907.zip
November 18, 20241 yr Community Expert Stop the array, click on disk3, set the filesystem to xfs, start the array in maintenance mode and check filesystem, run it without -n
November 18, 20241 yr Author Here is the msg i get: Quote Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.
November 18, 20241 yr Author Here you are: 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 destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_fdblocks 2513625030, counted 2514633862 - 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 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - 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 = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 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 (1:412001) is ahead of log (1:2). Format log to cycle 4. done
November 18, 20241 yr Community Expert Now start the array in normal mode, the emulated disk should mount, if contents look OK you can rebuild.
November 20, 20241 yr Author Thanks a lot for the help and patience. Rebuild seems to be going fine. I learned some new stuff I had not encountered before. I was wondering, what in the diagnostics file lead you to the conclusion that I should check the disk 3 filesystem?
November 20, 20241 yr Community Expert 29 minutes ago, papnikol said: I was wondering, what in the diagnostics file lead you to the conclusion that I should check the disk 3 filesystem? This from the syslog: Nov 18 20:06:36 towerP kernel: XFS (md3p1): Mounting V5 Filesystem Nov 18 20:06:37 towerP kernel: XFS (md3p1): Corruption warning: Metadata has LSN (1:411948) ahead of current LSN (1:411861). Please unmount and run xfs_repair (>= v4.3) to resolve. md3p1 is disk3
November 20, 20241 yr Author Thanks again, I really appreciated your (and @itimpi's) willingness to help
November 21, 20241 yr Community Expert awesome, glad you were able to figure this one out. Best I can recommend is review the doc to potential learn more. https://docs.unraid.net/unraid-os/manual/storage-management/#drive-shows-as-unmountable
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.