Michael_P

Members
  • Posts

    661
  • Joined

  • Last visited

Everything posted by Michael_P

  1. The total power that the supply can provide isn't as important as what the limit of the current the connector/wire can sustain. That's what was tripping me up, too.
  2. How many drives are hanging of of each molex connector? From my experience: I have a Norco 24 bay case, 4 drives per backplane and 6 backplanes total. My Power supply had 4 molex connectors, so I split 2 off to get the needed power. Everything worked fine with 14 drives, but if I added a 15th outside of the array and assigned to my WHS VM with my WHS VM running, every parity check would fail random drives for read errors, and then shortly after the drives would show pending sectors. If I stopped the WHS VM before starting the parity check, it would finish no problem. I was certain it was the Toshiba drives I was using. Every drive was stable as stable could be, as long as I didn't do a parity check with the VM running. I went probably few months or so, then I forgot about the parity check so my VM was still running when it started and I get the email a drive has dropped. At this point, I'm just ready to stop doing parity checks altogether, and went a couple months without one - until I stumbled on a thread about shitty splitters and a light bulb went off in my head. It's power. The drives aren't getting enough during load even tho the power supply is more than capable of delivering, with more than 4 drives on a connector it was sagging just enough to reset. I ordered some molex punchdown connectors on ebay, took one of the extra SATA lines that came with the power supply and created another molex string. Haven't had an issue since (knock on wood).
  3. FWIW- I had random drives throwing errors when I had too many on one string to the PSU, different ones each time, so could very well be flaky power
  4. If you're not using the bells and whistles Unraid provides, and you're just looking for up-time resilience (RAID 1) - you're probably better off with something like the My Book Duo. If you don't need resilience, just get a My Book or similar enclosure and plug it into your router - most newer models have USB ports for sharing out drives and acting as a NAS device. No sense building a machine for it, those portable drives use probably less than 10 watts idle.
  5. Disk 1 is on its last legs too I'd RMA the disk with reallocated sectors, especially since it has 820 after only 2 hours
  6. https://wiki.unraid.net/Transferring_Files_Within_the_unRAID_Server
  7. How many on 1 cable back to the PSU?
  8. The CRC errors for disk 1 don't look bad, it's the reallocated sectors for your parity disk VKK45Z3Y that would concern me
  9. yep, unraid only has 1 local account, root
  10. Depends on how much data you're transferring on a regular basis, and the size of the files. Writes of a lot of small files wouldn't see much of an improvement, but large writes would. Also, your transfer speeds would be limited by the write performance of your SSDs - saturating a 10G link isn't as easy as it sounds, bursts are great, but sustained is where the money is.
  11. I've been using Subsonic for 10 years now, one of the few reasons I keep my WHS running in a VM. It just works.
  12. Bent pin in the CPU socket could knock out a bank, too - ask me how I know :)
  13. You could try re-seating the RAM, or try the stick throwing errors in another slot
  14. Pending sectors are an automatic replace drive error for me, especially if under warranty. If your risk tolerance is higher than mine, continue to monitor the number - if it rises, bin it. If those pending sectors go un-correctable, bin it.
  15. Shove the traffic onto 443 or wrap it with something like Stunnel
  16. Set up a VPN end point inside your network, something like:
  17. A lot of the CPU usage is motion detection, 4k streams have a lot of pixels to compare and blue iris is very good at it - the in-camera's ASIC is faster, but more prone to false alerts (shadows, leaves, bugs)
  18. Blue Iris eats CPUs for breakfast and RAM for lunch. On my i7-8700 / 32GB system I have 2 cores/4 threads and 12GB of RAM dedicated to my W10 Blue Iris VM along with the iGPU. Those cores idle around 50%, and 70% while viewing the 10 cameras tiled remotely via UI3 in a browser, 40-50% if only viewing 1. That is after optimizing the devil out of Blue Iris. I Tested a few different configurations in my particular setup, 2 cores and 12GB was the sweet spot. More cores/threads and less RAM was significantly worse, so if you plan on doing anything else on the server, add more RAM
  19. If you have one 12TB parity and another 8TB parity your data drives would be limited to 8TB maximum each - data drives cannot be larger than either parity drive. You would need to upgrade the 8TB parity drive before adding larger data drives.
  20. When I migrated from Windows Home Server to Unraid, I just moved the WHS box into a VM. It still hums along backing up my local machines and managing my WMC storage.
  21. Yeah, that's the problem with Ebay, Amazon too sometimes. I had good luck with my HBAs on Ebay, but got my expander from Newegg I just slapped the fan on top. Wasn't terribly concerned with heat, just figured couldn't hurt to have a bit of air on it. If I see a heat sink, I have a compulsion to slap a fan on it.
  22. What throughput are you getting now? That small of a pool will probably not benefit from moving to an HBA
  23. Access to the server isn't affected at all, drive maps and all that will still work - just when you go to to network it won't show up in the list. If you type the name in the address bar you can browse to it as normal. It's an inconvenience thing, really. Restarting the server will restart the WSDD service, but eventually it will bug out again. Best bet is to pin the server under favorites in explorer in your Windows 10 client and just disable WSDD. Here's the procedure for replacing the cache drive: https://wiki.unraid.net/Replace_A_Cache_Drive