BVD

Idk what in doing differently, but I've yet to have a drive fail that wasn't either my fault, or almost immediately upon installation for years now. I always buy the enterprise line (WD gold, Seagate exos, etc), and they're always installed in dedicated hotswap bays in server chassis, but I've got something approaching 80k hours on a good number of em 🤷‍♂️

I'd recommend heading to the code repo for answers specific to the application (as opposed to the container, which is just packaging the application) - looks like there's quite a bit out there discussing this, with a short search showing the below as examples: https://github.com/arsenetar/dupeguru/issues/571 https://github.com/arsenetar/dupeguru/issues/730

Some would call me cheap - myself, I prefer "Thrifty" 😝

It's both cheaper,*AND* can actually be used as a computer! All on its own even! 🤣

@gyto6 very nice!!! I ended up ordering one of the upcoming framework desktop configs with the maxed out RAM to handle all the AI tom-foolery I'm planning to play with - only way I could find to do it all without both spending a fortune and refrain from supporting nvidia 😅

@facile-soot3303 I'm still not following - trim is disabled, I understand that, but what's the screenshot supposed to show? How can we help?

@hernandito just wanted to come back here once more to thank you for the service you've provided to the community - truly, it's been fantastic, and while it may seem small to some, the level of personalization it's allowed us to sprinkle in is sincerely appreciated. Brings a smile any time I get a comment on my dashboard, and just this evening, my oldest sat down with me to do some software maintenance together. What caught his eye first? Your icons, OF COURSE!! ❤️

@facile-soot3303 I'm glad to hear things are going well - I'm just not sure I follow what you're trying to say, could be a language barrier on my side...? While these changes may be suitable for your configuration, they certainly wouldn't be ones I'd recommend all apply without verifying it's necessary for their config. For example, I'm assuming that given you've went with kernel task priority, this is probably for drives within an array? It'll behave quite differently in a pool all it's own of course. Regardless, happy to hear you're making progress in whatever testing you've undertaken, congrats!

Only the MB manual would be able to answer that one unfortunately, sorry!

Anything that's *purely* sr-iov would follow the same process - most GPUs, however, would typically have their own unique implementation of the tech (from the manufacturer, amd/ngreedia/Intel), requiring tweaks to the steps unfortunately. I believe at least some of the older AMD workstation cards followed the raw spec to the letter, but I've not worked with GPU partitioning regularly for some time now, sorry to say 😞

Every Maxtor I ever worked with, you could fry eggs on 🤣 What I really want to mention though - if your drives are anywhere *near* 48°C, you've got a significant cooling / airflow problem, and I'd recommend looking in to it sooner rather than later. ~50°C is fine for NAND/SSDs/NVME, no worries there. But HDDs become significantly less happy the further above 40C they run.

I have mine going to a zfs fileset with zstd-5 compression configured - heavy compression usually reaps significant benefits for time series data, and totally worth the (relatively small, at least in my experience, and with a modern processor) performance tradeoff.

@T_Matz You would need to edit the actual dashboard file itself to remove those panels completely, opening the .json file and removing the corresponding lines

@UncleStu What do the Telegraf logs show? Should give an indication as to what's going on. You may need to update telegraf, and the logs there should indicate what perms issues need to be addressed as well actually 👍

You can always trim down the number of panels to suit your specific requirements. It is Plex only - if someone wanted to pull emby/jellyfin/(etc), you'd need to have a separate set of requirements since the API calls necessary to collect the data (and the applications which are responding to those calls) would be separate for each. Kind of an aside, but I think it's worth at least mentioning for anyone coming in to this fresh - I'd be willing to bet @falconexe has invested several hundred hours in to this over the years, so even if it only takes someone ~5% of the total "from-scratch" creation time to tweak it to match their specific combination of server + storage + containers + share config + (all the things)... Most should probably expect a needing a handful of evenings of dedicated effort to get the dashboard up to a fully functional state. (extra random thoughts, hoping 'spoiler'-ing it keeps this post from being too long unless someone clicks on it lol)