December 18, 20178 yr I think I have a permission issue going on with my dockers in my appdata folder. I noticed it last week when I could no longer access deluge, it would keep asking for the password to access the webgui. Looking at the logs I keep seeing "No such file or directory:" I tried to reinstall the docker and tried another version of deluge, but the same thing happened. I wanna say this started happening when I cleaned up my docker image and moved it to the root dir of my cache drive at /mnt/cache/ Attached my logs. If anyone could take a look. Thanks in advance! unraid-diagnostics-20171218-1726.zip
June 19, 20188 yr Author Ok, I cant remember exactly what I did last time to try and fix this, I think i ended up deleting the entire appdata folder and installing a different docker for deluge. But now I am having the exact same issue. And it cant be a coincidence that I am having disk issues again with my server, almost identical. But my appdata is all on my cache drive, which for the moment isnt having any issues, so I really don't know where to go from here. I feel like I am going in circles chasing this down. It could be my controller, or my parity 2/disk 1 drive. https://lime-technology.com/forums/topic/61966-call-traces-parity2-errors/ A year before that starting in Fall 2017, I had what I thought was a disk go bad, and that was back in the Fall of 2016. I ended up replacing the drive and the SAS2LP controller with another of the same model in April 2017. https://lime-technology.com/forums/topic/51135-disk-3-device-disabled-contents-emulated/ The only thing I didnt try was turning off the vt-d. I had hoped that replacing the drive/controller had fixed it and it seemed to do Ok for several months atleast. My parity 2 drive seems to not be throwing anymore UNC errors. And i have tried to rebuild the array 3 times with disk 1, I even tried using the preclear plugin and it still not able to rebuild the array, it does give it an honest effort tho: Im thinking about pulling drive 1 out of the server and putting into my win10 desktop and running a the smart tests to see what it says. Since I am running 2 parity disks, that means that I need to have 3 drives go offline before I loose any data? I do have 2 much older 5tb drives in a box, that were replaced by SSDs for my desktop. But they would different models and possible different speeds/cache. Was also mentioned that maybe my cables might be bad, I have no clue how to test that. When I replaced the SASLP card in Fall 2016, I replaced both of the cables which allow 4 Sata drives on each for total of 8. All 7 of my raid array drives are on that card http://www.supermicro.com/products/accessories/addon/AOC-SASLP-MV8.cfm Then my 2x 250gb SSD are in a raid 0 cache pool using the motherboards sata 6 ports. Anyways, sorry for the long ass post, but I hope I can provide enough information to try and get pointed in the right direction. Thanks again for the help so far, especially johnnie.black
June 19, 20188 yr Author Realized that I should have posted this in my other thread: https://lime-technology.com/forums/topic/61966-call-traces-parity2-errors/
Archived
This topic is now archived and is closed to further replies.