Disaster - Dockers Corrupted? Destroyed?

Help

1.Error At the bottom of my Docker list in the Docker tab.

/usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.phpon line 90

2. Within Share - AppData says to many files to list

3. Within Finder - AppDat Folder appears empty

4. Backup folder is (appears) empty

5. Usually in Settings - Docker - You get the option to delete the image, which was done, but that option is no longer there.

6. When I try to add containers, no files are pull and I get errors. Typically a Server Error and it is not recreated.

 

Only good thing is that I have all my files within share.

 

Running version 6.9.2

Here is a screenshot Docker Service

 

Any ideas? 

Edited September 1, 20214 yr by Profezor

Difficult to say much, you should share your diagnostics.

Go to Tools / Diagnostics and attach the full zip to your next post.

Will do.Thanks

On 9/4/2021 at 12:05 PM, Profezor said:

Will do.Thanks

I ran the diagnostics.

The forum will not let me upload the files. SO here is a dropbox link

https://www.dropbox.com/sh/0s08i16mat6wg90/AACZ5zhizGu43jk1CilGr9LQa?dl=0

 

Please help. I need to get the dockers back as the system is unusable for the last week.

Thanks 

Edited September 8, 20214 yr by Profezor
bad upload

The diagnostics is a single zip pile which should upload fine. 

I lost my appdata. Some how the contents of my appdata is either gone or invisible.

All my shares are still there and assessable.

 

My docker tab produces this error

Warning: file_put_contents(/var/lib/docker/unraid/images/unmanic-icon.png): failed to open stream: Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.phpon line 90

 

My question - How do I fix this? Can I reinstall all my dockers to make my system usable again? I hate to 

configure all my dockers again, but at this point I just need them back

 

My docker templates are there but won't reinstall.

 

I just downgraded to 6.9.1 to see if that would fix this docker error but no luck.

Please attach your diagnostics to your next post.

Sorry, an unknown server error occurred when uploading this file.

(Error code: -200)

 

This is the error I get when trying to upload the diagnostic files.

 

Can I give you a dropbox link?

10 minutes ago, Profezor said:

This is the error I get when trying to upload the diagnostic files.

File(s) plural? It should only be one zip file.

19 minutes ago, JonathanM said:

File(s) plural? It should only be one zip file.

That is the error when I try to upload THE SINGLE ZIP FILE.

 

Sorry, but my system has been unusable for over a week. I really need to get my dockers back and working and I am not getting anywhere. 😞

Edited September 14, 20214 yr by Profezor

I changed browsers.

Files attached

galaxy-diagnostics-20210908-0911.zip

On 9/8/2021 at 10:11 AM, itimpi said:

The diagnostics is a single zip pile which should upload fine. 

Changed browsers.

Here are the files.

 

galaxy-diagnostics-20210908-0911.zip

Unrelated, but connection problems with parity. You should shutdown and check connections, power and SATA, including splitters.

 

Corrupt docker.img. Why have you given it 150G? Have you had problems filling it? 20G is often more than enough. Making it larger won't fix filling it, it will only make it take longer to fill. The usual cause of filling docker.img is an app writing to a path that isn't mapped.

 

Why are you moving appdata, domains, system shares to the array? You want these shares to be cache-prefer so they will stay on cache. If they are on the array, dockers/VMs will not perform as well, and they will keep array disks spinning because these files are always open.

 

Set these shares to cache-prefer.

 

Disable VM Manager in Settings. Disable Docker in Settings and delete docker.img.

 

While you have Dockers/VMs disabled, run mover so those shares will get moved to cache where they belong.

 

After mover finishes, recreate docker.img, try 20G.

 

https://wiki.unraid.net/Manual/Troubleshooting#How_do_I_recreate_docker.img.3F

 

Reinstall your dockers

https://wiki.unraid.net/Manual/Troubleshooting#Restoring_your_Docker_Applications

 

You should run a non-correcting parity check just to confirm your parity connections are fixed.

 

Post new diagnostics if you have any problems or need further advice.

I have merged your threads so we can coordinate replies

Wow!

Thanks I will do the above and report back thanks.

A correcting parity check is running, so I do the above as soon as it stops.

 

Thanks again.

On 9/15/2021 at 1:07 AM, trurl said:

Unrelated, but connection problems with parity. You should shutdown and check connections, power and SATA, including splitters.

 

Corrupt docker.img. Why have you given it 150G? Have you had problems filling it? 20G is often more than enough. Making it larger won't fix filling it, it will only make it take longer to fill. The usual cause of filling docker.img is an app writing to a path that isn't mapped.

 

Why are you moving appdata, domains, system shares to the array? You want these shares to be cache-prefer so they will stay on cache. If they are on the array, dockers/VMs will not perform as well, and they will keep array disks spinning because these files are always open.

 

Set these shares to cache-prefer.

 

Disable VM Manager in Settings. Disable Docker in Settings and delete docker.img.

 

While you have Dockers/VMs disabled, run mover so those shares will get moved to cache where they belong.

 

After mover finishes, recreate docker.img, try 20G.

 

https://wiki.unraid.net/Manual/Troubleshooting#How_do_I_recreate_docker.img.3F

 

Reinstall your dockers

https://wiki.unraid.net/Manual/Troubleshooting#Restoring_your_Docker_Applications

 

You should run a non-correcting parity check just to confirm your parity connections are fixed.

 

Post new diagnostics if you have any problems or need further advice.

Midway report.

 

I have recreated docker.img

i can now see my  appdata folders in the share tab. Progress 
 

but docker service will not start. I get the following error..

 

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 682
Couldn't create socket: [2] No such file or directory
Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 866

 

Running a parity check with correction but is scheduled to run for 200 days at this rate.

I can stop and repost thee latest diagnostics or ?

post new diagnostics

37 minutes ago, Profezor said:

Running a parity check with correction

Not what you were told to do.

On 9/14/2021 at 7:07 PM, trurl said:

You should run a non-correcting parity check

 

Running non correction check. Estimate - 79 days

 

But as I said above I can't re install dockers as I get the above error message.

17 minutes ago, Profezor said:

Running non correction check. Estimate - 79 days

Does not seem a reasonable time. Are you having other read write operation on the Array ?

Please post new diagnostics.

It'a not reasonable. I am not running anything. Haven't been able to do anything for a few weeks without  my dockers.

Attached

galaxy-diagnostics-20210919-1533.zip

Edited September 19, 20214 yr by Profezor

You need check filesystem on disk 4

 

It also appears that your parity drive is having continual resets, probably due to a flakey sata / power connection to it.  Reseat / replace the cabline.

While your diags are from today, the syslog stops on the 13th, so I cannot see anything recent happening.

 

Maybe try to get them again. If it's the same, try to reboot ?

@Squid, you had better chance than me or you didn't check the date ?

I just assumed the logs got cut off.  Corruption exists on drive 4 (partial explanation for no containers), and if the server hasn't been powered off and cabling reseated, then the parity drive needs that and it also explains why the check is slow.

16 hours ago, Squid said:

You need check filesystem on disk 4

 

It also appears that your parity drive is having continual resets, probably due to a flakey sata / power connection to it.  Reseat / replace the cabline.

I will check the filesystem using the link. Thanks. and check the sata/power connections.

 

And report back. Thanks