May 14May 14 A friend of mine gave me his unRAID server (v6.12.13) because he was having problems with it. I guess he was screwing around trying to get it to work, and ended up messing it up.He said the parity drive was offline or "something" so he started trying to move disks around. To be honest, he isn't much help on what happened.If I replace the missing disk with a new 6TB drive, will the array rebuild itself? It's showing that the Parity drive is disabled and that a wrong disk is installed. It shows that the other two disks are correct and that the 3rd disk will be "Emulated". I'm wondering if I just assign the wrong disk to disk 2, it will rebuild itself, but I don't want to do that until someone smarter than myself gives me the go ahead. Thank you! tower2-diagnostics-20260514-0927.zip
May 14May 14 Community Expert There are two invalid disks with single parity, so it's not possible to recover the array as is. If you still have the missing disk2 you can then resync parity; if not, you will likely lose the data from disk2, in case it's important.
May 15May 15 Author I found the 744JSS disk and installed it, but I think it's dead. I swapped it into the SATA port of a working disk and it's still saying that it is Missing.Logs attached with 744JSS installed, but not appearing as a device.Thank you! tower2-diagnostics-20260515-1618.zip
May 15May 15 Community Expert Probably parity was already disabled when the other disk failed. So likely it isn't valid. But maybe we could try to trust parity and see if we could get anywhere trying to emulate the missing disk.Go to Tools - New Config - Retain All - Apply.Assign disk2.Very important. Check BOTH the Parity Valid box and the Maintenance Mode box, then start the array.Stop the array, unassign disk2, then start the array in normal (not maintenance) mode, with nothing assigned as disk2.Then post diagnostics
May 15May 15 Author Thank you for your response. I just want to make sure I understand. You want me install a replacement disk in the Disk 2 spot because it isn't seeing the 744JSS drive regardless of what SATA port I use, so I'm guessing it's dead.So:-Install replacement disk-Tools -> New Config -> Retain All -> Apply-Assign replacement disk to Disk 2 slot-Check Maintenance Mode and Parity Valid and start the array-Stop the array, set disk 2 to unassigned and then start the array without checking the Parity Valid or Maintenance Mode boxI go to that part and stopped because I'm seeing a big warning next to the parity drive that says "All existing data on this device will be OVERWRITTEN when the array is started".
May 15May 15 Community Expert 14 minutes ago, Spyderturbo007 said:I go to that partAssuming you mean this part16 minutes ago, Spyderturbo007 said:Check Maintenance Mode and Parity Valid and start the arraythe warning is incorrect since the parity valid box is checked.If that is not what you mean, explain further.
May 15May 15 Author Thank you so much @trurl , I think that worked! What do I do now? I have a replacement 6TB drive and a new 8TB drive that I can use for anything needed. New logs attached. tower2-diagnostics-20260515-1709.zip
May 15May 15 Community Expert Your screenshot is clipped on the right where it is telling you the important information. Emulated disk2 is unmountable, so we can't access its filesystem (yet).Unfortunately, it doesn't know what filesystem disk2 is supposed to be. Default for array disks is XFS, and that is what disks 1, 3 are. Unless you know differently we will assume disk2 is also supposed to be XFS.Stop the array, click on emulated (missing) disk2 to get to its page, set File system type to xfs, start the array with nothing assigned as disk2, and post new diagnostics.
May 15May 15 Author I changed it to XFS and then started the array, but it still shows "Unmountable" for disk 2 that's being emulated.Thank you SO MUCH for your help! tower2-diagnostics-20260515-1723.zip
May 15May 15 Community Expert Stop the array and start it in Maintenance mode so you cancheck filesystem on emulated disk2 from the webUI and post the output.
May 18May 18 Author Hi @trurl Sorry for the delay, the server is in my office and I was at home over the weekend. I'm attaching the output as a .txt file because it's huge. Once again, thank you for your help! Check Filesystem Status.txt
May 18May 18 Community Expert 39 minutes ago, JorgeB said:Click the FIX button, then start in normal mode and see how it looks.then post new diagnostics
May 18May 18 Author Unfortunately, I don't see a fix button. At the bottom of the log is a button that says "Check" and then a -n in the options line.At the top I have "Done" which takes me back to the Main page and then Erase, which I haven't clicked. I stopped the array and looked for it in regular mode, but I don't see it there either.
May 18May 18 Community Expert Sounds like you are running an older version of Unraid from before the Fix button was introduced? Remove the -n (which is the no modify flag) and run check again.
May 18May 18 Author It's on v6.12.13 right now. I guess this happened sometime in 2024 and he never did anything with it.Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: mismatched uuid in log SB : f993b396-6125-459e-83e1-9336207af746 * log: dab9dcc7-f000-49b2-b4fe-8778b80fa0d1 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.
May 18May 18 Author Thank you! Here is what I got:Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: mismatched uuid in log SB : f993b396-6125-459e-83e1-9336207af746 * log: dab9dcc7-f000-49b2-b4fe-8778b80fa0d1 ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. xfs_repair: libxfs_device_zero write failed: Input/output error
May 18May 18 Community Expert 31 minutes ago, Spyderturbo007 said:write failed: Input/output errorThis typically means a disk error. Post the diags after running the repair and before rebooting.
May 18May 18 Author There is no repair option. This isn't a real disk, it's an emulated disk. I have a spare 6TB drive I can use if needed.
May 19May 19 Community Expert 12 hours ago, Spyderturbo007 said:There is no repair option.With that release, the repair option is when you run check without -n.
May 19May 19 Author I'm not sure if I got this right or not. I ran it one time with no options and got this: There was a lot more to it, but this was the end.etadata corruption detected at 0x453030, xfs_bmbt block 0x23d50b7d8/0x1000 libxfs_bwrite: write verifier failed on xfs_bmbt bno 0x23d50b7d8/0x8 Metadata corruption detected at 0x453030, xfs_bmbt block 0x23d9c42d8/0x1000 libxfs_bwrite: write verifier failed on xfs_bmbt bno 0x23d9c42d8/0x8 Metadata corruption detected at 0x453030, xfs_bmbt block 0x71a09320/0x1000 libxfs_bwrite: write verifier failed on xfs_bmbt bno 0x71a09320/0x8 Metadata corruption detected at 0x453030, xfs_bmbt block 0x3e26eb38/0x1000 libxfs_bwrite: write verifier failed on xfs_bmbt bno 0x3e26eb38/0x8 Maximum metadata LSN (2079689086:1598493115) is ahead of log (0:0). Format log to cycle 2079689089. xfs_repair: Releasing dirty buffer to free list! xfs_repair: Releasing dirty buffer to free list! xfs_repair: Releasing dirty buffer to free list! xfs_repair: Releasing dirty buffer to free list! cache_purge: shake on cache 0x50c560 left 18 nodes!? xfs_repair: Refusing to write a corrupt buffer to the data device! xfs_repair: Lost a write to the data device! fatal error -- File system metadata writeout failed, err=117. Re-run xfs_repair.It said Ru-run xfs_repair, so I did and got this:Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - 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 = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 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... doneDiagnostics before a reboot and after the 2nd run with no options are attached.Thank you for sticking with me on this!tower2-diagnostics-20260519-0753.zip Edited May 19May 19 by Spyderturbo007
May 19May 19 Author I started the array after rebooting and got this: Edited May 19May 19 by Spyderturbo007
May 19May 19 Community Expert Emulated disk mounted, which is good, check contents to see if they look OK, also look for a lost+found folder.
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.