I meant the shutdown issue. I have been initiating shut down with the power button since when I tried it from the web GUI it froze. But this morning after shutting down, when I brought it back up the array was stopped and it should not have been. So I reverted back to rc12a for now. No idea what causes it, but I'll check out rc13 back on my primary unRAID to see if that ends up showing the same issue.
This is 99.9% likely a plugin issue, not a core release issue. I have had many issues with the web GUI and they are always related to a plugin process hanging or not failing gracefully. Try removing all your pulgins and you'll probably have no issues.
When this crops up for me, I can telnet in and look for webGUI hook that is stuck. Since almost all plugins have some shutdown action on array stop, you'll likely see one of your plugins is not shutting down properly and not returning properly, so the GUI is waiting for it to complete - usually a permissions issue, broken download URL, or something like that. From there you can either try and fix the shut-down problem, or alert the plugin author that there is a case that the plugin does not exit gracefully.
Cheers,
whiteatom
Since plugins will be supported in 5.0 final, it would seem that the plugin spec should specify how plugins should handle these scenarios more gracefully and with appropriate error logging. Either that or the webGUI should have a time-out period to go ahead and kill the plugin if it does not respond in a reasonable amount of time. Perhaps both would be the most reliable.