Acps

Accidentally posted this in another thread: Just like to mention I was able to fix it myself, by deleting the perms file and restarting the docker!

Mighta been to high to realize that lol, sorry

Ok Ive run into this issue before where I cannot login to the webgui of deluge. I get this far and hit enter, and then it just re-prompts me for the password again. I cant remember what I did last time to fix this. Any ideas?

From experience I can tell you it's very hard to brick a modern motherboard these days. Specifically gigabyte boards. Gigabyte puts a backup copy of the bios that can't be accessed by the user. Only able to copy it if and when you brick your motherboard and corrupt your primary bios. I had bricked my motherboard for a few days and about gave up until I found something like this: http://www.overclockers.com/forums/showthread.php/697533-GUIDE-Forcing-backup-BIOS-on-Gigabyte-motherboards I found a very nasty flaw with z77-hd3 original bios firmware that would brick it and had nothing to do with trying to update it. Once I learned how to system restore the bios once its corrupt. I repeated it a few times, motherboard is still being used without any problems. Similar thing happened when I was messing with DD-WRT on my Asus router. Thing was bricked for a few days until I uncovered a way to recover my router. Main thing is if you do brick something, don't lose hope. Spend some time searching online for a recovery method. Most tech within the last 10 years is fairly brick proof to the average user. Acps

Ok so I tried multiple things to try and fix this, including delete the docker and reinstalling, deleting the docker template, resetting and installing with default settings, deleting the dock image itself and rebuilding it. None of which fixed the issue. Until I found this post: And looking at my docker logs I could see it was having permission issues, so I did 2 things, first was to set my appdata folder "cache" settings to Prefer instead of Only. And I adjusted the appdate install path within the template from to So this is what my docker tab looks like now: The permission issues in the log stopped and the errors I was getting every time I launched the docker have stopped as well. Can able tell me whether or not this is how your supposed to set the path for the "appdata /config"? I switched my other docker apps to /mnt/user/ as well instead of /mnt/cache/. The whole reason why this even popped up for me was because I swapped out some ssds for my cache drive and reinstalled all my dockers from scratch. It had been running fine before that for atleast a year or so. Thanks in advance! ~Acps

I am having this same issue after swapping cache drives and choosing to rebuild my dockers from scratch. I think there is some sort of permission error going on, not only do I get this same error each time but it also walks me through the tutorial for the first time each time. Here is what my dockers look like I have also tried with all default settings as well as deleting my docker user template on my flash drive and trying another install, but nothing helps. Here is my docker log as well: supervisord.rar I thought that this might be related: https://forums.unraid.net/topic/72736-fix-common-problems-binhex-krusader-newbie-question/ But i still have issue without mapping anything but the default and excluding Unassigned devices to see if it would help. If anyone could point me in the right direction to try and fix this I would really appreciate it. P.S. I had a very much similar issue with deluge docker awhile back as well: https://forums.unraid.net/topic/62206-dockerappdata-permission-issue/ Thanks in advance for the help as always! ~Acps

I am trying to figure out what exactly I did, I was trying to manually backup my plex folder in appdata, then I was going setup the plugin to do auto backups from then on. I dont think i deleted it, as all my profiles and all my dockers are still untouched. I am trying to see if there is anyways to get to my plex appdata or if it is gone. I been looking at swapping my ssds from my cache drive to something smaller like 250gb vs 500gb, raid 0. IF my appdata really is gone I might just start from scratch then with differenty ssd's

has anyone been able to take a look at this for me? ty

So ive been trying to setup for my appdata folder in case of a drive failure. I was trying to backup my folders by hand before doing this and I ran into problems. My plex appdata seems to be missing, whenever I open Plex to view media, there is none and it wants me to add media to itself. It kinda looks like all my settings got reset back to default and all my metadata removing my shares of Movies and TV Show. I was thinking I might of deleted something by accident, but looking at the folder size its at 4gn, I think it should be around 70gb+. If someone culd peek at my logs to see I would really appreciate it. Thanks in advance for the help! ~Acps unraid-diagnostics-20181023-0023.zip

My cache drive data currently sits with just my appdata for a few dockers, mainly plex which is probably 25gb+ now, and my docker image which is 20gb. My plex app can be sluggish when starting up for the first time but I think this is from being spun down/offline? to conserve power? Or could be from my massive library. Currently I have 2 250gb SSDs setup as a raid0 pool. They are connected to my sata 6gb/s sata ports on my motherboard. A couple of things; 1) Does having 2 ssds raid 0 in a pool give me a huge performance bump as opposed to raid 1 for redundancy? I was pooling 500gb total for plex and 2-3VMs. 2) Can I drop my x2 250gb raid 0 setup for a x2 128gb raid 1 pool instead? The thought being I can now pass-through my ssds for my VM instead of making vdisks. I'm thinking I want to switch to raid 1 pool if its not a huge performance hit for read/write, so that my plex library is backed-up with my appdata. As it stands now if I lost my plex library appdata I would loose over 25gb+ most of which is metadata for my media. I have terrible internet 12Mbps/1Mbps, so it would take ages to try and replace it all. Thanks in advance! ~Acps

Just to follow up I was able to rebuild just fine replacing disk 1 and parity 1. Parity 1 had to be replaced because i somehow set it on fire while checking disk 1 and parity 2 inside my case, it caught fire right at the sata power port as soon as I powered it back on. I also swapped my raid controller from a pcix4 slot to my pcix16, also I moved all my raid disks to the raid controller exclusively and my 2 ssd cache drives to my 6gb/s sata ports on my gigabyte motherboard. Hoping that it might clear up my drives dropping offline from my controller. Thanks again for all the help jonnie I really appreciate it. I wanted to try and document as much info while working on this in my thread in case I need to come back to it later or have similar issues in the future as I have a terrible memory! ~Acps

