- Minor
I followed the instructions to zero out a data drive for removal while keeping parity ( https://docs.unraid.net/unraid-os/manual/storage-management/#notes-1 ). It just finished the zeroing process and the next instruction is to stop the array and all I got was:
Nov 11 21:32:07 storage emhttpd: Unmounting disks...
Nov 11 21:32:07 storage emhttpd: shcmd (602): umount /mnt/disk1
Nov 11 21:32:07 storage root: umount: /mnt/disk1: not mounted.
Nov 11 21:32:07 storage emhttpd: shcmd (602): exit status: 32
Nov 11 21:32:07 storage emhttpd: Retry unmounting disk share(s)...
Nov 11 21:32:12 storage emhttpd: Unmounting disks...
Nov 11 21:32:12 storage emhttpd: shcmd (603): umount /mnt/disk1
Nov 11 21:32:12 storage root: umount: /mnt/disk1: not mounted.
Nov 11 21:32:12 storage emhttpd: shcmd (603): exit status: 32
Nov 11 21:32:12 storage emhttpd: Retry unmounting disk share(s)...
Nov 11 21:32:17 storage emhttpd: Unmounting disks...
Nov 11 21:32:17 storage emhttpd: shcmd (604): umount /mnt/disk1
Nov 11 21:32:17 storage root: umount: /mnt/disk1: not mounted.
Thankfully my array is not set to auto start so i issued the reboot command which after a couple minutes forced it to stop its endless looping and restarted the server. I completed the following instructions and removed the drive without issue.
** I attempted to umount it myself and it did confirm it wasn't mounted. I had thought about mounting something fake in its place just to get the script to move along but i worried that might do something unintended.
Also I'll add that the command given in the manual and the user script had dd targeting /dev/md1 but i had to target /dev/md1p1 in order to get it to actually run. I have it running a correcting parity check right now, 200GB into 4TB and 0 errors thus far, I'll report in the morning if it finds anything wrong.