Me thinks W.D. needs to look at how the WebUI received and processes the update file before invoking the update.
I’m making guesstimates here, but I have witnesed the WebUI process finish and return to the menu BEFORE scripts have completed. I spotted this whenb I was changing access to several shares. The WebUI showed that it has completed but the scripts kept running for about another minute or two.
Following my observations I will no-longer due the WebUI to perform any firmware upgrades.
It would help that W.D. actualy check their scripts as a few posts earlier to this one I’ve highlighted files relating to the web server that drives the WebUI being dumped in the rot directory of the operating system’s partition.
I think that the people at W.D. are aware of some of these bugs but because “it works” thry choose to be lazy and not fix these upgrade script problems. The evidence is quite clear and concrete.
