WD is happy to announce the latest firmware updatefor My Book Live. For information about the firmware update, please check out the release notes.
Please feel free to post your experiences in this thread.
1 Like
Any specific considerations or requirements before installing this update?
The question that does not apply to me but will apply to some is if things like a feature pack has been installed or aptitude used to install and remove stuff, will that have any affect to installing this update?
Will this update remove any customisations and Linux updates?
I’m guessing some people (including me) will be a bit anxious and worried about beginning this update and it bricking the drive requiring it to be sent back to Western Digital who’s policy, I believe, is to reload factory restore it to the out-of-the-box condition.
Just follow the instructions on page 5 of the release notes. I would also check out the Knowledge Base article link that I posted for the update to see if there are any other instructions. And, as always, make sure you have your data backed up before beginning the firmware update. For the rest of your questions, I don’t know. But I’ll try to get someone else to chime in here.
Ok. Thing is…  If someone’s got a massive amout stored on the MyBook live then I can see a popular question being… “Where to I back-up my data? I not got room on any of my computers to do that.” 
I shall visit the note. Already done one update when I first plugged it in and before putting any data on it. Hopefully this and other future updates will go in just as well.
You can expect the firmware update to reimage the system files of your My Book Live to a 1.05.07 default state. Your files are stored elsewhere and will be preserved (/DataVolume should remain untouched) but any custom-installed programs will not be. While standard configuration settings (anything you configured in the Dashboard) are preserved, there’s no guarantee that any modifications made via SSH will carry over to the new update.
There are lots of fun ways to modify these drives. I know a colleague was mirroring several Ubuntu update repositories on his drive for others in tech support. apt-mirror installed great before one update, and wouldn’t install after an update. He wasn’t actually using what became version 1.05.07 so I have no idea if this update will affect your ability to use aptitude or apt-get, but that’s the point–we certainly don’t test for this use because we don’t support it.
This is a good time to remind you that these are appliances. It’s yours and feel free to modify yours all you want (I have SSH enabled on mine on principal but never did get around to installing nethack) but when it’s update time then you’re on your own. Read the release notes and decide for yourself if it’s better to upgrade and gain functionality or to stay with what you have which is working for you.
Lastly, please remember that all hard drives fail eventually and any important data should always be backed up on more than one disk! I’m a big fan of the WD Elements drives and use one to back up my media library. A spare drive isn’t exactly pocket change, but it’s far less than data recovery costs.
Good luck and happy hacking!
1 Like
I hoped that this update will resolve the MAC OS X Lion’s Time Machine AFP error, but it wasn’t. So I’m waiting again unbackuped and still hope that my laptot drive don’t crash.
Myron wrote:
I’m guessing some people (including me) will be a bit anxious and worried about beginning this update and it bricking the drive requiring it to be sent back to Western Digital who’s policy, I believe, is to reload factory restore it to the out-of-the-box condition.
Oh, one other thing of note. If you send us a drive for warranty replacement, we immediately send you a like-new, recertified unit once we receive your credit card info (for advance RMAs) or your defective unit (for standard RMAs). This gets you the fastest turnaround time possible.
Your defective drive is soon run through various tests, during the course of which all data contained on the drive is irrecoverably destroyed past the point of data recovery. (This is an intended effect and we use a test drive to verify this with a data recovery partner periodically.)
Update worked flawlesslty. Kept my slightly customised samba configuration. Had to re-apply changes to /etc/vsftpd.conf after making a back-up of the original. That’s it now. Leaving it well alone so as not to mess anything up for the major update. :smileyvery-happy:
For those who maybe interested. The update log file…
(Reading database ... 19223 files and directories currently installed.)
Preparing to replace apnc 00.12.00 (using /CacheVolume/updateFile.deb) ...
stopping duplicate md device /dev/md0
Prepare for upgrade install...
Prepare for upgrade pkg install...
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
125184 inodes, 499952 blocks
24997 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=515899392
16 block groups
32768 blocks per group, 32768 fragments per group
7824 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 27 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
preinst: current root device=/dev/md1
preinst: upgrade root device=/dev/md0
Unpacking..
Unpacking replacement apnc ...
Setting up apnc (01.05.07) ...
postinst: upgradeDevice= /dev/md0
postinst: currentRootDevice= /dev/md1
Copy image to upgrade device /dev/md0
Compare checksum
-: OK
ok 0
postinst: replaced old version 010406
mount new root file system
postinst: new version is 01.05.07
Copy current settings to the 'upgrade' rootfs...
`/etc/localtime' -> `/mnt/rootfs/etc/localtime'
`/etc/network/interfaces' -> `/mnt/rootfs/etc/network/interfaces'
`/etc/hosts' -> `/mnt/rootfs/etc/hosts'
`/etc/remote_access.conf' -> `/mnt/rootfs/etc/remote_access.conf'
`/etc/nas/UI_prefs.conf' -> `/mnt/rootfs/etc/nas/UI_prefs.conf'
`/etc/nas/service_startup/vsftpd' -> `/mnt/rootfs/etc/nas/service_startup/vsftpd'
`/etc/nas/service_startup/ntpdate' -> `/mnt/rootfs/etc/nas/service_startup/ntpdate'
`/etc/nas/service_startup/mionet' -> `/mnt/rootfs/etc/nas/service_startup/mionet'
`/etc/nas/service_startup/itunes' -> `/mnt/rootfs/etc/nas/service_startup/itunes'
`/etc/nas/service_startup/twonky' -> `/mnt/rootfs/etc/nas/service_startup/twonky'
`/etc/nas/service_startup/ssh' -> `/mnt/rootfs/etc/nas/service_startup/ssh'
`/etc/hostname' -> `/mnt/rootfs/etc/hostname'
`/etc/alert_email.conf' -> `/mnt/rootfs/etc/alert_email.conf'
`/etc/passwd' -> `/mnt/rootfs/etc/passwd'
`/etc/shadow' -> `/mnt/rootfs/etc/shadow'
`/etc/trustees.conf' -> `/mnt/rootfs/etc/trustees.conf'
`/etc/auto_update.conf' -> `/mnt/rootfs/etc/auto_update.conf'
`/etc/samba/smb.conf' -> `/mnt/rootfs/etc/samba/smb.conf'
`/etc/samba/overall_share' -> `/mnt/rootfs/etc/samba/overall_share'
`/etc/samba/smbpasswd' -> `/mnt/rootfs/etc/samba/smbpasswd'
`/etc/dhcp3/dhclient.conf' -> `/mnt/rootfs/etc/dhcp3/dhclient.conf'
`/etc/contentdir' -> `/mnt/rootfs/etc/contentdir'
`/etc/default/ntpdate' -> `/mnt/rootfs/etc/default/ntpdate'
`/etc/standby.conf' -> `/mnt/rootfs/etc/standby.conf'
`/etc/timezone' -> `/mnt/rootfs/etc/timezone'
Copy saved logs...
Copy boot links...
Shutting down changeNotifySocket:
iNotify is not running...
Shutting down MioNet:
MioNet is not running...
Verify: Now changeNotify is Not running
Verify: Now Mionet is Not running
mionetd: stop plugin
plugin_command = stop
PLUGIN_HOME = /usr/mionet/plugin
plugin launcher = miocrawler/miocrawlerd
Kill Miocrawler Process...
No miocrawler process is found
Mionet current versionID=1539
Mionet new versionID=1521
Copy existing mionet...
A reboot is required for the upgrade to take effect.
postinst complete.
Congratulations and thanks for the update! 
Nathan, that was a well-stated position statement up there!
Updated without a hitch.
TonyPh12345 wrote:
Nathan, that was a well-stated position statement up there!
Updated without a hitch.
This update was ultra-super-light lol.
Update without any problem.
Now the “Backups” option don’t give an error, but the list is empty: My Time Machine backup are not listed.
I  read through the messages on this thread and am now confused! Does this update fix the problem caused by the new Mac OS Lion ??  When I run Time Machine, it reports back an error, “The network backup disk does not support the required AFP features.”  Will running this update on the My Book LIve resolve this issue and allow me to begin backing up again? or better yet, access my earlier backups???
Thanks,
-eb
I don’t think it has been fixed yet.  I have updated my NAS and TimeMachine is still giving me an error.  I’m sure it will get fixed soon.
No - No Time Machine fix. As I mentioned in the other thread, the Time Machine fix won’t be out for a bit. We have another update coming out in the next week that WILL NOT contain anything related to fixing Time Machine. After that update, we will be working towards getting a fix in order. Please be patient… New OS’s always cause problems like this!
WDTony wrote:
… . New OS’s always cause problems like this! …
Never happens with Windows…
(* Is that crickets I hear chirping?? Or, thundering hoards *)
I would very much appreciate if someone can confirm that after update to current firmware you can still install MySQL-server. That is essential to my setup…
Thank you everyone!
WDTony wrote:
No - No Time Machine fix. As I mentioned in the other thread, the Time Machine fix won’t be out for a bit. We have another update coming out in the next week that WILL NOT contain anything related to fixing Time Machine. After that update, we will be working towards getting a fix in order. Please be patient… New OS’s always cause problems like this!
This is not acceptable!!! QNAP and Sinology are still providing uptodate firmwares…
1 Like
You are right…this is rubbish…thats what developers tools are …get ahead of the curve…
From what I have read this update is in preparation for the major update and v1.05.07 does not fix anything.
It is a puzzle why this update was released as not that long ago it was mentioned that whatever update is downloaded, it completely replaced the previous firmware with only a few essential configuration files copied from the replaced firmware to the new firmware before the previous firmware and all it’s customisations are obliterated.
Personally, I’m happy. My MBL is (hopefully) in a nice stable state where it’ll take the next update.
Would still be nice to have a PPTP server on the MBL. Now that would be a good thing for the marketing people to scream and yell about in delight. 
