Spyderturbo007

Right now, I'm running an older SuperMicro server that never spins down the fans. There are 7 fans in there running at 3,500rpm all day long, even when all the drives are spun down. Apparently it's an known issue with the H8DGU board. Now that my electric bill keeps going up and up, I was looking for lower power options. Does anyone run a higher drive count server that's low power? I'm not even sure what's reasonable when it comes to power draw. The current server is 4U, has 32 drive bays and is currently running: 2 x AMD Opeteron 6380 64GB Memory 20 x 3.5" drives set to spin up individually and spin down when not in use. 3 x SSDs NVIDIA Quadro P620 2 x 1400w redundant power supplies It's primary use is Emby and unless I'm doing a parity check, it rarely spins up more than a couple drives if we are all watching separate movies. I haven't put a meter on it yet, so I can't even say where I'm at right now, but with all those fans spinning 24/7, it can't be low. I forgot that my UPS shows usage. I have one power supply plugged into the UPS right now, because oddly the other failed yesterday, and it's showing 385 watts. I have a replacement on order.

I think I'm all set. I replaced the parity disk and the parity check shows as completed with 0 errors. Thank you so much @trurl and @JorgeB ! I'm going to try and tackle the upgrade to 7.3.0 now and see how that goes. Fingers crossed!

@trurl Here is what I got. Last SMART test result: Completed: read failure WDC_WD60EFRX-68L0BN1_WD-WX11D37444PZ-20260522-0937.txt # 1 Extended offline Completed: read failure 30% 35746 3477753040 # 2 Extended offline Completed: read failure 90% 35738 3547641224

I replaced the disk and it did the rebuild, but it looks like there might be some issues with the Parity drive. It's showing 230,000+ errors. I have an 8TB drive that I can swap in it's place, which is something I wanted to do anyway. How do I resolve the issue with the parity drive? There were a ton of these errors, but I ran the short SMART test (attached) on the drive and it said it was fine. 20-05-2026 19:53 Unraid Parity disk SMART health [197] Warning [TOWER2] - current pending sector is 122 WDC_WD60EFRX-68L0BN1_WD-WX11D37444PZ (sde) warning 20-05-2026 19:53 Unraid Parity disk SMART health [1] Warning [TOWER2] - raw read error rate (failing now) is 6572 WDC_WD60EFRX-68L0BN1_WD-WX11D37444PZ (sde) warning Thank you! WDC_WD60EFRX-68L0BN1_WD-WX11D37444PZ-20260521-0811.txt tower2-diagnostics-20260521-0819.zip

Can I just swap in a new drive in the disk 2 slot and will it rebuild the data now that it seems to be emulating correctly?

The main folder is named 2018 and contains 195GB of data, which appears to be good. There is a lost+found folder with 1170 files. He said if that's all he lost, he'd be just fine with it. But obviously if we can get it back, that would be great. If not, I'd just like to learn how to rebuild the disk and get it working again. Thank you!

I started the array after rebooting and got this:

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

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.

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

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.

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.

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

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

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