Ah yes, 2.10.310…
First off, why when there is a firmware update does the EX2 go through registering the product again?
Second, why no fix for the ridiculous behaviour of the drive LEDs during power save?
Ah yes, 2.10.310…
First off, why when there is a firmware update does the EX2 go through registering the product again?
Second, why no fix for the ridiculous behaviour of the drive LEDs during power save?
Hello,
Thanks for bringing your concern to us. We have passed this for further investigation.
Does resetting the unit makes any changes on the lights?
Here seems that the solutions about all problems is RESET THE DEVICE…
There are a klot of problems that WD ignored and they are all explained in this forum:
lights red
ADS won’t work
E-mail notifications won’t work
I’m wondering if u read the forum or just ignoring the user’s notifications
Sounds like a stock response to me too Simone. I for one am beginning to wish I’d bought a QNap or Synology NAS instead.
that’s right, i’ve done a mistake buying a WD… support is terrible, WD should continue to make HDD only
I’ll stay on firmware 1.05.36, until this will be fixed.
There is nothing new for me on OS3 version except fast working GUI, and it is the last feature that i need.
And as for me EX2 is:
So it is quite good for home use.
I don’t like only the new firmware with its LED behaviour and all other bugs, that described in this community.
Take a look at this Idea posted by @Felix_The_Cat . I recommend you vote by hitting the “like” button.
https://community.wdc.com/t/my-cloud-ex2-leds-behavior-with-firmware-2-10-302/67555
Hello,
The following KBA’s may assist with your BLUE/RED LED questions.
The front Hard Drive LED on a My Cloud Mirror or My Cloud EX2 remains solid blue
http://support.wdc.com/KnowledgeBase/answer.aspx?ID=13173
The front LED on a My Cloud Mirror or My Cloud EX2 displays solid red
http://support.wdc.com/KnowledgeBase/answer.aspx?ID=13175
Regards,
Samuel Brown
Sorry Samuel,
but we are not arguing that the new LED behaviour is not “in line” with new 2.10.xxx firmware, so there is no point to address us to KB.
We are saying that the new LED behaviour is irrational and should be restored to old 1.05.36 FW behaviour, with LED 1 and 2 OFF during stby.
WD should listen requests on forum. The new 2.10 FW is a stumble (and not only for LEDs) !!!
Hello,
We are saying that the new LED behavior is irrational and should be
restored to old 1.05.36 FW behavior, with LED 1 and 2 OFF during stby.
Understood.
The feedback provided has been escalated to the appropriate parties within our organization.
Thanks
Samuel Brown
A month later WD at last understood, what exactly we want.
One of the community mods escalated this issue to WD Support. Since then I’ve had a few emails, the first pointing me to the KB, the next accepting our point of view, then a THIRD again pointing me to the KB outlining the new behaviour, again!
So I’ve done another “self-escalation” stating in no uncertain terms:
“Yes we KNOW what the KB says about the new behaviour. We just hate it! We want the old behaviour back. It is simply incongruous to have a so-called power save sleep mode with all the LEDs ON”.
Me thinks the bright spark who thought up the “new behaviour” doesn’t want his/her pet feature canned. Well WE DO!
Maybe WD could post a list of what “improvements” they are proposing for future updates to gauge feedback before implementing them. I’m still struggling to understand why they changed what was perfectly logical behaviour for the LEDs.
Here are two more issues to add to the list, one of which was also present in 2.10.302: