September 4, 20169 yr Hi everyone, I have been trying to figure out this issue for a few weeks now and having pulling my hair out with frustration! I have an issue where I would randomly lose access to the array and a docker would crash.I can access via telenet to enter commands, however after creating logs via the powerdown package, the server will not restart. I have to then do a hard reset. The last time I ran the server, it was up for a day then crashed, before I did a reset I checked on a few things. Dockers Accessible after/during the crash: Sabnzbd Couchpotato Plex Plexpy Crashplan Dockers not accessible after/during the crash: Sonarr VM installed (did not check if it was not accessible after the crash): 1 Win 10 VM I have been an unraid user since the 4.7 days and have never had an issue quite like this since I switched over to 6.0 and dockers, I am at a loss right now to figure out what the issue. I appreciate the help in advance! I attached a copy of syslog, however I have the entire diagnostics package that powerdownpackage creates if needed. EDIT: Attached package. syslog.txt ephesus-diagnostics-20160904-1000.zip
September 4, 20169 yr Community Expert ... I have the entire diagnostics package that powerdownpackage creates if needed. Save us the trouble of asking for it next time.
September 4, 20169 yr Author ... I have the entire diagnostics package that powerdownpackage creates if needed. Save us the trouble of asking for it next time. I apologize, I have attached it for reference. I'll edit the original post as well. ephesus-diagnostics-20160904-1000.zip
September 4, 20169 yr One thing is that your plexpass app appears to have invalid characters in the name (probably the brackets) Beyond that, nothing is really jumping out at me.
September 4, 20169 yr Author One thing is that your plexpass app appears to have invalid characters in the name (probably the brackets) Beyond that, nothing is really jumping out at me. Yes, thanks to the FCP plugin, I was able to fix that issue, I removed the illegal characters and replaced it with something that is compatible. The current error from FCP is moving the docker image completely to the cache, which I am still trying to figure out how to do. (FCP does give me a suggestion on how to do it)
September 4, 20169 yr One thing is that your plexpass app appears to have invalid characters in the name (probably the brackets) Beyond that, nothing is really jumping out at me. Yes, thanks to the FCP plugin, I was able to fix that issue, I removed the illegal characters and replaced it with something that is compatible. The current error from FCP is moving the docker image completely to the cache, which I am still trying to figure out how to do. (FCP does give me a suggestion on how to do it) If the docker.img file is the only thing sitting in the share, then setting it to be cache only should do the trick. But if there are other files / folders in it, then you should probably delete the docker.img file and then recreate it either on the root of the cache drive, or in a newly created share set to be cache-only. No idea how the system responds if the docker.img gets moved to the array while containers are still running.
September 4, 20169 yr Author One thing is that your plexpass app appears to have invalid characters in the name (probably the brackets) Beyond that, nothing is really jumping out at me. Yes, thanks to the FCP plugin, I was able to fix that issue, I removed the illegal characters and replaced it with something that is compatible. The current error from FCP is moving the docker image completely to the cache, which I am still trying to figure out how to do. (FCP does give me a suggestion on how to do it) If the docker.img file is the only thing sitting in the share, then setting it to be cache only should do the trick. But if there are other files / folders in it, then you should probably delete the docker.img file and then recreate it either on the root of the cache drive, or in a newly created share set to be cache-only. No idea how the system responds if the docker.img gets moved to the array while containers are still running. Turns out the docker.img in the user share had not been modified since 2015, could have been a remnant from an old configuration. I was able to delete the share without issue. New/Current docker.img is kept on the cache drive.
Archived
This topic is now archived and is closed to further replies.