So, to preface this - I apologize, I am the very definition of an amateur hobbyist.

 

My unraid box is very simple - MSI H81i motherboard, Core i5 4440s, 8gb RAM. 2X 3TB WB RED and a Toshiba 3TB 7200rpm parity drive. No cache drive. unRAID 6.0.1. Plugins are Community Repositories, openvpnclient, Webgui, and the unRAID OS. Everything is current (per the "update" button).

 

My issues started when I updated to 6.0.1 the other day. It has been running parity checks back to back to back; it will complete one, and then restart. If I cancel one, it restarts. Additionally, maybe related (?) but my dockers are all MIA.

 

Here is a pastebin of the server log since I rebooted yesterday during my own (ineffective) troubleshooting http://pastebin.com/TUiqvkwC

 

Any thoughts? Thanks!

Whoops, wrong support forum. I've requested this thread be moved.

Hard to say for sure without the full diagnostics, but it looks to me as if there's a cron file scheduling a parity check every single minute.  All of the rest of the problems may just be because of the trouble that that is causing.  Did you possibly modify the scheduling for parity checks in the last session?

Hard to say for sure without the full diagnostics, but it looks to me as if there's a cron file scheduling a parity check every single minute.  All of the rest of the problems may just be because of the trouble that that is causing.  Did you possibly modify the scheduling for parity checks in the last session?

 

Or perhaps some cron job defined in the go file ?

Hard to say for sure without the full diagnostics, but it looks to me as if there's a cron file scheduling a parity check every single minute.  All of the rest of the problems may just be because of the trouble that that is causing.  Did you possibly modify the scheduling for parity checks in the last session?

 

If I did, it certainly wasn't intentional - wouldn't know how to if I tried. Is that something I can change in the GUI or do I need to do it via command line?

Can you describe how you upgraded?  Did you make sure that you didn't restore your old go file?  You might reread the Upgrading to UnRAID v6 guide, and comparing it with your experience, and see if that rings any bells.

 

Once you reboot, try obtaining a Diagnostics file (Tools -> Diagnostics), and attaching it here.

I upgraded from 5.x using the instructions at the link you gave me - formatted the usb stick and installed anew. I should have been more clear - I upgraded from a beta 6.0 release to 6.0.1 using the "check for updates" function on the plugins page.

 

I rebooted and when I brought the array back up, it hasn't started a parity check since - so knock on wood there. Still not sure what's going on with the dockers, but I'll keep poking around. Thanks for the help so far.

Here is the log since I started the array- http://pastebin.com/7cZG44Yw

OK, I think can add a little bit more information-

 

When I go to Docker Settings, I only see the top section - the one where I can enable/disable and define the path for the docker image. Nothing below. The log has this error:

 

Jul 15 19:30:45 unraid php: 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/dockerClient.php on line 505

Jul 15 19:30:45 unraid php: Couldn't create socket: [2] No such file or directory Done.

Please do this:

...Once you reboot, try obtaining a Diagnostics file (Tools -> Diagnostics), and attaching it here.

Whoops, missed that, sorry!

 

Attached here. Thanks.

unraid-diagnostics-20150716-1500.zip

Your syslog indicates possible flash corruption. Put it in your PC and let it checkdisk.

 

I also see some stuff about VPN in your syslog, and your docker.log has a message in it that googling makes me think there may be some conflict there. Not much help but maybe that will get you going on some research.

Thanks - I think you were correct. It was the OpenVPN client, and it's apparently a known issue. Appreciate your help!