July 3, 20233 yr Hit stop array, stuck at stopping. I already killed the nginx process that was getting stuck at /mnt/user. This sort of thing happens ALL the time. I have never once successfully shut down an array without a hard power down. I would love to know why and have it work properly for once. It is hot today and I don't want to run a parity check in the heat. root@Tower:~# tail -f /var/log/syslog Jul 2 18:06:23 Tower emhttpd: Unmounting disks... Jul 2 18:06:23 Tower emhttpd: shcmd (3779): umount /mnt/disk4 Jul 2 18:06:23 Tower root: umount: /mnt/disk4: target is busy. Jul 2 18:06:23 Tower emhttpd: shcmd (3779): exit status: 32 Jul 2 18:06:23 Tower emhttpd: Retry unmounting disk share(s)... Jul 2 18:06:28 Tower emhttpd: Unmounting disks... Jul 2 18:06:28 Tower emhttpd: shcmd (3781): umount /mnt/disk4 Jul 2 18:06:28 Tower root: umount: /mnt/disk4: target is busy. Jul 2 18:06:28 Tower emhttpd: shcmd (3781): exit status: 32 Jul 2 18:06:28 Tower emhttpd: Retry unmounting disk share(s)... root@Tower:~# lsof | grep /mnt/disk4 root@Tower:~# root@Tower:~# mount | grep /mnt/disk4 /dev/md4p1 on /mnt/disk4 type xfs (rw,noatime,nouuid,attr2,inode64,logbufs=8,logbsize=32k,noquota) /mnt/disk4/system/docker/docker-xfs.img on /var/lib/docker type xfs (rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota) tower-diagnostics-20230702-1808.zip
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.