albertogomcas

Which is not great either, at that pace that drive is going to bite the dust in less than a year...

I believe there is a general problem of writes being amplified (easily x10). Since plex (especially some flavors of the docker) writes a lot, this can become the most visible. I actually reached the same conclusion than you when I started investigating. But then I had a hard look at the other dockers and still there is way too much writing (In your case half a GB in half an hour may not sound much, but is still 4TB a year for doing... nearly nothing?)

For the record I have this similar problem and was googling around these forums, reddit... and plex forums. In my case, the official plex docker is the clear culprit, stopping it practically starves the loop2. Installing other alternatives (linuxserver) radically lowers the amount of writes. https://www.reddit.com/r/unRAID/comments/ea85gc/high_disk_writes_with_official_plex_docker_in/ https://forums.plex.tv/t/pms-docker-unraid-is-constantly-writing-to-its-docker-home-library/419895 Now the numbers: (from iotop -oa -d 60 and collect 1 minute), I start the respective docker a couple minutes beforehand to discount spawning read/writes No plex docker active: 58M Writen by loop2 => 81 GB/day Official plex running: 387M Writen by loop2 => 0.5 TB/day linuxserver/plex running: 36M Written by loop2 => 50 GB/day (Clearly there are other things writing around meanwhile, but there is a comfortable factor ~10 difference by not using the official plex docker. So, I advice everybody to check their cache usage if using plex, and possibly gain years of life on your SSDs. You can simply point to the old appdata folder in the advanced docker configuration to save reconfiguring and watch progress. I imagine is a very good idea to NOT have both dockers running at the same time (I have and will not try). (I would also advice unraid devs to place some kind of warning regarding these kind SSD killer issues?).