Actually yes… so bear with me on the long winded stretch of typing…
The first time I installed OS3 I only turned off only two services at the beginning
Then inserted the USB drives of which both were giving out errors…
Then I moved one of my OS3 device from the shelf to my desktop (doing a shutdown and power up).
This time after I powered it up… I issued my script…
of course wddispatcherd is no longer a part of OS3.
Then I inserted the USB drive.
so that the USB drive gets updated on the Dashboard page…
Then I stopped it after it gets mounted.
This was the first time that I managed to mount my USB drive on OS3.
I figure it had to do with possibly the shutdown and power up (much like a small reset). Also I notice that in one of the boot up scripts they issue a chmod on all the Public folders to make public share to fix the permission problems with public.
Anyways, I run the above stop scripts on all my OS3 drives now. The reason that I don’t leave the other services running as you saw on my “Absolutely terrible! Absolutely Unusable!” post the services really play havoc on your drives if you are not careful.
I’m pretty sure one of the services are causing trouble. Also, I noticed back with 3.04, if you wait about 5 minutes after the startup, inserting a USB drive doesn’t cause a lock up. This may be the same effect that we might be seeing here in OS 3.
If however, you stop wdnotifierd and wddispatcherd in 3.04 and restart them after inserting the USB drive, then stop them afterwards, you stop the lockup.
Thus the carry-over… stopping, starting and stopping wdnotifierd; which I think all it does is update the dashboard.