ConnerVT

Members
  • Posts

    121
  • Joined

  • Last visited

Recent Profile Visitors

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

ConnerVT's Achievements

Apprentice

Apprentice (3/14)

29

Reputation

  1. I agree that it isn't a major factor in making a change. And let's hope, given the world's current economic issues, it stays that way. But for others that may read this thread, the reduction in power usage also bring less heat, noise and cabling. Perhaps a smaller sized power supply and/or case, or the elimination of a HBA or two. Just things to consider when spec'ing out a new build.
  2. Just read through your build thread. I touched on it in an earlier post, but you'll appreciate the reduction in power. My HGST drives are a bit power hungry. I keep 3 spinning all of the time (parity + 2 with video media) plus a NVMe (cache + appdata) and a SSD (usually idle - my transcode cache drive, until I kill it, it is ancient). The screenshot below is when sitting idle in this state. 56-64W. When all drive are spun up, and CPU busy, mid 90W. I have to max the system out to get it to pull 120W.
  3. The time to run the parity check scales pretty linearly with the size of the parity drive (as it is the largest). My system is similar in processing power to yours (if your siggy is correct_ - 1st Gen Ryzen 1700 to my 1500X gives you 2 more cores and the same everywhere else. With my 8TB drives and the system mostly idle (while running about a dozen dockers) a parity check runs about 14.5 hours. I've streamed Plex movies during a parity check (both Direct Play at home and hardware transcoded away) and had no issues (stuttering/pauses/etc). One month when I was doing this, the parity check time increased to about 16 hours. So it comes down to what activity is happening on the server when running a parity check, and does it have any meaningful impact to users. That a parity check may take longer, or a file transfer may take a little longer isn't worth worrying over. If video playback suffers, or other noticeably annoying behavior is observer, do some planning as to when you can schedule your parity checks for the least intrusive times. Even if it takes 12 days @ 2 hr/day really doesn't matter, as long as the maintenance task is done.
  4. No one ever came home after buying a new television and has said "I should have bought the smaller one." 😄 Buy as much storage as you anticipate you will use now, and in the future. Replacing all of those small drives with a few large ones will reduce your power consumption (and noise, and heat...) as well as reduce the number of points of failure. The Parity Tuning plug in works well. You can schedule parity checking to run during non-prime time hours if you do feel any impact.
  5. I have the 1350VA/810W version of this model. I cannot speak more highly of it. Plug and play with Unraid, handles both power loss and unstable voltages perfectly. My server coasts along most times at 60-70W of power draw, and could potentially get a bit over an hour of run time (though best practice is never run more than 50% battery capacity before shut down).
  6. Oh. My bad. I haven't been nagged to update the libraries for the new Plex agent since I downgraded for the OTA TV issue. But then, I haven't read a single good thing about Plex's new metadata agent, only people who had lost many custom updates, poor metadata matching to video files, and other complaints. Don't get me wrong - I love my Plex server. Just sometimes I smh at Plex itself. 😒
  7. I believe it is not recommended to update from within a docker. Limixserver.io updates their dockers pretty regularly, so I would think their latest docker would likely include the latest release of Plex. As for Plex itself, I'm not a big fan of quickly updating to their latest and greatest release. They have a bad habit of fixing/adding one thing, and breaking another feature. Just need spend some time in their forums (or Reddit /PLEX) to read the stories. I run a pretty old revision myself, as they broke my OTA TV streaming back during football season.
  8. It isn't as no one wants to answer your question. It is that it is impossible to answer, without knowing much more information, and then, it becomes a best guess. The devil is in the details. It is like answering the question, "I need to bring some stuff to a friend's house. What do I need to take it there?" Without knowing what you are bringing, or how far it need travel, the question can't be answered. Will it fit in your pocket? Is your friend far away? You may be able to walk it over to him, you may need to put it in your car, or you may need a semi-trailer truck. Without details, no one can begin to guess. There are basically 3 ways a media file gets sent to a display - Direst Play, Direct Stream, or Transcoded. Each has a different load that is put on the media server. Direct Play, Direct Stream, Transcoding Overview A modern smart 4K TV, using a native app, will direct play or stream most 4K media files without transcoding (those that don't are 4K files that may have been created with some uncommon methods). Your listed server hardware should be able to handle this easily, as it is basically just moving a file from one place (the server) to another (the TV). This is especially true if the TV (or display adapter such as an Apple 4K TV, Roku, etc) are connected to your network via wired LAN. It also applies if using WiFi, as long as the load on your WiFi isn't overloaded with other traffic. Transcoding does need more server work, as it is basically shrinking the file (compressing it) to be smaller, or into a different format. This is needed if you are sending the data over the internet (watching a movie at a friend's house) or to a TV or device that doesn't support the format the video file is encoded. Plex will do this either in software (by your CPU) or with external hardware (GPU + Plex Pass). Software encoding works fine, especially for 1 or 2 users at the same time (assuming light/normal server usage, not running a busy commercial web server or such). The i7-4790K, while an older CPU, should be enough for two people to easily watch Direct Play or Stream at home, or transcode the movies on the fly. A note, real time (on-the-fly) transcoding 4K down to a smaller resolution is *never* a pleasant thing to do, regardless of how much hardware you throw at the task. So it basically comes down to evaluating what display hardware you have, and how you plan to consume your media. Then you can evaluate what is needed in your server.
  9. My server has an old Kingston HyperX 3K. How old? It was the boot drive for my Windows XP daily driver PC. Been in several desktops and laptops since then. I use it as for the transcoding shares of my Plex and Unmanic dockers. Might as well run it until it dies, and in the mean time, it is fast and keeps the wear off my primary cache drive.
  10. Glad to hear you got things back up and running. It can be frustrating and scary when things run off the track like this. I agree with you on the BIOS updates, especially when it comes to Ryzen motherboards. It is great that AMD has stayed with one socket (AM4/TR4) through several generations of Ryzen, unlike Intel that basically requires you to buy both a processor and motherboard every time you wish to upgrade. But there is a downside to this as well. Many early motherboards were built with limited NVRAM for the BIOS. As new features appeared in later generation processors, there wasn't enough room to fit the growing AGESA as well as the other BIOS features. So some trimming of the code is done by the board manufacturer to support the new series of processors. This sometimes impacts the earlier CPUs, sometimes the BIOS feature/setting you may rely on disappears. I have found the sweet spot to be using the latest BIOS release *before* the release of next generation of the CPU you are using is the safest. Unless you really believe a later version has the cure for an issue you have been troubleshooting, It is best not to update. tl;dr - If it ain't broke, don't fix it.
  11. The temp/fan plugins are not at fault - Ryzen and Linux drivers are more the issue. Many of the SuperIO chips don't have Linux drivers written for them, as the chip's manufacturers don't supply decent documentation (when they do at all). There are work arounds, but all carry some sort of risk. I went down that rabbit hole a year ago, and chose to live without the fan control.
  12. I'm no expert, but perhaps a problem on the client side (as it only fails when attempting direct play)? Perhaps an update to the player or a recent settings change is affecting things? If you have other players that support TrueHD, you might wish to test with them as well.
  13. AliExpress. Won't be surprised there is no valid GUID.
  14. Shields Up! Will do a port scan from outside you LAN
  15. Went through this with my 1500X build. Since setting the PSU idle power in BIOS and setting RAM to the Ryzen default speeds appropriate for my memory (and pay attention to which single/dual rank RAM you have), my system as been rock solid stable. I never touched my c-states. YMMV