New Firmware Version 1.02.12 for the My Book World I & II (10/19/11)

now i cannot log in to the Time Machine backup AT ALL. 

No matter what I do, I cannot log in.

WD_Backup account just does not work. UGH!!!

After my automatic upgrade to the new firmware, Time Machine started to work. It took around 10 minutes to upgrade to the new firmware level. I can connect to the network shares also in 30-40 seconds. Be sure that your computer and Mybook is on the same workgroup/domain…

Itunes can not stream still.

Thanks WD. 

After installing this update, I sadly have to report that (for me at least) this update is complete garbage.  I’m re-deploying 01.02.06 installing opware and the homebrew Netatalk that fixes the issue.  Sure I will STILL have to disable crappy Twonky or I’ll get lockups but at least it will work.

Same here. After upgrading to 1.02.12 I solved all the problems about network stability but:

  • it takes 20 - 30 seconds to connect to shares as a registred user (with previous firmware il took no more than 2 seconds) on Mac machine; no delays on Windows machines;

  • iTunes can not stream: it tries to connect with no results.

Please WD help us to fix our problems: MBWE II was great, fast, affordable with previous firmware!

Hello to everyone.
Even for me it’s the same thing: I have a home network managed by a router and two netgear switches with Mac Snow Leopard. The connection times with TM have become very long, while with the older firmware were instantaneous.
The same happens when I connect as a registered user to shared folders.
I updated the FW 1.02.10 in September and I expected the new firmware without doing anything. I have full confidence in the development of the WD stuff. :wink:

well, i took my MBW to a computer tech friend of mine and he’s said the drive is knackered. there was nothing wrong with the drive before we did the update. i have to now employ the services of a data collection company to get the 10 years or so of documents, travel and family photos we have on that. costing between $700 and $1500 to do so. this will not be the last we hear of this saga.

@kimmyjus before you fork out those sums… have you first tried connectng via Ethernet? If that fails too, you could open up the MBW ( http://www.instructables.com/id/Disassembling-MyBook-World-Edition/)) and connect the disk to a machine running Ubuntu (or any machine that can read linux partitions), and from there you should be able to access the data…

another thing my MBWEII cannot do is send out a test email.

i used to get emails whever we lost power, but i can’t have that now because the NAS cannot send out email wirelessly.

So now I can’t log into the TIme Machine account at all.

Is a new firmware being developed for this?

Jazzwhistle wrote:

@kimmyjus before you fork out those sums… have you first tried connectng via Ethernet? If that fails too, you could open up the MBW ( http://www.instructables.com/id/Disassembling-MyBook-World-Edition/) and connect the disk to a machine running Ubuntu (or any machine that can read linux partitions), and from there you should be able to access the data…

i did try the ethernet connection and the tech friend i have did exactly your suggestion with removing the disk and mounting it on a linus reading device. that’s where he concluded it is the actual drive that is knackered.

The firmware would not have broken the drive.  You cant blame anyone for you not making a backup.  The mybookworld is a consumer drive at best, and should be treated as one.

Umpa2011 wrote:

The firmware would not have broken the drive.  You cant blame anyone for you not making a backup.  The mybookworld is a consumer drive at best, and should be treated as one.

My issue is that the drive was working 100% fine before the firmware update, then immediately after the update, it stopped working. I am no techie, so I dont know what went wrong. What I;ve been told is the drive is knackered.

And yes, in my naivety, i neglected to make a backup of my backup. I’ll then have to make a backup of that backup of the original backup, just in case the 2nd backup fails as well.

Seriously though, I will now be making a backup of the replacement backup. Hard lesson learnt on that one.

I certainly wont be buying a HDD with a firmware component again.

Thing to realise is - is the firmware does *NOT* update the firmware on the drive as far as I know, you should think of the nas as a low powered Linux PC.  The firmware updates the software on the drive, but not the electronics of the hard drive.  I don’t know if it updates the computer side of the electronics, but my initial thought is that it does not hence you can downgrade quite easy to lower firmware versions.

I remember when peoples xboxs’ went RROD after a forced update - people said what you did ‘it was ok before’ but the fact was it would have gone RROD simply on the next power cycle in any case.  In your case if the drive its self has crapped out then I think it was purely coincidental that it did it after the firmware update.

For what its worth I have also lost data when my 8TB ShareSpace crapped out, it was a software/firmware issue after update. The drives were fine, but the software on them prevented it from booting.  Also because it was a striped raid it meant plugging them in to a PC to recover the data was not an option for me.  I sent the unit back for a replacement.  It would have been impossible to backup that amount of data anyway.  It takes the ShareSpace 16 hours to rebuild its own array lol.

Bottom line is (I have found from experience) is to NOT upgrade your software/firmware if you don’t really need to. Its not worth the risk of losing the data.  I don’t mind on my MBWE’s because I have 5 of them and like to tinker (you should see the software that can run on them) - its awesome, but my sharespace will never ever get updated no matter what new features come out. I simply can’t afford to lose all my home videos, photos, sound recordings etc…  Basically I have entrusted WD with my digital life and have been bent over by them - I won’t do it again - lol.

Don’t get me wrong I like the ShareSpace and MBWE - but even the ShareSpace regardless of how WD market it is a low cost consumer Item, you would pay more for just the BOX for a Qnap.  I guess you get what you pay for.

actually it’s the firmware that damaged his hdd … how i know that? … cause that’s exactly what happend to my mirror drive RIGHT after i installed the DOOMed .10 firmware … it became “degraded”

All I can say to that is LOL.  

Kareem wrote:

actually it’s the firmware that damaged his hdd … how i know that? … cause that’s exactly what happend to my mirror drive RIGHT after i installed the DOOMed .10 firmware … it became “degraded”

Perhaps you should fit it in a PC and use Spinrite on it.  Look it up at GRC.com or use some other HD maintenance software.  The firmware Could NOT do this - seriously have you understood anything in my other post ?

Power cycling on and off whilst the software is still being written might give rise to some bad sectors and the all common click/click/click sound, but there is *NO WAY* this firmware flashed the hard disk and screwed up your hard disk.  I have never ever had to flash a hard drive in my life, to suggest it did is silly.

 Look I also think the new upgrade is garbage, but lets stick to comon sense here.

i’m just telling what happend … don’t care if you think this HOLY firmware can never damage the HDD … that’s what happend with me …period

does RMA means in any way that WD would replace my damaged HDD?

If under guarantee of course WD will replace it, but thats not the issue here is it !

i’m just asking cause BBBBBrandon is helping me to try get my data back from one of the drives and he asked for my NAS serial for RMA after i told him about the degraded drive issue caused by the firmware upgrade… so it may be kinda relevant :slight_smile:

If you RMA the device, chances are you will get a refurb back. If your in raid 5 then you wont lose your data because the device will re-build the array - however if your in stripe 0 mode your screwed.  Best option would be to run spinrite on the disk, see if it can fix the drive, put it back in the mbwe & see if you can boot it.  If so then copy your data to another drive and  then RMA it.

Its unfortunate that this problem arose but I seriously doubt the firmware caused it.  Chances are it was on its way out anyway.

Does anyone know if WD is working on a new firmware to fix this? The last go-round between .10 and .12, the staff were posting regularly in the thread. Unfortunately, they were hit with a lot of anger (don’t get me wrong, I’m NOT happy here, but I don’t want to shoot the messengers.)

Just wondering if anyone knew of any updates.