http://supportdownloads.wdc.com/downloads.aspx?lang=en
Product Firmware > Filter by Product > My Cloud > Submit > Select your Current Firmware > Firmware Version 04.x.
dāoh!
I forgot that after āSelecting my current firmwareā from the pop-up, it went to that page; my recollection was that it immediately started a downloadā¦
Update went without a hitch.
The first I knew about this update was this email:
vent title:Firmware update successful
Event description:The firmware update was successful.
Severity:Info
Event code:2004
Event time:01-29-2016 04:27:20 AM
Firmware version: 04.04.02-105
Impressed 
Iām disapointed. The new Firmware doesnāt fix the problem about 0 Kbytes for atached USB drive. The topic about
USB external drives showing 0kb is not fixed.
Safepoints may actually work under this firmware. At least I have passed the 1TB mark and the progress is still updating in the dashboard. I hope I havenāt jinxed myself by saying this.
Edit: yep, jinxed. Just had a power failure long enough to outlast the ups and after power back, the in progress safepoint was gone (no safepoints at all on the device). I donāt understand why that should be the case.
Has anyone that completed the update to this firmware had any issues other than Royce_Lithgo with a safepoint and and_sma with the 0 Kbytes for atached USB drive?
To Royce_Lithgo and and_sma:
Have you tried a 40 second reset? or āRebootā?
I already have a safepoint that works fine on āManualā update and I certainly do not want to lose that. (I have My Cloud (A) safepointed to My Cloud (B). It takes way TOO long to re-create.
Any info would be greatly appreciated.
I have gone ahead and updated my 2TB Cloud with the new firmware. It took only 10 minutes + a few more for it to reboot and ā¦ all is well. No issues in the upgrade and after the device completes the (mandatory) scan weāll have a peek and see whats up.
Paul
Thanks Paul ā¦ please keep us posted.
Tried a 40 second (factory restore) to what end? The firmware update worked fine and the safepoint create was progressing nicely. It was only the power failure at our home which cause the safepoint create to fail.My only concern was why there was no partial safepoint after the restart.
Interesting results after the FW update. Once the Cloud rebooted itself, it did not recognize (find) my attached USB Safepoint drive. So, I powered down the USB drive and powered it back up and after a while it appeared in the Dashboard and now Iām waiting for the Safepoint scan to be populated.
More later (hopefully all good news)
Paul
Yes. I still have the problem with the 0K and the USB drive not being mounted with my Toshiba 1T USB 3.0 external USB drive.
Unable to create share
A share could not be created on a USB device (vendor: Toshiba, model: External USB 3.0, serial number: 2011111316674, file system: ntfs, label: TOSHIBA_EXT, share name: TOSHIBA_EXT).
Friday, January 29, 2016 11:53:27 AM Code 1122
It appears as if the USB drive is recognized, but the existing Safepoint is not. It reports 0 Kb available.
Iām working on it.
paul
So far, the FW update seems to have messed up the Safepoint process.
I am attempting to see if there is a workaround. The Cloud does not recognize the previous Safepoint and it also reports no space available on the USB drive. Unloading and reloading the USB drive didnāt help. The Safepoint process will not show any existing Safepoints. If you click on [+] to add a new Safepoint, the process seems to get stuck reading the drive for retrieving partitions. Iāve waited 30 minutes (never took this long before) and nothing.
Next, reboot the Cloud.
More later.
paul
Unfortunately, the Safepoint process now seems to be unable to connect to a previously created Safepoint.
From the release notes for 04.04.02-105
ļ· Resolved issue of USB volume with large directory tree causing
inaccessible/unresponsive/sluggish device behavior
I wonder if that fix messed up something else? I am still waiting for all the scans etc. to end before I pull the USB drive and reset it.
Later.
Paul
@ Morden2004
This is what I was afraid of ā¦ losing previous created Safepoints, this does not sound good at all. It takes way too long to re-create any Safepoint and the possibility of losing them is nerve racking to say the least. Just give it some time, which might be an understatement, but it once worked for me. I hope it straightens out on its own after the scans.
@ Bennor
This doesnāt sound good either. I have never used a USB drive on either My Cloud. I use my second My Cloud as a safepoint for the first.
To be honest ā¦ ever firmware update gives me the shivers!
No go. I tried several tricks and was unable to get the 04-04-02 software to see anything on the USB drive. The data is there and the file structure looks fine. I checked and scanned the drive on my Win 10 system and then I tried again. Still no luck.
So I have temporarily plugged the USB drive into one of my ASUS routers as a Samba share and Iām currently creating a new Safepoint. Iām bummed.
Paul
I donāt normally use Safepoint. But Iāve had that USB issue with that one Toshiba drive and one other generic docking station when it held a 1T drive since the introduction of the OS3 firmware. Other USB hard drives and flash drives (all smaller than 1T) seem to work fine with the OS3 firmware.
It just gets more ugly as we get deeper into it. There is a Safepoint there and I can access from Win10. When I tried to create a new one in Safepoints, the Cloud reported that āyou cannot use an previously used nameā so now I have to blow away my Safepoint and start from scratch. Fortunately, yesterday I added the WDMyCloud to my mirroring software and I have a backup on the mirror drive.
Ugly.
Paul
