I have been having a problem with the disks in my server not being able to mount after start up.
I noticed a problem with some of my docker containers (Specifically MakeMKV) not acting the way they should be. In order to troubleshoot the problem I initiated a reboot of the docker container itself, but instead it just hung in a started state. From there I figured that whole system reboot would be the best way to go, but I still wanted to isolate the docker container. To do this, I switched all of the docker container’s “Auto-Start” toggles to off, and initiated the reboot from inside the web browser GUI. However, on shut-down, it got hung up on “Turning off Swap” for a while. After about an hour I finally broke down and force shut down the system with the front panel button.
Upon start up, I can get to the web browser GUI and see all my disks per usual. However, since I do not have “Array auto start” on, when I click start array, the array is now in an endless “Array Starting - Mounting Disks” state. And I can’t seem to get out of it.
Here is what I have already tried…
Booting in safe mode and trying to mount the disks that way.
Starting array in maintenance mode and running xfs_repair on the disk I believed to be the problem, md1.
I have tried removing all plug-ins that may be causing the problem. And then eventually removing all plug-ins.
There is also a weird anomaly that I have seen through all of this. Two of the logical cores on my CPU are pinned at 100% oddly enough. I am not too sure if that’s related or not, but I just thought I would mentioned it.
I have attached my most recent Diagnostic. If someone could take a look at it and maybe lead me down the right path of repair, that would be awesome.
Thank you!
mecca-diagnostics-20190127-1632.zip