Rallysports

I have debated getting a SAS controller and going that route to allow more drives as my Mobo SATA is maxed out. I wonder if that could take the strain off as that is what is in my prior server that has been running for 5+ years.

Hey johnnie.black, I have to say I panicked and did a fear reboot hoping everything would be ok afterwards. I will remember this next time to pull the logs before. I am currently just using onboard SATA. Could this maybe be a Mobo thing? To resync the parity do I just need to wait for the "Read Check" to finish and then there will be an option to resync or is it more in depth? And thanks for the quick response. One of the reasons I love UNRAID is because of the community support.

Hey All, Had a weird occurrence last night as I was doing another bulk copy of my data to a new server. Around 3:55am the parity drive (GU28Z) showed in error state. Then a minute later it showed errors on the rest of the array drives. These are all brand new 10TB WD drives and all went through the preclear process. After a reboot I show no errors but the parity drive is disabled. Currently I am performing a "Read Test". I have read in other posts that if nothing is wrong with the parity drive then I can reassign it? I am not sure how to determine if the drive is ok. I am wondering if I may have had a power issue or something. The new server is on my desk currently and not yet protected behind a UPS. Was going to move it down once I had everything running normally. Any help would be appreciated. Thanks jktower-diagnostics-20200218-0729.zip

Please take a look at the first post for "How can I download a copy of the plugin log" and send the file here. Not sure if there is a mix up but this file is what I PM'd you. I did as the instructions stated. Is there something I am not seeing? JK TOWER-preclear.disk-20180506-1649.zip

I sent them over gfjardim. Thanks for taking a look at it. JK

I have updated to the latest version of the plugin and I have had the same thing happen on a brand new drive 3 times. The first two I skipped the extra parts and the last one I let it run through the whole thing. It keeps disconnecting the drive, only accessible after I pull the drive and reseat. Then it tells me that a signature was not valid. At what point do I determine if this was a DOA drive or something up with the script or plugin? Thanks JK

That was my first thought as well, but transmission does not seem to be affected. It will connect at around 7MB and stay there through the end of the download. JK

I have went all the way down from 20 connections to 2. It all gets me the same result. It is kinda spooky actually because the graph that Sab shows has the same thing every time. Straight across and then it curves until 1.3 and then solid again. JK

I am having an issue with Speed on my container. I will start a download and it will go up to 4.5 or 5MB and then after about a minute like clockwork it goes down to 1.3MB. This happens for many downloads and it always seems to happen when I dont have anything going and then start something. Then it stays at 1.3MB exactly for the rest of the download. If I wait long enough and add something it will then start high and then lower back to 1.3MB Could this be a docker networking issue rather than a container issue? Thanks JK

That could be it. I will do some research on the preclear and try that tonight. Thanks JK

I am just getting started with unRAID. I have always used Windows Home Server and luckily got away without any failed drives on it. (knock...knock) My issue is this. I setup a machine with 2 drives and 1 parity to test. I put data on and made sure that some was on both the data drives. I then let the parity drive do its thing. When trying to duplicate a drive failure by unplugging one of the drives and then put in a new one realized all the drives that I had to put in were bigger than the parity drive. So I then proceeded to get the array working back like normal and then upgrade the parity drive in the same way. The issue is when I plugged in the new larger drive where the old parity drive was and then changed it from no device to the long drive name, it paused for a second and then went back to no device and there was no other drive option. I tried rebooting and everything and it would never come back, so then I plug the old parity drive back in and then it would see it and would rebuild the parity. Am I doing something wrong? I can try it again and pull a syslog but it was adding things so fast I couldnt see any errors. Thanks for any help. JK