I have good news, I think mine is working… Here is a rundown of what I learned:
Originally did the following:
From WebGUI Settings tab, clicked “Check for Updates” and let it process the firmware update on it’s own.
After update WebGUI was slower and much less responsive. Drive was not available on the network (either by IP, or name, or wdmycloud). Was only ever able to get Cloud Access working sporadically on my phone, but now the device would not connect at all and showed as offline on the website ( https://www.wd2go.com/getDevicesInternal.do)..)
Power cycled the unit, with slightly better results, but still not usable.
Changed all shares to Media Serving OFF
Disabled (turned off) all settings that would slow down the basic config (Media Streaming, iTunes Server, SSH, FTP Access, Cloud Access, Mac Backups)
Turned Drive Sleep Off… not even sure why this is an option, or why it is defaulted to On.
Set to Static IP
Still, GUI was really slow and drive speeds were horrible
Decided to perform a System Only restore noting that this should not remove the users…
Users were wiped out, all shares were reset to Public Access ON, and system was still really slow.
Performed the same disabling and config as above to speed up remaining config (Device Name, Time Zone, Static IP…)
Still, GUI was really slow and drive speeds were horrible, and authentication was not happening
Tried the reset initiated by holding in the button for at least 10 seconds (varied reports as to the needed time from WD agents, I actually held it in for 40 seconds as that was the longest suggestion by any of the representatives I spoke with)
Performed the same disabling and config as above to speed up remaining config (Device Name, Time Zone, Static IP…)
GUI still slow, but better than other times (initial page only took about two minutes to give me a login option)
Attempted to recreate the users and reset the rights without success.
[Note, I learned this later, but it is important to state now… if users are removed by some process of the system, new users “MUST” be created and “MUST” be named something different than any old users. Some elements remain in the OS that will link users with a new name to the old credentials, with very limited success that will result in network authentication failing.]
[Note, when setting user share rights, even if it takes 30 seconds per click, only do one share/entry at a time. If you click several rights changes at the same time, you will not necessarily get those rights even if the system stops responding with “please wait” and looks like it has processed those changes. One at a time, or else!]
Spoke to Level II, who heard all of my trouble shooting and said that I had covered all of the bases and that likely the only option would be to RMA the drive… again.
Because I didn’t want to go through the trouble of copying all of the data and attempting to deal with the RMA process again, I informed him that I still wanted to try some things… I suggested that I would like to download the firmware and try the Manual Update. He agreed that that would be a valid thing to try…
Downloaded the 4.00.00-607 firmware from http://www.wdc.com/wdproducts/updates/?family=wdfmycloud_s and put it on my hard drive.
Used the Manual Update “Update from File” option and let the system have at the firmware again.
After the install and reboot… GUI was soooo much faster.
Performed the same disabling and config as above to speed up remaining config (Device Name, Time Zone, Static IP…)
Users:
After trying to recreate them and reconfigure the rights (which was still a long’ish process), users could not connect through the network (“invalid user” I believe was the error on the Windows devices). Realized that as I added back users with the same names as they were previous, some of the users were getting “some” rights to some shares automatically. This lead me to do more testing and I discovered that a brand new user with brand new share rights (selected and processed one at a time), could connect to the device from my Windows computers. Created all new users, set share rights for each user one at a time, and deleted the failed “replacement” users I had created. After this, connected to a share and saved credentials with no issue. User access restored. Note, I did not put email addresses in at this time so as to not over complicate things.
Shares:
After users were all reestablished went though all shares and turned off Public Access on all of the ones I wanted more control over and made sure user rights were accurate.
Media Server:
After system seemed stable turned Media Streaming back on. Did not turn on iTunes Server (mostly because I didn’t intend to use it, but also because I had read reports about it being a stumbling block to the performance since it hangs on some sort of file… Doesn’t matter, left it off mostly to make sure I had control over my testing).
Went to the few shares that I wanted to work with Media Streaming and set Media Serving to ON for those few directories.
Connected to the Twonky server ( http://wdmycloud:9000/ ). Configured the Navigation Tree to By Folder because I like that more. Under Sharing, set /Public to “Photos & Videos” (due to another report I had read that suggested the Media serving gets angry at some music files and hangs the system, and also to eliminate that as an issue. set my share that is just for videos to “Videos” so I wouldn’t get a whole list of other files that I don’t want (like images left over as part of WMP scanning them and so forth or music that was placed here by mistake).
Hit the share from my smartTV and all went very smooth. Interface didn’t stall or take several minutes to load the data and playback was clean and responsive.
Cloud Access:
Some of this was trial and error, here is what worked…
Deleted my device from https://www.wd2go.com/getDevicesInternal.do
Deleted my device from the app on my phone and tablet.
Turned Cloud Access, Remote Access ON.
Left the Cloud Access Connection Option for Connectivity on Auto.
Added an email address to one user.
On the Cloud Access tab, select that user
Clicked the “Get Code” button and used that code to add the NAS back on my phone and tablet.
Working very well on my phone and tablet at this time. Cloud Access shows “Connected, Port forwarding connection established”
[Note, router settings… I had previously set port forwarding for the NAS IP address for port 8080 and 8443 but it had little impact. I presently still have those ports forwarded, even though I have the NAS set to Auto so I doubt it is using them. I also took the easy way out and just put the **bleep** thing in the DMZ. This is the one area I still want to go back and research a bit, but I like that it’s working, so am leaving it for right now.]
I share all of this with you so you know that I am working, I believe, and so that perhaps my research and finding will help you or others.
on a separate share through ssh and ive noticed that throughout the copy process the speed drops, stalls, then resumes periodically. Average speed dropped as well. What is up with this firmware??