- Solved
- Minor
EDIT: Solved. There was a VM still running. Once ALL VMS and Docker images were stopped, I was able to shut down the array.
I have a new 4TB drive I want to add to the array, but when I attempt to stop the array, "Stopping services..." hangs.
- No Docker images are running
- No VMs are running
- Main->Stop array:
Results: All array buttons are disabled or non responsive. Only way to return array to normal operation is to do a (clean) reboot.
syslog:
May 31 01:22:06 Tower kernel: mdcmd (36): nocheck cancel
May 31 01:22:07 Tower emhttpd: Spinning up all drives...
May 31 01:22:07 Tower emhttpd: read SMART /dev/sdg
May 31 01:22:07 Tower emhttpd: read SMART /dev/sdd
May 31 01:22:07 Tower emhttpd: read SMART /dev/sde
May 31 01:22:07 Tower emhttpd: read SMART /dev/sdb
May 31 01:22:07 Tower emhttpd: read SMART /dev/sdf
May 31 01:22:07 Tower emhttpd: read SMART /dev/sdc
May 31 01:22:07 Tower emhttpd: read SMART /dev/nvme0n1
May 31 01:22:07 Tower emhttpd: read SMART /dev/sda
May 31 01:22:07 Tower emhttpd: Stopping services...
May 31 01:22:07 Tower emhttpd: shcmd (85): /etc/rc.d/rc.libvirt stop
May 31 01:25:06 Tower nginx: 2022/05/31 01:25:06 [error] 5039#5039: *1384 upstream timed out (110: Connection timed out) while reading upstream, client: 127.0.0.1, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "localhost", referrer: "http://localhost/Main"