Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About brainbone

  • Rank
    Advanced Member


  • Gender
  1. Letting the GPU handle decoding/encoding leaves your CPU open for other work. Generally, the encodes from a GPU (hardware encoder) will be lower quality than the encodes from the CPU (when using x264), though newer generation hardware encoders are starting to close this gap. (the K10 does not have a newer generation hardware encoder.) If you have a powerful enough CPU to keep up with the transcodes being requested and everything else being requested of your unraid server, you'll likely see no real benefit with a hardware encoder. "Unraid Nvidia" lets you use the GPU with Plex/Emby/etc. dockers. See this list for what you can expect in Plex. The K10 isn't included in that list, but if it works at all, I'd expect it to perform something like the other GK104's No experience with any of the Tesla cards, but how useful it will be depends on your specific use case. I use a Quadro P400 for nvenc/nvdec in my Plex Docker, leaving my CPU (and GTX 1080) open for use with a gaming VM. For me, it was worth the time involved passing the 1080 GTX through to my gaming VM, and using Unraid Nvidia to offload Plex transcoding to the P400. Allows me to dedicate more CPU cores to the Gaming VM.
  2. I just use a second NVMe for transcoding and other stuff that makes more sense on a scratch disk. This saves some endurance and bandwidth on the main cache SSD, where I'd rather not have its appdata and domains mounts go down, and leaves ram open for more useful endeavors like VMs, dockers, read cache, etc. If you're confident you don't need a huge amount of space for transcodes / scratch disk, a 64GB (or even 32GB, if you don't have that many plex clients) intel Optane will have much higher endurance than a typical NVMe. However, I just use a pair of 500GB 970 EVOs -- one for a standard cache drive + docker/vm storage, the other for transcode/scratch. I'll likely need to replace them every 3 to 5 years.
  3. Yikes! I'm behind the curve here. I updated to 6.7.2 from 6.6.6 a few days ago, before seeing this information. I've not yet had any corruption, but I'm a little worried. Glancing over this and related threads, so far it seems like only those storing SQLite DBs directly on disk rather than on SSD/Cache are seeing this issue. Is that correct, or are there reports of people storing appdata on cache with this issue? Having all my dockers in appdata, and having appdata set to cache only, am I immune to this issue, or should I roll back to 6.6.7?
  4. Please edit or delete that last post. The first post in this thread forbids talking about that!
  5. Make sure you pay attention to what's highlighted in green/yes. The 1030, for example, is a GPU you should NOT get. This list has more detailed information on GPUs with Plex.
  6. I'm not exactly sure how much extra power my GTX 1050 is chewing sitting idle without being in a power saving mode, but my guess (based on readings from a "Kill A Watt" with the GTX installed vs. not.) is around 15 to 20 watts. 15 to 20w x $0.15 per kwh = ~ $20 to $25 per year. I'd certainly be willing to donate at least that much towards getting this done.
  7. I think I'm seeing this same issue. When mover is running, Plex is for the most part frozen. Happened both before and after installing an old Geforce 1050 (using Unraid-Nvidia) for transcoding, so it seems unrelated to Unraid Nvidia. I'm not certain if this happened before I upgraded to 6.7.0 as I seldom manually ran the mover when I was on 6.5.x -- though I don't recall it happening before the upgrade to 6.7.0.
  8. Is there a way to throttle the mover so it doesn't saturate the unraid array while moving data from SSD cache to the array?
  9. Seeing negative/wrong MB/CPU temps on dashboard on unraid 6.7.0 / Dynamix System Temperature 2019.01.12a Any idea what I'm doing wrong? (See attached:)
  10. I'd like an option for critical and warning thresholds for low HDD temperature in addition to high. Due to server location (by an air-intake vent), I noticed my HDD temps had dropped to ~ -19°C as outdoor temperatures fell to -33°C. Also, it would be helpful to have an option to keep the array spun up if any single HDD or SDD is below a specified "keep spun up" temperature threshold.
  11. Exactly. Hence my concern. I've resorted to taping up the vents on the case and keeping all drives spun up. Currently have them at around 55°F (~ 13°C). I'll need to find a permanent solution, though my preferred solution would be to shut off select (in my case, all) chassis fans based on HDD temp, however keeping the array spun up is also needed. An unraid feature to force spinup when HDD temps are too low would be nice, however since temperature isn't available when they are spun down, it could be difficult to implement/use, requiring at least one HDD or an SSD be kept spinning as a canary. Low temp alerts in addition to high temp alerts would also be nice. (Guess I'll go create a feature request for these.)
  12. Just like we used to do on extremely code days for car radiators eh? (I'm now using a sheet of plastic, since cardboard is too flammable to have that close to a boiler -- but the temps are still are still pretty cold @~40°F. I'll probably need to add some tape!) I'd like to avoid adding more hardware, but you're probably right. I may need to add a separate fan speed controller.
  13. Any way to get Autofan to control more than one PWM controller and/or fan? I run one of my servers in a boiler room, next to the fresh-air intake. (Yeah, Yeah, but it is what it is.) This works great most of the time, since when the boiler runs, the make-up air from the fresh-air intake nicely cools down the server, offsetting the heat from the boiler room. Problem is, when it's -27°F (~ -33°C) outside, like it is today, the HDDs are running at 19°F (just spun up) to 28°F (spinning) (~ -7°C to -2°C), which is probably way too cold to run these HDDs. I have multiple chassis fans. I'd like to automatically spin all of them down when it's this cold. If any chassis fan is running, even the exhaust fans, too much cold air is pulled in.
  14. The is a critical enough issue where you really should remove 6.6.4 from the stable release category.
  15. If you're not running a cache drive mirrored, yet expect data on the cache drive to be flushed to your protected drive pool nightly, but then a week down the line your unprotected cache drive dies, everything you expected to have been flushed to the protected drive pool but wasn't is now lost. I would call that data loss.