• Content Count

  • Joined

  • Last visited

Community Reputation

9 Neutral

About ConnerVT

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. My server is a bit of a lightweight - 4-core 1st gen Ryzen with 21TB in the array. Built from recycled and new parts, it's main purpose is to offload the Plex media server off my daily driver. It also is a place to store backups from the daily driver, as Windows Update seems to bugger everything up ever 4-6 months. (Thanks Micro$oft) It has also been a fun project to learn some new stuff. Lots of docker loaded, but no VMs yet. May load a MacOS later this year, just to mess around with. Plex Server (nVidia Quadro P400 for hardware transcodes) - Just fa
  2. This is what I thought. But I've been known not to ask about such things, only to find there was some easy fix to remedy it. Thanks for your input.
  3. The smi always reports fan speed at 34% and N/A for the power. I don't know if the fan actually changes speed on the card, as I don't spend much time watching the innards of the server. I know if there is something funky going on, it is more likely an issue with the nvidia driver than anything else. But folks coming into this thread are more likely to notice their fan speed reporting (or not), so just trying to confirm if this is something down for everybody, or just me.
  4. Thank you for the useful plug in. For the most part, works great. NVIDIA P400. Is it just me, or does anyone else not have it reporting Fan Usage and Power Draw?
  5. ^ This The difference in price between 2x4GB vs 2x8GB kits is minimal. But if when you decide to upgrade to more memory, it is better to be at 2x8GB than 4x4GB for performance reasons, and a 2x8GB kit can be more easily re-purposed if needed. 2x4GB will end up in a spare parts bin.
  6. For transcoding only, no benefit to buy the the more expensive P620. I picked up a PNY Quadro P400 for my system for ~$125, works great for my family's PLEX server.
  7. It comes down to whether the device you are playing the video on can Direct Play the file or not. Many modern TVs and media clients play HVEC natively, so the Plex server does not need to transcode. An Atom can pass a file easily. But if the file needs to be transcoded, either because the device can't Direct Play the format, or you are compressing it down so it can be sent over the Internet to your mobile device away from home, then the advice Hoopster gave you above is valid.
  8. Good deal. As I noted initially, there really isn't much room for savings when you are already at 70W. And how much you can find really depends on your hardware (your drives look to be around 5W spinning and idle - my HGST are more power hungry, around 8W each).
  9. Main tab. Green dot is spun up, grey is spun down. Spun up drive will also show the disk temp. Click on the dot to spin up/down that disk. Click on the arrows below, to spin all up/down.
  10. Late to the reply, but don't visit this sub-forum often. 70W is a fairly low draw. You didn't say what is going on at the time (drives spun up or not, activity, etc) so it is hard to gauge where to go from here. As you have 5 spinning drives (4 + parity), the #1 controllable thing is to keep drives spun down as much as possible. Each at idle is ~8W of power. This is a challenge when running VMs and Dockers, as each of these seem to always want to access a disk for something. Moving as much of their working files to cache/ssd as possible (and using cache f
  11. Ah! You guys are awesome! You answered both of my questions. I needed to go back further in my brain, to remember what I did. There was originally a Disk 4 (along with the Parity 2) in my array. I moved the data that was on it to the other disks, and pulled it out of the swap bay, to keep in cold storage in case I needed it in the future (for good or bad reasons). That's when I changed the Global Share settings. That was about a month ago. The Parity 2 drive is buried inside the tower case, so just configured it to the array, so not to mess with any cabling. I ha
  12. I don't how I did this. Worse, I'm unsure how to un-do it. Running 6.9.1. Disk 4 was my Parity 2 (put it to work, just to test things out). A few days ago, I reconfigured it to be Disk 4 in my array. All seemed to go without issue. I did a parity rebuild, and everything seems to be working without any problems. Just now, I was looking through the server, and noticed on the Shares tab that Disk 4 is listed as a share (currently has no data on it at all). This can't be correct. How do I remove this share?
  13. I see the same here, running 6.9.1. Same device as well - Samsung_Flash_Drive_FIT
  14. Agree. My server loads my 1350VA UPS an average of ~ 10%, giving me a reported run time of about 60 minutes. I'm setup to start a shutdown after 12.5 minutes, which is long enough to handle any unannounced "planned" outages. (Where the power co. need to switch off an area to service some equipment, the typical reason I may lose power.) I don't have my server power back up after shut down, as it isn't mission critical, and is on site at home. I also have it configured to shut down at 50% battery capacity (if multiple outages less than 12.5 min occur) or if less than 10 minutes o
  15. Exactly. Though I've read some mixed thoughts as if it is 100% resolved in Zen+ and Zen 2. But that's to be expected on the Internet. As Power Supply Idle Control has no cost other than perhaps a negligible amount of power draw, it is worth checking off the list.