Feanux

Members
  • Posts

    8
  • Joined

  • Last visited

Feanux's Achievements

Noob

Noob (1/14)

0

Reputation

  1. It was absolutely the PSU. I swapped the old one out and followed the steps to do the parity-sync and it completed on the first try without errors. I would have thought that more drives would have been affected if the PSU was failing because the parity was in a daisy-chain of other drives. To be safer in the future I put the parity on its own dedicated line and also split the remaining 4 drives into 2 separate lines. Here are the healthy diagnostics. Thanks again for the help @trurl! hms-diagnostics-20231106-1006.zip
  2. Good call on the power, the PSU might actually be pretty old so I can definitely see that being an issue. I ordered a Seasonic Focus GX-750 and it should be here tomorrow. I'll get it hooked up, try the parity check again and see what we get. If that doesn't resolve the issue and I've swapped the SATA cable and the port on the MB it could either be the MB failing (least likely) or the drive (most likely) in that scenario, right?
  3. Thanks for the info @itimpi! Just to clarify, in the documentation I want to follow the steps for "Reset the array configuration" (and keeping the Pool config), correct? I have already tried to rebuild the parity drive by stopping the array, unassigning parity, starting array, stopping array, reassigned parity, started, checked/sycned. This process never fully completed and failed about 1/3 of the way through as well.
  4. About a week ago I noticed my Parity drive no longer showed in Unraid. I restarted the server, confirmed the drive still showed in the BIOS, and when I booted back into Unraid the drive showed up but in a disabled state. I ran a SMART extended test that came back with no errors. When I try a parity check the process never fully completes, it either pauses or states that it completed with no errors but the full disk is never checked and the parity stays disabled. I've replaced the SATA cable and also connected the drive to another port on the motherboard. All other drives seem to be working fine. I'm unsure of where to go from here, any help would be super appreciated. hms-diagnostics-20231101-0707.zip
  5. First, I want to apologize for the picture. I know snipping and ShareX are a thing but at the time the laptop I was on was.... antiquated. It just stays here.
  6. Thanks, I'll get on that. In regards to the issue - I know I didn't setup the new cache correctly and that's likely why it's not working. I still have the old cache drive available but when I select it in the Unraid GUI it tells me it's going to wipe the drive. Which leads me to my question: Could I just power of the server, grab both the new and old drive, clone the old drive to the new drive using something like Macirum Reflect, reinstall only the new drive? Or is there maybe a better way to "try again" for installing the new cache drive (except correctly this time).
  7. Oh, balls, thanks for noticing. I set "Use cache pool" to "Only" and "Select cache pool" to "Cache" for my system share settings. Once Mover is invoked it should move them off disk3, right?
  8. I'll try to be brief with the story but the gist of it is that I cannot install new containers, they always hang during the pull. Events that lead up to where I am: Installed a new cache drive Forgot to stop/turn off Docker services Used rsync to move all data from old cache to new cache. Selected new Cache drive in Unraid Docker wasn't working, no containers appeared Stopped Docker services, rsync'd again. Enabled Docker Docker worked fine for a bit but Plex became inoperable Deleted/recreated Docker image Tried to reinstall Plex, couldn't Tried to install any Docker container, can't, hangs when pulling images I've attached the diagnostics, not too sure where to go from here. hms-diagnostics-20220808-1452.zip