WD is pleased to announce the update release of My Cloud Firmware Release 3.04.01.
- Please follow the instructions when doing the update.
Please feel free to post your questions and experiences in this thread.
2 Likes
will wait until the silence is defening 
1 Like
Ralphael wrote:
will wait until the silence is defening
Am I missing something?
I am.
Does it address the “drive self-wake up” issue?
@ Bill, @ All,
You don’t mind if I wait carefully to see the cat out of the tree do you ?Â
Like ummm who takes the first plunge…anyone ???
PS, I saw your post 19 Minutes after you posted it, without knowing you had :smileyvery-happy:
@ Ralphael,
Is it a bit like this ?
http://www.youtube.com/watch?v=K8E_zMLCRNg  <~~~ Click linkÂ
:smileyvery-happy:
LardVader wrote:
I am.
Does it address the “drive self-wake up” issue?
Firmware Version 03.04.01 -219
Resolved Issues:
ď‚·
- Resolved remote connection through www.wd2go.com web portal is blocked when updating to Java™7 Update 51.
- ď‚· Added 3 seconds of white/blinking LED to indicate the system restore upon power up function has initiated.
- ď‚· Added blinking LED to indicate the hardware reset process has initiated once the reset button on the back of the unit has been depressed long enough.
- ď‚· Added Product Improvement Program option. This option will allow WD to improve future updates by collecting information such as the product serial number during a firmware upgrade.
- ď‚· Resolved issue of NTP is still running after being disabled through the dashboard.
- ď‚· Resolved issue of support web page links from the dashboard are opening in English despite the dashboard running in another language.
-  Resolved issue of a USB drive named as “backup” will not mount when attached to the USB expansion port.
- ď‚· Resolved issue of a created scheduled safepoint is not run automatically.
- ď‚· Resolved issue of firmware update duration is taking too long to complete.
- ď‚· Resolved issue of no indication is shown when an incorrect username/password is entered when creating a safepoint on a private share.
- ď‚· Resolved issue of dashboard displays inconsistent number of media files.
- ď‚· Resolved issue of the dashboard media scanning progress displays incorrect status.
- ď‚· Resolved issue of created user names are displayed only in lowercase text.
- ď‚· Resolved issue of notification emails are still sent after being disabled through the dashboard.
- ď‚· Scheduled automatic firmware update is now randomized to occur within the selected hour.
1 Like
I just installed the update and I did not have any problems. The overall time for the download, install and reboot was about thirty minutes.
1 Like
Installed, no issues so far.
Bill_S wrote:
Ralphael wrote:
will wait until the silence is defening
Am I missing something?
it was so quiet after you posted… so I thought I would wait till either the silence is defening or until the cows comes home the cows came home…
1 Like
Finally, someone had the courage. :smileyvery-happy:
@ Cat0w, @ RealAct,
Post your Dashboard Picture here, lemme see it. :stuck_out_tongue:
@ Bill,
In order to update, do you have to remove the USB drive first if it is connected  ?
Pacific_Dollars wrote:
@ Bill,
In order to update, do you have to remove the USB drive first if it is connected ?
I was thinking the same thing… and I think you better since I don’t see a fix for that… but what does Bill say?
By design, you should be able to leave the drive attached, especially since you can set the drive to autoupdate. However, having said that, if I was doing a manual update, and there wouldn’t be an issue to safely remove the drive, then I would probably remove the drive.  But that’s just because of my experience with installing windows. I’ve had windows wipe a drive I left attached.
@ Bill,
You said: “I’ve had windows wipe a drive I left attached.”
I am now still surprised how it is possible that Bill Gates is the richest man on earth.:smileyvery-happy: It reminds me of when he attached the first time an USB device on Windows 98 and it crashed while he was doing a presentation.Â
http://www.youtube.com/watch?v=Wpj1SgQQ984 Â <~~~ Click here
Note: Â After the upgrade, check your Twonky status.
Looks like Twonky got upgraded to 7.2.6-2G  (from 2E) – and it might have a bit of an issue.
After the upgrade, the only share that Twonky was actually serving was Public, even though all of my other shares were set to ON for Media Streaming.
When I toggled the switch back & forth on one share, all the other shares started working, too.
is it just a slow adoption? or are there only 3 survivors?
Ralphael wrote:
is it just a slow adoption? or are there only 3 survivors?
+1
So far so good. I updated some 12 hrs ago and i just checked the user.log: the recurrent, random, wake-up is still there:
Mar 6 03:15:18 MCloud logger: exit standby after 7 (since 2014-03-06 03:15:11.128182002 +0100)
Mar 6 03:45:16 MCloud logger: exit standby after 1193 (since 2014-03-06 03:25:23.518182002 +0100)
Mar 6 04:12:04 MCloud logger: exit standby after 1003 (since 2014-03-06 03:55:21.068182002 +0100)
Mar 6 04:37:13 MCloud logger: exit standby after 904 (since 2014-03-06 04:22:09.028182002 +0100)
Mar 6 05:07:05 MCloud logger: exit standby after 1187 (since 2014-03-06 04:47:18.088182002 +0100)
Mar 6 05:36:15 MCloud logger: exit standby after 1145 (since 2014-03-06 05:17:10.028182002 +0100)
Mar 6 06:00:20 MCloud logger: exit standby after 840 (since 2014-03-06 05:46:20.048182002 +0100)
Mar 6 06:24:01 MCloud logger: exit standby after 816 (since 2014-03-06 06:10:25.038182002 +0100)
Mar 6 06:48:50 MCloud logger: exit standby after 884 (since 2014-03-06 06:34:06.058182002 +0100)
Mar 6 07:18:28 MCloud logger: exit standby after 1173 (since 2014-03-06 06:58:55.028182002 +0100)
Mar 6 07:41:50 MCloud logger: exit standby after 797 (since 2014-03-06 07:28:33.028182002 +0100)
