July 30, 200916 yr I'm not exactly sure since when this has been occurring, but I have seen it for awhile now. What I have seen is that if I press the stop array button shortly after the server has started I can see messages about "device is busy" on the console and in the web interface it changes all the drive statuses to Unformatted. What I have to do is just wait a couple minutes and then try the stop again. It was a bit scary the first time I saw it. So it looks like while the web interface shows the array as started, it apparently it isn't quite ready. I recommend that either the issue be fixed regarding the device is busy (if its a fixable bug, but I don't believe it is a bug) or the web interface should show the button as disabled with the text "Starting" and then when everything is 100% ready change the button to "Stop".
July 31, 200916 yr That is a good suggestion, would be nice to have this moved to the Feature Requests forum. The 'Unformatted' issue is a different but related problem, and we understand a fix is being planned. The individual drive mounts are what are probably causing drives to appear 'busy', because I don't know of any commands to abort the individual mounts. So mounts that have started probably have to finish, then the unmounts issued. Another time consuming part of the startup is the setup of the User Shares (if turned on), but that should be easy to abort and tear down.
July 31, 200916 yr Author While aborting would be nice, if it's too much hassle, changing the interface to letting me know when I can actually stop the array would be good enough.
July 31, 200916 yr What I meant about the 'aborting' was that I was trying to explain/hypothesize why it was taking so much time to stop, Tom can't abort previously issued mounts. Actually, to add to your suggestion, there should also be a Stopping status displayed. So the states would be: State Buttons Array All Drives and Shares When Stopped Start button is enabled array is down unmounted the initial state Starting no buttons available array is unavailable in the process of being mounted after clicking the Start button Started Stop button is enabled array is up fully mounted normal operation Stopping no buttons available array is unavailable in the process of being unmounted after clicking the Stop button By tying this in with the drive status and colored balls, I *think* this would help to avoid some of the 'Unformatted' issues too. Don't show drive status unless Array state is Started or Stopped, both of which assume all mounting or unmounting is complete.
Archived
This topic is now archived and is closed to further replies.