deaerator Posted July 25, 2015 Share Posted July 25, 2015 I tried to re-install some dockers and nothing is working now. IMAGE ID [latest]: Pulling from gfjardim/nzbget. IMAGE ID [511136ea3c5a]: Pulling fs layer. IMAGE ID [53f858aaaf03]: Pulling fs layer. IMAGE ID [837339b91538]: Pulling fs layer. IMAGE ID [615c102e2290]: Pulling fs layer. IMAGE ID [b39b81afc8ca]: Pulling fs layer. IMAGE ID [8254ff58b098]: Pulling fs layer. IMAGE ID [ec5f59360a64]: Pulling fs layer. IMAGE ID [2ce4ac388730]: Pulling fs layer. IMAGE ID [2eccda511755]: Pulling fs layer. IMAGE ID [5a14c1498ff4]: Pulling fs layer. IMAGE ID [adc8c0d192ae]: Pulling fs layer. IMAGE ID [d7fed2669ee1]: Pulling fs layer. IMAGE ID [ca741522778f]: Pulling fs layer. IMAGE ID [81e13f5c6a26]: Pulling fs layer. IMAGE ID [dbfbc570a878]: Pulling fs layer. IMAGE ID [e1bb03e410af]: Pulling fs layer. IMAGE ID [2accc56105d5]: Pulling fs layer. Layer already being pulled by another client. Waiting.. Pulling repository gfjardim/nzbget. Download complete. Pulling image (latest) from gfjardim/nzbget. Pulling image (latest) from gfjardim/nzbget, endpoint: https://registry-1.docker.io/v1/. Pulling dependent layers. IMAGE ID [511136ea3c5a]: Pulling metadata. Pulling fs layer. Error pulling dependent layers. IMAGE ID [2accc56105d5]: Error pulling image (latest) from gfjardim/nzbget, endpoint: https://registry-1.docker.io/v1/, Server error: Status 0 while fetching image layer (511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158). Error pulling image (latest) from gfjardim/nzbget, Server error: Status 0 while fetching image layer (511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158). root@localhost:# /usr/bin/docker run -d --name="NZBGet" --net="bridge" -e TZ="America/Halifax" -p 6789:6789/tcp -v "/mnt/user/appdata/nzbget":"/config":rw -v "/mnt/user/appdata/downloads":"/downloads":rw gfjardim/nzbget Unable to find image 'gfjardim/nzbget:latest' locally latest: Pulling from gfjardim/nzbget 511136ea3c5a: Pulling fs layer 53f858aaaf03: Pulling fs layer 837339b91538: Pulling fs layer 615c102e2290: Pulling fs layer b39b81afc8ca: Pulling fs layer 8254ff58b098: Pulling fs layer ec5f59360a64: Pulling fs layer 2ce4ac388730: Pulling fs layer 2eccda511755: Pulling fs layer 5a14c1498ff4: Pulling fs layer adc8c0d192ae: Pulling fs layer d7fed2669ee1: Pulling fs layer ca741522778f: Pulling fs layer 81e13f5c6a26: Pulling fs layer dbfbc570a878: Pulling fs layer e1bb03e410af: Pulling fs layer 2accc56105d5: Pulling fs layer 2accc56105d5: Pulling fs layer 2accc56105d5: Layer already being pulled by another client. Waiting. Pulling repository gfjardim/nzbget 2accc56105d5: Download complete 2accc56105d5: Pulling image (latest) from gfjardim/nzbget 2accc56105d5: Pulling image (latest) from gfjardim/nzbget, endpoint: https://registry-1.docker.io/v1/ 2accc56105d5: Pulling dependent layers 511136ea3c5a: Pulling metadata 511136ea3c5a: Pulling fs layer 511136ea3c5a: Error pulling dependent layers 2accc56105d5: Error pulling image (latest) from gfjardim/nzbget, endpoint: https://registry-1.docker.io/v1/, Server error: Status 0 while fetching image layer (511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158) 2accc56105d5: Error pulling image (latest) from gfjardim/nzbget, Server error: Status 0 while fetching image layer (511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158) time="2015-10-24T21:46:21-03:00" level=fatal msg="Error pulling image (latest) from gfjardim/nzbget, Server error: Status 0 while fetching image layer (511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158)" The command failed. Quote Link to comment
deaerator Posted July 26, 2015 Author Share Posted July 26, 2015 Update: I reformatted my usb drive and put Unraid back on it with a clean install. I saved my array settings and back up and running again. Docker is still giving me the same errors Pulling image: linuxserver/plex:latest IMAGE ID [latest]: Pulling from linuxserver/plex. IMAGE ID [511136ea3c5a]: Pulling fs layer. IMAGE ID [53f858aaaf03]: Pulling fs layer. IMAGE ID [837339b91538]: Pulling fs layer. IMAGE ID [615c102e2290]: Pulling fs layer. IMAGE ID [b39b81afc8ca]: Pulling fs layer. IMAGE ID [8254ff58b098]: Pulling fs layer. IMAGE ID [ec5f59360a64]: Pulling fs layer. IMAGE ID [2ce4ac388730]: Pulling fs layer. IMAGE ID [2eccda511755]: Pulling fs layer. IMAGE ID [5a14c1498ff4]: Pulling fs layer. IMAGE ID [e206d5fe2a5b]: Pulling fs layer. IMAGE ID [cfd284ec74f2]: Pulling fs layer. IMAGE ID [e6624efa03db]: Pulling fs layer. IMAGE ID [d680890e907c]: Pulling fs layer. IMAGE ID [26a00a9ab589]: Pulling fs layer. IMAGE ID [8172f09f7095]: Pulling fs layer. IMAGE ID [4b5ccf93ca2a]: Pulling fs layer. IMAGE ID [cf788be675fd]: Pulling fs layer. IMAGE ID [dad4ea3f0ebd]: Pulling fs layer. IMAGE ID [91bcfb40161d]: Pulling fs layer. IMAGE ID [05c5b8ad1f8a]: Pulling fs layer. IMAGE ID [29af19c672e1]: Pulling fs layer. IMAGE ID [1945f71177cf]: Pulling fs layer. IMAGE ID [6c64bfaf5450]: Pulling fs layer. IMAGE ID [031fcb0b8e62]: Pulling fs layer. Layer already being pulled by another client. Waiting.. Pulling repository linuxserver/plex. Download complete. Pulling image (latest) from linuxserver/plex. Pulling image (latest) from linuxserver/plex, endpoint: https://registry-1.docker.io/v1/. Pulling dependent layers. IMAGE ID [511136ea3c5a]: Pulling metadata. Pulling fs layer. Error pulling dependent layers. IMAGE ID [031fcb0b8e62]: Error pulling image (latest) from linuxserver/plex, endpoint: https://registry-1.docker.io/v1/, Server error: Status 0 while fetching image layer (511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158). Error pulling image (latest) from linuxserver/plex, Server error: Status 0 while fetching image layer (511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158). TOTAL DATA PULLED: 0 B Command: root@localhost:# /usr/bin/docker run -d --name="plex" --net="host" -e PUID="99" -e PGID="100" -e PLEXPASS="1" -e TZ="America/Halifax" -v "/mnt/user/appdata/plex/":"/config":rw -v "/mnt/user0/":"/media":rw -v "/tmp":"/transcode":rw linuxserver/plex Unable to find image 'linuxserver/plex:latest' locally latest: Pulling from linuxserver/plex 511136ea3c5a: Pulling fs layer 53f858aaaf03: Pulling fs layer 837339b91538: Pulling fs layer 615c102e2290: Pulling fs layer b39b81afc8ca: Pulling fs layer 8254ff58b098: Pulling fs layer ec5f59360a64: Pulling fs layer 2ce4ac388730: Pulling fs layer 2eccda511755: Pulling fs layer 5a14c1498ff4: Pulling fs layer e206d5fe2a5b: Pulling fs layer cfd284ec74f2: Pulling fs layer e6624efa03db: Pulling fs layer d680890e907c: Pulling fs layer 26a00a9ab589: Pulling fs layer 8172f09f7095: Pulling fs layer 4b5ccf93ca2a: Pulling fs layer cf788be675fd: Pulling fs layer dad4ea3f0ebd: Pulling fs layer 91bcfb40161d: Pulling fs layer 05c5b8ad1f8a: Pulling fs layer 29af19c672e1: Pulling fs layer 1945f71177cf: Pulling fs layer 6c64bfaf5450: Pulling fs layer 031fcb0b8e62: Pulling fs layer 031fcb0b8e62: Pulling fs layer 031fcb0b8e62: Layer already being pulled by another client. Waiting. Pulling repository linuxserver/plex 031fcb0b8e62: Download complete 031fcb0b8e62: Pulling image (latest) from linuxserver/plex 031fcb0b8e62: Pulling image (latest) from linuxserver/plex, endpoint: https://registry-1.docker.io/v1/ 031fcb0b8e62: Pulling dependent layers 511136ea3c5a: Pulling metadata 511136ea3c5a: Pulling fs layer 511136ea3c5a: Error pulling dependent layers 031fcb0b8e62: Error pulling image (latest) from linuxserver/plex, endpoint: https://registry-1.docker.io/v1/, Server error: Status 0 while fetching image layer (511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158) 031fcb0b8e62: Error pulling image (latest) from linuxserver/plex, Server error: Status 0 while fetching image layer (511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158) time="2015-10-25T01:58:29-03:00" level=fatal msg="Error pulling image (latest) from linuxserver/plex, Server error: Status 0 while fetching image layer (511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158)" The command failed.] Quote Link to comment
Squid Posted July 26, 2015 Share Posted July 26, 2015 Just for the heck of it, try setting some DNS addresses in the network settings. IE: 8.8.8.8 and 8.8.4.4 and try it again. Quote Link to comment
deaerator Posted July 26, 2015 Author Share Posted July 26, 2015 Changing the DNS settings did not work. Quote Link to comment
deaerator Posted July 27, 2015 Author Share Posted July 27, 2015 Update: I'm still at a loss of words on what could be wrong here. I get a messaged that it disables IRQ #21 http://1drv.ms/1gYcapY Quote Link to comment
RobJ Posted July 27, 2015 Share Posted July 27, 2015 I'm sure you know that IRQ assignments are different on every machine, so we need a LOT more info to know what it's assigned to. Please provide a Diagnostics zip. Please read Need help? Read me first! Quote Link to comment
deaerator Posted July 27, 2015 Author Share Posted July 27, 2015 Diagnostics is attatched tower-diagnostics-20151026-1147.zip Quote Link to comment
trurl Posted July 27, 2015 Share Posted July 27, 2015 Your logs, and in fact, the files contained in the zip file, have timestamps from October 2015, the future. Also, even though your array has several disks assigned, and there is nothing in your syslog about flash corruption, your super.dat is unreadable. Oct 25 18:43:37 Tower kernel: read_file: error 2 opening /boot/config/super.dat Oct 25 18:43:37 Tower kernel: md: could not read superblock from /boot/config/super.dat Oct 25 18:43:37 Tower kernel: md: initializing superblock None of this is obviously related to your complaint, but it is a cause for concern. Take a screenshot of your disk assignments in case they don't survive a reboot. Stop, shutdown, put your flash in your PC and let it checkdisk. Also, check your BIOS time or something to get your server time fixed. After you have done all this, boot up again and give us another diagnostic. Quote Link to comment
deaerator Posted July 27, 2015 Author Share Posted July 27, 2015 I found no errors when i did check disk on the flash drive here is a new diagnostic. tower-diagnostics-20150727-1000.zip Quote Link to comment
wbee Posted July 27, 2015 Share Posted July 27, 2015 I had a power failure at home and after that my docker also is missing... I cant see any applications. So you are not alone in this. Quote Link to comment
deaerator Posted July 28, 2015 Author Share Posted July 28, 2015 UPDATE: I found two problems with my setup. 1. I had a bad network cable that decided to crap out at the same time as my docker crapped out. 2. I decided to change the size of the docker file to 25gb, and when i Istarted it back up some how it got duplicated and to another one of my drives, and every time i tried to make a new docker it failed. Should I be worried that the super.dat file can't be read. Quote Link to comment
trurl Posted July 28, 2015 Share Posted July 28, 2015 UPDATE: I found two problems with my setup. 1. I had a bad network cable that decided to crap out at the same time as my docker crapped out. 2. I decided to change the size of the docker file to 25gb, and when i Istarted it back up some how it got duplicated and to another one of my drives, and every time i tried to make a new docker it failed. Should I be worried that the super.dat file can't be read. The latest diagnostic you posted didn't indicate a problem reading super.dat. That file is where your array configuration and status is stored. When you create a new array, that file won't exist until you start the array. Is that maybe what happened? Anyway, I think it is OK now. As far as your docker img getting duplicated, are you sure it didn't get moved by mover? What is the path to your docker img? Quote Link to comment
deaerator Posted July 28, 2015 Author Share Posted July 28, 2015 It probably did get moved, when i checked the shares on the location of the file it had it on cache drive and disk 6. Quote Link to comment
trurl Posted July 28, 2015 Share Posted July 28, 2015 It probably did get moved, when i checked the shares on the location of the file it had it on cache drive and disk 6. What is the path to your docker img? Quote Link to comment
deaerator Posted July 28, 2015 Author Share Posted July 28, 2015 The path I had was /mnt/user/appdata/docker/docker.img Quote Link to comment
trurl Posted July 28, 2015 Share Posted July 28, 2015 The path I had was /mnt/user/appdata/docker/docker.img And is your appdata user share set to cache-only? Quote Link to comment
deaerator Posted July 28, 2015 Author Share Posted July 28, 2015 It was set as a cache only share, and is now. Quote Link to comment
scottc Posted July 28, 2015 Share Posted July 28, 2015 the path should be /mnt/cache/appdata/docker/docker.img instead of /mnt/user/appdata/docker/docker.img Quote Link to comment
trurl Posted July 28, 2015 Share Posted July 28, 2015 The path I had was /mnt/user/appdata/docker/docker.img And is your appdata user share set to cache-only? Actually, I seem to remember there is a requirement for docker img to be on an actual disk, instead of a user share. I have my docker img at /mnt/cache/docker.img. Mover doesn't touch files at the root of cache, only folders. If you would rather, you can put it at /mnt/cache/appdata/docker/docker.img. You would still need the appdata user share set to Use cache disk: Only. Quote Link to comment
deaerator Posted July 28, 2015 Author Share Posted July 28, 2015 Changing the path to /mnt/cache/appdata/docker/docker.img Quote Link to comment
deaerator Posted July 28, 2015 Author Share Posted July 28, 2015 Does it matter if your docker config file go through /mnt/cache/ or /mnt/user Quote Link to comment
trurl Posted July 28, 2015 Share Posted July 28, 2015 Does it matter if your docker config file go through /mnt/cache/ or /mnt/user Shouldn't matter but I always refer to cache-only shares with /mnt/cache instead of /mnt/user. Less work for the system to figure out which disk, and more obvious to the user (me). Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.