Jump to content

Michael_P

Members
  • Content Count

    169
  • Joined

  • Last visited

Community Reputation

15 Good

About Michael_P

  • Rank
    Advanced Member

Recent Profile Visitors

742 profile views
  1. 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.
  2. 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.
  3. Bent pin in the CPU socket could knock out a bank, too - ask me how I know :)
  4. You could try re-seating the RAM, or try the stick throwing errors in another slot
  5. 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.
  6. Shove the traffic onto 443 or wrap it with something like Stunnel
  7. Set up a VPN end point inside your network, something like:
  8. 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)
  9. 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
  10. 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.
  11. 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.
  12. 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.
  13. What throughput are you getting now? That small of a pool will probably not benefit from moving to an HBA
  14. 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