So i was installing that rutorrent docker from @Capt.Insano but  the docker run command failed at the end and now dashboard and docker page is showing that their are no docker installed to show but still i can access all my dockers.

their is also a warning that is appearing on both dashboard and docker page.

 

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 673 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 853 Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 673 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 853

 

i will be attaching the diagnostics with this post. if anyone knows how to fix this then in that case in any kind of help will be appreciated.

unraid-diagnostics-20170506-1515.zip

 

So guys i just ran scrub test and its showing one uncorrectable error.

Edited May 6, 20179 yr by Max
Some more info

Docker image is corrupt, probably due to the frequent ATA errors on disk1, replace cables and then delete and recreate docker image.

 

If errors persist it may be a bad disk.

Edited May 6, 20179 yr by johnnie.black

Quote

Docker image is corrupt, probably due to the frequent ATA errors on disk1, replace cables and then delete and recreate docker image.

 

If errors persist it may be a bad disk.

i guess you forgot who i am.

So let me remind you i am that same person that was a couple of days back  was having some trouble with unraid so you suggested me to replace the cable so i did.

So is their any way to make sure that its a bad disk

Edited May 6, 20179 yr by Max

Make sure you also replace the power cable, also run an extended SMART test, but sometimes a flaky disk can pass the test, if issues continue use another disk.

Edited May 6, 20179 yr by johnnie.black

2 hours ago, johnnie.black said:

Make sure you also replace the power cable, also run an extended SMART test, but sometimes a flaky disk can pass the test, if issues continue use another disk.

i guess i did change the power cable, don't remember for which one disk1 or disk2.

Could you please tell me where to look for that error.

On the syslog, multiple entries like this:

May  6 14:57:49 Unraid kernel: ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
May  6 14:57:49 Unraid kernel: ata6.00: irq_stat 0x00400040, connection status changed
May  6 14:57:49 Unraid kernel: ata6: SError: { PHYRdyChg 10B8B DevExch }
May  6 14:57:49 Unraid kernel: ata6.00: failed command: READ DMA EXT
May  6 14:57:49 Unraid kernel: ata6.00: cmd 25/00:40:a0:eb:72/00:05:62:00:00/e0 tag 23 dma 688128 in
May  6 14:57:49 Unraid kernel:         res 50/00:00:6f:85:26/00:00:5d:00:00/e0 Emask 0x10 (ATA bus error)
May  6 14:57:49 Unraid kernel: ata6.00: status: { DRDY }
May  6 14:57:49 Unraid kernel: ata6: hard resetting link
May  6 14:57:54 Unraid kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May  6 14:57:54 Unraid kernel: ata6.00: configured for UDMA/133
May  6 14:57:54 Unraid kernel: ata6: EH complete

 

@johnnie.black

Just now i was trying to delete docker image so i order to delete docker image it tried to stop the unraid array but then it got stuck at unmounting disks so i had to hard reboot.

So now after deleting docker isn't loading properly.

Its like this.

2 minutes ago, Max said:

@johnnie.black

Just now i was trying to delete docker image so i order to delete docker image it tried to stop the unraid array but then it got stuck at unmounting disks so i had to hard reboot.

So now after deleting docker isn't loading properly.

Its like this.

Stopping the array isn't the correct procedure, and I doubt you could delete it with the array stopped anyway since all disks would be unmounted.

 

What you should do is go to Settings - Docker and stop docker then it will let you delete it and recreate it from that same page.

 

So how did you delete docker?

 

Your screenshot is unclear. Is that the Docker page or the Settings page?

1 minute ago, trurl said:

Stopping the array isn't the correct procedure, and I doubt you could delete it with the array stopped anyway since all disks would be unmounted.

 

What you should do is go to Settings - Docker and stop docker then it will let you delete it and recreate it from that same page.

 

So how did you delete docker?

 

Your screenshot is unclear. Is that the Docker page or the Settings page?

that's the docker page.

