January 6, 201016 yr I've hit on Stop Array withing "unRAID Main" (in unMenu) with cecked box "Sync" and it just won't return nor stop the array! Any hint as to what I may do? Thanks!
January 6, 201016 yr I've hit on Stop Array withing "unRAID Main" (in unMenu) with cecked box "Sync" and it just won't return nor stop the array! Any hint as to what I may do? Thanks! What is happening on the unRAID page when used on its own? Newest versions of unRAID will NOT shut down unless all the disks can be un-mounted. A disk cannot be un-mounted if it is busy. A disk is busy if a file on it is open, or if a process is using it as the current directory. So... basically, stop any add-on processes you might have that are keeping your disks busy and unRAID will stop. If you "cd'd to a /mnt/disk, then log off or "cd" elsewhere. If your "Mover" script is currently moving a file from cache to a disk, wait for it to finish the move. The lsof command will let you know what is happening Type lsof /mnt/disk1 lsof /mnt/disk2 etc... To see the open files or processes with a disk as a current directory. Joe L.
January 6, 201016 yr Author Some time after a fresh reboot, first I noticed that the disks do not spun down, then checked cache_sync (called -w -B from go, just before last call to unMenu), killed it completely. However, cache_dirs and spinning down has been working. The main unMenu page showed that all drives are OK, no errors, everything clean. Syslog showed basically the same. I checked asap with fuser and there were no remaining processes. Same with lsof. Sync on the command line just couldn't terminate either. Ctrl-C didn't stop, only closing the terminal window and opening a new one was good. Now, 8 hours after, all disks are spun down and sync on the command line peforms well and exits. The array is still running and I get unRAID Main. Stoping the array works also (I just wanted to add one more precleared drive). Maybe some timeout has been elapsed since? lsof still doesn't show anything. Still a little confused but will start cache_dirs -w -B again and see what happens.
Archived
This topic is now archived and is closed to further replies.