This is what my array looks like if I want to try and rebuild. Here are my logs from this morning unraid-diagnostics-20180722-0943.zip

It was a UNC error reported on Parity2. I acknowledged the error and since then been able to do several Parity checks without any errors.

So i got 2 replacement drives 5tb. Last night I was going to replace Disk1 first and rebuild the array, then replace Parity2 and rebuild it again. Not sure what happened after i installed Disk1, but when I powered it up, Parit1 caught fire and melted the Sata connector from the power supply. Im not sure whether or not Parity1 is actually damaged beyond repair yet, obviously the Sata power cable melted and is, but I might be able to clean up the disk port and clean the contacts off to bring it back to life. My questions is, since I have 2 parity drives, i can loose 2 disks and still not have any data loss. Technically Disk1 is dead, Parity1 might be and Pairty2 has some errors. What is going to be my best route to not loose any damage if its still possible? Can i use my 2 new 5tb drives for Disks1 and Parity1, and rebuild it with my a faulty parity 2? Thanks again for the help! ~Acps

Accidentally posted in another thread, that I thought is related to what was going on here. https://lime-technology.com/forums/topic/62206-dockerappdata-permission-issue/?do=findComment&comment=664652 On a side note, I was able to pull the smart report from disk 1: unraid-smart-20180618-2304.zip

Realized that I should have posted this in my other thread: https://lime-technology.com/forums/topic/61966-call-traces-parity2-errors/

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

Sorry I took me a bit to get around to posting these again. I was gonna install the preclear plugin and try running that again on disk1? I tryed to rebuild it twice and it wasnt working like before when this happened in Dec. unraid-diagnostics-20180616-2308.zip unraid-smart-20180616-2352-parity2.zip unraid-smart-20180617-0001-disk1.zip

Looks like I might be having the same issue again. IS it my parity 2 disk that is having issues or my disk 1? unraid-smart-20180517-1305.zip unraid-diagnostics-20180517-1303.zip

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

Was going over some settings in my dockers, and was wondering if Privileged was needing to be turned on since the docker is ran as a Host type network?

I think they are related as they both started last month some time. The call traces were first reported on Nov-11 and the Parity2 started showing errors on Nov-18. Attached both unraid logs and the smart errors report. Thanks in advance! unraid-diagnostics-20171209-0201.zip smarterrorlog.txt Edit: Added diagnostics from October as well, there was alot of entries repeating themselves too. And I also noticed there is a 4 day gap between my logs for some reason, Nov 10-14. On the 14th the log doesnt begin with the startup sequence, like it normally does. unraid-diagnostics-20171110-1307.zip

Ok, So I am still having issues. The same drive failed several times, at like 4 week intervals. Each time it looked the same as before, and I was able to rebuild the array. I was excited for dual parity, and quickly upgraded to that. Since I did, a whole new set of issues popped up. Here is what my last few parity checks look like: On Feb 28, I was streaming Plex during the weekly Parity check. At some point during that Plex tosses an error that It cannot read the data anymore, I go and check and find drive 3 and 4 failed this time. So I did a system reboot. After the reboot, drives 3/4 are being emulated now, but also my cache 1 drive is now missing. Not failed, but it straight up did not boot and the server doesn't even see it. Did another reboot to see if it would come back up and it does not. I ended up switching to another cable/port on my raid controller. And it came back up and mounted with cache2 to restore my appdata. So I ran extended smart tests on both drives 3/4 and they passed with no errors. So i rebuilt the array and everything checked out. I have the syslogs and will attach them at the bottom. I put 2 syslogs down there, one before and the reboot after the failures. Now on Apr 10, literally the exact thing happened again, right down to me streaming plex. And I went through the motions again and checked the smart reports, and swapped cache1 cable on the controller. I dont have the syslogs for this due to the fact Powerdown wasnt updated for 6.3 and I didnt realize this till today. I am getting paranoid now that at some point I will get a scenario where I cant rebuild my array which is now 23TB and will loose data. This cannot be a coincidence either, that after updating to dual parity i have 2 drive failures shortly after. And that its occuring during parity check, and then the cache drive blows my mind. I think my next step needs to be identifying all my hdds in my case, and seeing which ones are on my raid controller and which ones are on the onboard sata ports. I do know that both my cache drives are on the raid controller. In my previous post I mentioned I did indeed swap out the controller card, and thought the issue was resolved. The odds of both controllers going bad and starting with drive 3 failing has me thinking it cant be the card. I would really appreciate it if someone can take a peek at my syslog from Feb28 and point me in the right direction towards getting this resolved! Thanks in advance! syslog-20170228-041347.txt syslog-20170301-215946.txt

Ok, ironically I accidentally bought 2 of the same controller when i installed it. So i just swapped out the controllers for now and left the cables, as they are buried in my server. I do have spare cables if I am still having issues after this. I do not have an extra PCI slot tho, well kinda. I have 2, the other is filled with a video card. While I could swap the controller to that PCI slot, the video card if installed has to be in that slot. But I don't think a PCI slot can go bad?

Well, the device is offline again, after rebooting for unraid update. Short Smart Test is saying Passed. Is this a good indication that I have a bad drive? Why isnt the smart report finding anything? unraid-diagnostics-20161129-0804.zip