DO NOT UPDATE 1.02.10 FIRMWARE

[aPerson]

From: http://wdc.custhelp.com/app/answers/detail/a_id/8422

"If you have already updated to version 1.02.10 and are experiencing this issue, please Contact Us for further assistance, or create an RMA (Return Material Authorization) to replace the drive. For assistance creating an RMA, please see Answer ID 8: How can I replace a product under warranty?."

This is surely dumb advice? Why is it necessary to return the device to WD when by following the instructions posted elsewhere in this thread it's possible to upload firmware 01.02.06 and get back to a working device?

WD - you should at least acknowledge in your advice that this method of installing the old firmware is available?

[Nitnot]

Thanks a ton Spanners..!

I was almost crying when my NAS started working for the first time in 2 weeks ! All back to normal now with the downgrade as advised by you...

Kudos!

[fpardi]

Could the downgrade be accomplished by simply renaming the 1.02.06 firmware to 1.02.11 and then do a manual upgrade? How would the NAS handle this?? Just asking...

[Tom_21]

Bill_S

Why not create a 1.02.11 build from the 01,02.06 checkin point.  I'm sure you use some sort of source control tool. SVN, Mercurial.  With a higher rev number, all of use with the DOA 1.02.10 version can "UPGRADE" to the 1.02.11(aka 01.02.06) copy.   Shouldn't take more than a day to respin your bits if you ONLY change you version number.  This will be a whole lot cheaper than RMA'ing  thousands of drives.

Hope this helps your firmware team,

Tom

[Bill_S]

Thank you for the recommendation.  But, I doubt it's just not that simple, or we'd do it just like we do with the WD TV products.  With the WD TV's you can roll back to just about any version.  And that's because the WD TV firmware is fully rewritten when it's updated.  Whereas, it may be the case (and I could be wrong about this) that the NAS drive firmwares are much larger and may only be being updated.  So, with an update there may be comparitives written in the code that can't be changed, thus preventing full complete rollbacks.  Like I said, I could be completely wrong, and I haven't really asked anybody, but I have a feeling that's the case.  So, we're pretty much stuck with waiting. 

Nevertheless, we are hurrying to get this out, but we can't bypass the testing process to do so.

[Bonne]

make silence and solve the problem

[Ardvark]

---

Bonne wrote:

make silence and solve the problem

---

Err.... Bonne, I'm pretty sure bill_s is just a moderator. Likely a 20 year old kid paid minimum wage to interact with us and take down bad posts, forward information on and stuff. Having him go "silent"  wouldn't get anything done any faster.....

[Bonne]

ok!

but 'is the face of WD, sorry, wd

seriously less than zero

i love  bill_s

ogni volta che mi sveglio, ogni volta che mi sbaglio....

[svistakk]

I've downgrade firmware (to 01.02.06, I've tried also 01.02.05) - disk working stable but my mac won't auto map drive (I can't see my shares in finder under "shared", but can conect via go to.../connect to server command) and iTunes can't see shared music (media server is on).

Any ideas?

[DaveF]

I followed these instructions:

connect via PUTTY to the MybookWorld (port 22)
login as root
password : welc0me    (0 is a zero)

issue the commands:

mv /etc/version /etc/version.ori

echo 01.00.14>/etc/version

exit

Now when I go to the html page to login to the drive I get this error:

"Warning: file_get_contents(/etc/version): failed to open stream: No such file or directory in /proto/SxM_webui/admin/inc/wixHooks.class on line 1354 Warning: file_get_contents(/etc/version): failed to open stream: No such file or directory in /proto/SxM_webui/admin/inc/wixHooks.class on line 1354"

I have reset the drive, rebooted, unplugged, plugged back in, hit it, kicked it, yelled at it but to no avail.  Did I do something wrong?  At this point I can't login to the drive to flash the older version of the FW.  Dead in the water.  Any help would be greatly apprieciated.