I tried going to my nzbdrone docker, but it said it couldn't connect, or some such error.  I tried to remove it, but it failed, and I didn't capture the error sorry.

 

I decided to just shut down and reboot the server.

 

Now, when it's booted back up, docker won't even start.  I have it set to load the image here...

 

/mnt/disk10/docker

 

I checked, and this seems to still exist at this location, but when I click start, it tries, then comes back to showing as stopped.

 

I did another shutdown, confirmed the machine turned off, then turned it back on, and tried again with the same results.

 

This is all with beta9.

 

I've started a parity check, but the last one I stopped said it was going to take 22 DAYS to finish, which is absurd.

 

Something is obviously wrong with my server, but I don't know what.

syslog.zip

The syslog is showing a continual stream of errors for disk10.  It is continually showing an error and being reset by the system.  This probably explains your docker issue, and also why the parity check predicted time was so long.

 

I would suggest you first get a SMART report for disk 10 to see if it shows anything.  I would also recommend powering down the server and carefully checking the power and SATA cabling to that disk.