March 18, 20197 yr I upgraded from 6.5.3 to 6.6.7, and now the docker and vm manager are not responding. When I enabled docker, I get Docker service failed to start error. The vm manager just keeps spinning. The server has been up for over 30 minutes now, and two of the cores still at 100% (showing in the dashboard) I could not cd to my cache, but it doesn't say that it is "unmountable" I could not open the log after clicking it I think I found what causing some of the CPU cores to load at 100% - the parity check. No matter what I do, the parity check keeps running. If I disable it before turning on the array, then enable docker then the damn parity would start running again. It has been 7 hours now for the parity check, but the docker is still in Starting services. And could not get the diagnostic file. I have never had luck upgrading my server. Should I go back to 6.5.3 and stay with it? See screenshot for core utilization
March 18, 20197 yr Author I couldn't login to the console. Somehow when I try to type in root, I get ^R^O^O^T as an output. Sent from my ONEPLUS A6003 using Tapatalk
Archived
This topic is now archived and is closed to further replies.