lattimershotgun

So I took out the drive that was supposedly bad and replaced it with a new drive and it get the same Red X. I then replaced the sata cable and still no luck. I doubt the new drive is also bad so I think this is somehow software related and not hardware related. If I attempt to preclear the new disk I also get an error. Any ideas? ST20000NT001-3LT101_ZVTHDANB-20241213-2230.txt nas-diagnostics-20241213-2249.zip

I am thinking what is happening is the actual sata cable went to garbage. The old disk and new disk both have errors as soon as I put it in PC. I am thinking a bad cable so I am replacing the cable and seeing what happens. I have had cables go bad in the past or get loose and cause issues. So fingers crossed!

So I had a parity drive fail. I only had one parity and it took a crap on me so I pulled it out and replaced it with a new drive that is 2tb bigger. It said if I start up the array it will start a resync rebuild, so I clicked start. Shortly after this drive also got an error and has a red x next to it not allowing it to rebuild. Am I missing something? Do I do something besides just letting it rebuild? It will not rebuild now due to it being disabled.

Thank you so much that worked! Once I saw that in the share config I figured something weird was happening. The cache is working! Thank you very much, this whole ordeal has sparked my old love of linux again and makes me want to get back into it. I miss IT! haha take care!

the new test share is called test share

here is the new diag. I looked into share.cfg in the diag and it shows shareCacheEnabled="no" which means its not active correct? nas-diagnostics-20241127-1358.zip

files are transcoded to the cache just fine during plex hardware transcoding. So I am at a loss.

it went to disk four in the array. It did not go to the cache.

so I went in and set the shares to 50gb for some reason they were at 0 like you said. Not sure how but I reset them to 50 across the board and left the cache at 100gb and still the files write to one of the drives on the array instead of using the cache.

Wondering if I should just clear everything out and redo the whole set up I’m trying to avoid doing that. I have a feeling there has to be some stupid setting. I’m not thinking of.

Over Smb via windows network share drive. And when I run home I’ll double check but I thought I set a minimum of 90gb on that share. Is that different than a floor ?

So the shares are 90gb some are 97.8gb because unraid set that way by default. I set the minimum cache to 100gb. If I try to drag a file over to movie folder or any of my other shares, it just goes directly to one of the array drives. I was assuming maybe that diagnostics it would show. I have a hard time reading that.

I am sorry if I am coming off as ignorant but I am not sure what you mean. Do you mean the shares minimum needs to be smaller than the cache? So I would set the shares to 50gb and the cache to 100gb and problem solved?

I just wanted to say thank you for the help up front. I have ran an Unraid server for a long time but never messed with the cache. I now want to use my 1tb cache drive and have followed the proper steps I believe. I have the shares set to 1st drive cache 2nd drive array then mover is cache --> array. I also set the minimum share to 100GB and the cache drive to 100GB. So even large 4k movies should be fine for the most part moving to the cache and then the array. No matter what I have no activation on the cache drive and only see one of my arrays writing during the file transfers. I am attaching a diagnostics print up of my server. Thank younas-diagnostics-20241126-1047.zip in advance!