Actually earlier in docker settings page delete option was not appearing, so thought maybe they appear after stopping the array.

i dont know why the status says its stopped.

Change Enable Docker to No

 

Why do you have it set so large? You must be doing something wrong if you are filling up 40GB. I've never heard of anyone needing more than 20 unless they were doing something wrong.

 

Have you read the Docker FAQ?

 

 

1 minute ago, trurl said:

Change Enable Docker to No

 

Why do you have it set so large? You must be doing something wrong if you are filling up 40GB. I've never heard of anyone needing more than 20 unless they were doing something wrong.

 

Have you read the Docker FAQ?

 

 

okay set it to "no" now, what's next how am i going to use dockers after disabling it.

As for docker image being so large, Actually earlier when my docker image got corrupted fix common problem plugin reported that it could be docker image is full, so at that time when i created a new image i also increased the size of it for just in case.

But after that i kept an eye on it so now i know i never used more than 5.5 gigabyte, so yeah im not doing something crazy.

@trurl @johnnie.black So after a reboot somehow docker page loaded fine but after still dockers were not working properly so i had to delete the docker image again.

I just ran scrub test on disk and now its showing this error.

Edited May 6, 20179 yr by Max

1 hour ago, Max said:

I just ran scrub test on disk and now its showing this error.

 

I assume that is disk1, btrfs is not very tolerant of hardware issues like those frequent ATA errors, you'll need to get to the root cause of that and reformat disk1.

1 minute ago, johnnie.black said:

 

I assume that is disk1, btrfs is not very tolerant of hardware issues like those frequent ATA errors, you'll need to get to the root cause of that and reformat disk1.

okay btw did u find any error for disk2 or its irrelevant to ask cause their is no data on it.

Only disk1, but if disk2 is not in use it's much less likely to show any issues (if there are any).

1 minute ago, johnnie.black said:

Only disk1, but if disk2 is not in use it's much less likely to show any issues (if there are any).

okay, thanks.

@johnnie.black could it because of some bad sata ports of my motherboard cause my new setup is like this -- disk which was earlier disk1 is now disk2 and the disk which earlier disk2 is now disk1 so i ran extended self test on both the drives, so the disk2 which was earlier disk1 the one which was showing those ata error passed the extended self test but the disk1 which was earlier disk2 the one which wasn't showing any errors suddenly gone missing in the middle of extended self test.

 

So the reason behind me thinking it could be bad sata ports of motherboard is that i also interchanged the powercables and sata ports.

Bad cable is more common but a bad port is certainly possible, you have two other free ports so try one of those.

22 minutes ago, johnnie.black said:

Bad cable is more common but a bad port is certainly possible, you have two other free ports so try one of those.

okay this time im trying a different sata port but now its giving Interrupted (host reset) error.

unraid-smart-20170507-1245.zip

Edited May 7, 20179 yr by Max

@johnnie.black @trurl guys i could really use some help over here.

Get a new board?

36 minutes ago, johnnie.black said:

Get a new board?

Yeah that's what i thought, so now trying out those out drives on my main video editing rig.

Will run smart extended test on my main rig just to be sure that my drives aren't at fault here.

You clearly have a hardware problem somewhere, you have to replace/swap one thing at a time to start ruling things out.

19 minutes ago, johnnie.black said:

You clearly have a hardware problem somewhere, you have to replace/swap one thing at a time to start ruling things out.

Hmm, my current setup should tell me whether my hard drives and sata cable aren't fault here (so far from the looks of it, it looks like they are gonna pass cause they have already passed the point they used to fail earlier).

Then i will test those back with my unraid server rig just with different power supply, if it fails then that should mean my board is at fault but if it passes then that should mean my power supply is at fault.

Right?

Let me know if I'm an idiot and I'm doing it all wrong.

@trurl @johnnie.black so guys it turned out to be a psu related issue, so just yesterday i bought a new one and ran smart extended test and it ran find but after that i also ran that scrub test but it's giving me this error on disk.

So what should i do now?