Liteon ssd health check update#

The first step is to run the inotifywait command from mgutt: There are a few basic places writes come from with docker and each has it's own fix. Generally the first 3 or 4 characters are enough to find the right container. To match up a long container ID with container in unraid GUI, simply use crtl+f to search the docker page in unraid for the container ID you see in the activity logs. Section of the docker template in unraid (you will need to go to the advanced view in the top right corner) Part 2: Docker logs causing write inflationĪll the docker commands I will put below need to be entered into the The excessive writes still persist as you see just to a lesser extent after this, the remaining writes will be dependent on what dockers you are using and is an issue with docker. This dropped my writes to around ~75-85gb/day using a single BTRFS formatted drive with BTRFS image.įormatted as XFS with BTRFS image my writes dropped to ~25gb/day but you can't have redundancy then and has it's own issues. It fixes some partition and mounting issues with the filesystem.Īfter that move the data back to the cache from the array. This fixes the core unraid side of the excessive writes.

You will then erase the cache pool using the built in erase option and reformat it when you restart the array.

Liteon ssd health check update#

The first step to reducing writes is to update to upraid 6.9+ and then move all the data off your cache SSD's to the array temporarily. ~200gb+/day IIRC (forgot exact numbers and lot my notes from that long ago but it was a LOT) My writes when starting this journey with far less dockers then I have now was around : To the point it has killed a number of SSD's in a very short amount of time and used up a hefty amount of the life of many other drives.īut instead of reading all that I am going to give you the results of all the testing that went on in that thread. Ok, so as many have started to realize unraid had a serious issue with massively inflated writes to the cache SSD for the last few years. Honestly it is a good excuse to update your complete backup. I would recommend getting a fresh backup of your cache drive and docker/appdata before starting any of this, just in case.

To start out with, this is just a journal of my own experiences dealing with these writes, you do any and all of these commands at your own risk! Always make a backup of any data/drives you will be messing with.