Dimtar Posted September 4, 2014 Share Posted September 4, 2014 Not sure if this is the right place but running beta8 and this happens when I try to start a Docker: root@localhost:# /usr/bin/docker logs CrashPlan *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... No SSH host key available. Generating one... Creating SSH2 RSA key; this may take some time ... Creating SSH2 DSA key; this may take some time ... Creating SSH2 ECDSA key; this may take some time ... Creating SSH2 ED25519 key; this may take some time ... invoke-rc.d: policy-rc.d denied execution of restart. *** Running /etc/my_init.d/config.sh... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 105 *** Shutting down runit daemon (PID 105)... The command finished successfully! Dockers won't start, is this related to something with the new Beta? Link to comment
jonp Posted September 4, 2014 Share Posted September 4, 2014 Not sure if this is the right place but running beta8 and this happens when I try to start a Docker: root@localhost:# /usr/bin/docker logs CrashPlan *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... No SSH host key available. Generating one... Creating SSH2 RSA key; this may take some time ... Creating SSH2 DSA key; this may take some time ... Creating SSH2 ECDSA key; this may take some time ... Creating SSH2 ED25519 key; this may take some time ... invoke-rc.d: policy-rc.d denied execution of restart. *** Running /etc/my_init.d/config.sh... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 105 *** Shutting down runit daemon (PID 105)... The command finished successfully! Dockers won't start, is this related to something with the new Beta? Can you post a full syslog as well? Link to comment
Dimtar Posted September 4, 2014 Author Share Posted September 4, 2014 Not sure if this is the right place but running beta8 and this happens when I try to start a Docker: root@localhost:# /usr/bin/docker logs CrashPlan *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... No SSH host key available. Generating one... Creating SSH2 RSA key; this may take some time ... Creating SSH2 DSA key; this may take some time ... Creating SSH2 ECDSA key; this may take some time ... Creating SSH2 ED25519 key; this may take some time ... invoke-rc.d: policy-rc.d denied execution of restart. *** Running /etc/my_init.d/config.sh... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 105 *** Shutting down runit daemon (PID 105)... The command finished successfully! Dockers won't start, is this related to something with the new Beta? Can you post a full syslog as well? syslog.txt Link to comment
jonp Posted September 4, 2014 Share Posted September 4, 2014 Not sure if this is the right place but running beta8 and this happens when I try to start a Docker: root@localhost:# /usr/bin/docker logs CrashPlan *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... No SSH host key available. Generating one... Creating SSH2 RSA key; this may take some time ... Creating SSH2 DSA key; this may take some time ... Creating SSH2 ECDSA key; this may take some time ... Creating SSH2 ED25519 key; this may take some time ... invoke-rc.d: policy-rc.d denied execution of restart. *** Running /etc/my_init.d/config.sh... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 105 *** Shutting down runit daemon (PID 105)... The command finished successfully! Dockers won't start, is this related to something with the new Beta? Can you post a full syslog as well? Some things that stand out: Sep 4 23:08:28 DAMONSTER kernel: ata1.00: exception Emask 0x50 SAct 0x200000 SErr 0x280900 action 0x6 frozen Sep 4 23:08:28 DAMONSTER kernel: ata1.00: irq_stat 0x08000000, interface fatal error Sep 4 23:08:28 DAMONSTER kernel: ata1: SError: { UnrecovData HostInt 10B8B BadCRC } Sep 4 23:08:28 DAMONSTER kernel: ata1.00: failed command: READ FPDMA QUEUED Sep 4 23:08:28 DAMONSTER kernel: ata1.00: cmd 60/08:a8:c0:01:00/00:00:00:00:00/40 tag 21 ncq 4096 in Sep 4 23:08:28 DAMONSTER kernel: res 40/00:ac:c0:01:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Sep 4 23:08:28 DAMONSTER kernel: ata1.00: status: { DRDY } Sep 4 23:08:28 DAMONSTER kernel: ata1: hard resetting link Looks like something wrong with an ata device? There are lots of other errors in this syslog. Can someone with a sharper eye than I for storage-related error messages in a syslog take a gander at this? Link to comment
RobJ Posted September 4, 2014 Share Posted September 4, 2014 I cannot see any connection between the disk issues and Docker. There are 2 drive issues, one concerning Disk 11, and the other concerning an unknown SATA storage device that cannot be identified, is never set up. Disk 11 (on ata1.00, sdb) almost certainly has a poor SATA cable, causing the packet corruption (SATA error flags BadCRC etc) when first set up at speed 6.0 Gbps. Once dropped to 3.0 Gbps, there were no further issues in this syslog, but I would be VERY suspicious of more trouble under load to Disk 11. Replace the SATA cable. The one place you cannot skimp on is SATA cables. This is however a minor issue, and data traffic is retried and retried until successful. Apart from slow I/O to this drive, it should have no effect at all on the rest of the system. The drive itself by the way is almost certainly completely fine. You have an 8 port SATA controller card that is almost empty, except for the very last port. Something on that last port keeps connecting a SATA link at 1.5 Gbps (the slowest possible), but all attempts to get the device to identify itself fail. This too should have no effect at all on the rest of the system. If this device was something that Docker support depended on, then I would expect to see errors later, about a missing location. I don't have any Docker experience to help you further. Link to comment
Dimtar Posted September 5, 2014 Author Share Posted September 5, 2014 Hey everyone. I connected to the unraid web interface and deleted the two containers. I redid them and this fixed them so they are now working! RobJ, I have scanned what you said. I am away for the weekend but when I get back I would like to make some comments back about that so I can correct it. Thanks all. Link to comment
jonp Posted September 7, 2014 Share Posted September 7, 2014 Glad to hear your issue was resolved. Thanks! Link to comment
Dimtar Posted September 8, 2014 Author Share Posted September 8, 2014 Glad to hear your issue was resolved. Thanks! JonP, I have replaced the sata cable and plugged it into a new port on the board. Can I paste the new syslog here or start a new thread? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.