November 7, 201411 yr Hola, Would it be possible to add some kind of warning if the mover is running when you click the 'stop' button? Last week I was moving a few TB from the cache drive across to the array when I decided it would be a simply fabulous idea to shut down my server (forgetting that it was moving data at the time) and the result was stopping the array during the move process. The data disk in use would not unmount as it was in use and the webui kept getting spammed with a message that it was trying to unmount the disk. From memory I could also not telnet into the server at this time. As an added extension of this, though maybe a little more involved - if you press the power button on the server to initiate a shutdown and the mover is running the server could perhaps respond with a unique "beep" sequence than the normal "two beep" shutting down made by the PC speaker. Cheers
November 12, 201411 yr Just had a similar issue happen as well. Ideally this would come along with a stop/pause mover button.
August 7, 201510 yr Bringing it back, as I just ran into the same issue again... is there a safe way to stop the mover?
August 7, 201510 yr Not without diving into the shell. I am changing this to a bug as unRAID should handle it cleanly.
August 12, 201510 yr This troubles me a little, seems like an incomplete fix. If you need to stop the array, you NEED to stop the array. This blocks it. I understand the rationale behind it, which is valid, but a complete solution would seem to include ways to either inform the user why it can't stop now and/or what has to be done to 'unblock' it, or it needs to provide a 'Force Stop' option. * If it's the Mover running, user should be informed, but user may or may not know how to abort the Mover, if a stop needs to happen Right Now. * If it's a huge copy or move operation, it's assumed the user would know how to abort what they started. * If the reason for disallowed stop is unknown, user won't know what to abort, therefore may need a 'Force Stop' option. Perhaps, in the Mover case, all that's needed is a little education as to how to abort the Mover.
August 12, 201510 yr For me this is acceptable as under normal operation you want in progress acts to complete before you shutdown. However there is also the long outstanding issue of information feedback on what is causing the array to be stuck open and a force safe close option. To me thought these are different issues?
August 12, 201510 yr This troubles me a little, seems like an incomplete fix. If you need to stop the array, you NEED to stop the array. This blocks it. I understand the rationale behind it, which is valid, but a complete solution would seem to include ways to either inform the user why it can't stop now and/or what has to be done to 'unblock' it, or it needs to provide a 'Force Stop' option. * If it's the Mover running, user should be informed, but user may or may not know how to abort the Mover, if a stop needs to happen Right Now. * If it's a huge copy or move operation, it's assumed the user would know how to abort what they started. * If the reason for disallowed stop is unknown, user won't know what to abort, therefore may need a 'Force Stop' option. Perhaps, in the Mover case, all that's needed is a little education as to how to abort the Mover. I tossed with the idea to change the Mover button into Abort when it is running, at the end didn't go for it and reasoned that it is better/safer to let the mover finish rather than breaking it (accidentally?) half way... Ps. If you have installed the optional Dynamix System buttons plugin, you can do a forced shutdown/reboot by pressing CTRL while selecting the required action (this requires the powerdown plugin however).
Archived
This topic is now archived and is closed to further replies.