September 15, 201213 yr I'm trying to add 4 more drives that have been precleared but when I run unmount from the web page the cache drive won't unmount. I am guessing it's because of the modules I have installed. Is there a manual way to shut it down so I can add the drive? Even after all these years with UnRaid my Linux skills suck
September 15, 201213 yr Well the cache drive is no array drive, so there must be files open on the array, did you stop all addons and devices that connect to the server? You could try the powerdown command, if the powerdown script is installed, or the shutdown now command. Don't know if this will be clean though.
September 15, 201213 yr Well the cache drive is no array drive, so there must be files open on the array, did you stop all addons and devices that connect to the server? You could try the powerdown command, if the powerdown script is installed, or the shutdown now command. Don't know if this will be clean though. The add-on powerdown command has absolutely NOTHING in it to deal with the cache drive or processes with files open on the cache drive. It will not help with un-mounting the cache drive if a file on it is open. The array will NOT be stopped cleanly. (It was written before the cache drive was added to unRAID, and never updated to include it in its steps to stop the array) (The "shutdown now" command does even less to stop the array cleanly)
September 15, 201213 yr Author All drives in the arry say stopped. The Cache drive still says Unmounting and the status says Stopping. Sooo... I can't add a device. Not sure what to do at this point. Reboot from the command line? If I do that it will kicj off a parity check, and I will have to wait for that to finish before trying to stop the array again.
September 15, 201213 yr All drives in the arry say stopped. The Cache drive still says Unmounting and the status says Stopping. Sooo... I can't add a device. Not sure what to do at this point. Reboot from the command line? If I do that it will kicj off a parity check, and I will have to wait for that to finish before trying to stop the array again. Type lsof /mnt/cache and fuser -mv /mnt/cache and see what process is keeping the disk from being un-mounted. Then, type kill PID where PID is the process ID number. The disk should then un-mount (as unRAID is continually trying to un-mount it) Joe L.
September 15, 201213 yr Sorry, I stand corrected. Learning here every day. No problem... I had to go look at the code myself, as there are several other things neither unRAID or the powerdown script does not check for. (swap files, mount points for other file systems) I never remembered the powerdown script looking at the cache drive. Not sure if we even had a cache drive when it was originally written Or if unRAID waited for the cache drive to be un-mounted before the array was stopped on older versions. (I almost never run with a cache drive unless testing something)
Archived
This topic is now archived and is closed to further replies.