Mybook live duo firmware installed on Mybook live by mistake

Hi all,

I recently bought a Mybook live 2TB drive, but once I connected it to the computer (Windows 7) the installation software did not recognize it at all. I could access the dashboard but whenever I wanted to change any of the settings the system gave me a different 5 figure error message starting with number 3. Since the drive instantaneously updated firmware when I first connected it, I decided to downgrade the firmware via SSH in hope that it would solve my problem. I followed nfozdiz’s guide to downgrade firmware via reset button, but I somehow managed to download a firmware for mybook live duo instead. Once the drive rebooted the light on it was continuously red. Currently it intermittently flashes (yellow) and I have access to dashboard and I can still access drive via SSH. I tried to install a proper live firmware again but with no success - the update log shows an error message “all drives must be present for upgrade” (dashboard alert shows message “unable to mount drive” since the firmware thinks it should have two drives). Crazy thing about it is that now I have no problem in changing settings in dashboard, but it is no use since I cannot use the drive. 

If anyone has any suggestions on what I could try, please let me know. At this point any help would be appreciated.

Easy to fix as I have done this myself just to play with the new MyBookLive Duo firmware on a MyBookLive

  1. Download mtab from http://www.mediafire.com/?66o1i6sa1cda1o6
  2. Download WinSCP from http://winscp.net/download/winscp510setup.exe
  3. Extract mtab from the mtab.zip file you downloaded in step 1
  4. Open WinSCP and SSH into the MyBookLive (login: root password:welc0me)
  5. Browse to /etc
  6. Copy mtab to /etc and when prompted, overwrite the existing file
  7. Now we can mount your data volume :wink:
  8. Download PuTTY from http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe
  9. Login to the MyBookLive via PuTTY (login: root password:welc0me)
  10. At the prompt type
    mount /dev/sda4
  11. Data volume is mounted!
  12. Download latest MyBookLive firmware http://download.wdc.com/nas/apnc-023205-046-20120910.deb
  13. Use 7-zip to extract the rootfs.img file from the .deb file you downloaded above and copy it to the root of your Public folder
  14. Download resetButtonAction.zip from http://www.mediafire.com/?42pv7zrx1kx3xkk
  15. Extract resetButtonAction.sh from the zip file you downloaded in step 14
  16. Connect to the MyBookLive using WinSCP again
  17. Copy resetButtonAction.sh to /usr/local/sbin and when prompted, overwrite the existing file
  18. Connect to the MyBookLive in PuTTY again
  19. Login and type
    /usr/local/sbin/resetButtonAction.sh
  20. Let the script do it’s thing and reboot and you are back to MyBookLive firmware
  21. Celebrate!
2 Likes

nfodiz, thank you for your prompt reply.

Can you tell me what is the location of Public folder when copying through SSH? Is it /DataVolume/shares/Public ?

Also, after entering mount /dev/sda4 via Putty, should I see any confirmation of progress (after I entered it, it seems as nothing happened)?

Thank you a lot for your help!

The easiest way to put rootfs.img in the Public folder is just to transfer it through the good old windows network to the Public folder. If you want to do it through SSH though, yes it is at /DataVolume/shares/Public (The transfer rate is lower through ssh if I remember correctly) Don’t forget to delete or overwrite the old MBL Duo rootfs.img that is there from when you ran the script the first time.

For question number 2, no you will not get a response back from mount /dev/sda4 (This is good, it means your data volume is mounted)
To verify it is mounted after issuing that command, type
mount
and hit enter
You should see it in the mounts list (This is possible because I took the MyBookLive mtab file and uploaded it for you to replace the MBL Duo one which will not let you mount /dev/sda4 (your datavolume) without some editing.
You need the DataVolume mounted so you can put the rootfs.img file in the Public folder and then you can re-run the script against the proper firmware file.

My datavolume is already mounted as you can see in the below PuTTY log but I just wanted to show you what it should look like

login as: root
root@192.168.1.6's password:
Linux MyBookLive 2.6.32.11-svn52288 #1 Wed Oct 26 18:57:59 PDT 2011 ppc

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

Disclaimer: SSH provides access to the network device and all its
content, only users with advanced computer networking and Linux experience
should enable it. Failure to understand the Linux command line interface
can result in rendering your network device inoperable, as well as allowing
unauthorized users access to your network. If you enable SSH, do not share
the root password with anyone you do not want to have direct access to all
the content on your network device.

MyBookLive:~# mount /dev/sda4
mount: /dev/sda4 already mounted or /DataVolume busy
mount: according to mtab, /dev/sda4 is already mounted on /DataVolume
MyBookLive:~# mount
/dev/md0 on / type ext3 (rw,noatime,nodiratime)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755,size=50M)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,size=50M)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw,size=50M)
/var/log on /var/log.hdd type none (rw,bind)
ramlog-tmpfs on /var/log type tmpfs (rw,size=20M)
/dev/sda4 on /DataVolume type ext4 (rw,noatime,nodiratime)
/DataVolume/cache on /CacheVolume type none (rw,bind)
/DataVolume/shares on /shares type none (rw,bind)
/DataVolume/shares on /nfs type none (rw,bind)
none on /sys/kernel/security type securityfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
MyBookLive:~#

 Here is script output from PuTTY when you run resetButtonAction.sh

login as: root
root@192.168.1.6's password:
Linux MyBookLive 2.6.32.11-svn52288 #1 Wed Oct 26 18:57:59 PDT 2011 ppc

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

Disclaimer: SSH provides access to the network device and all its
content, only users with advanced computer networking and Linux experience
should enable it. Failure to understand the Linux command line interface
can result in rendering your network device inoperable, as well as allowing
unauthorized users access to your network. If you enable SSH, do not share
the root password with anyone you do not want to have direct access to all
the content on your network device.


MyBookLive:~# /usr/local/sbin/resetButtonAction.sh


currentRootDevice = /dev/md1
upgradeRootDevice = /dev/md0

Ensure both partitions are members of the original MD device
mdadm: hot remove failed for /dev/sda1: Device or resource busy
mdadm: Cannot open /dev/sda1: Device or resource busy
mdadm: hot remove failed for /dev/sda2: Device or resource busy
mdadm: Cannot open /dev/sda2: Device or resource busy

Setting up the upgraded raid unit
mdadm: /dev/sda1 appears to contain an ext2fs file system
    size=1999808K mtime=Wed Dec 31 16:00:01 1969
mdadm: size set to 1999808K
mdadm: creation continuing despite oddities due to --run
mdadm: array /dev/md0 started.
mke2fs 1.41.12 (17-May-2010)
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

Checking for bad blocks (read-only test): done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 20 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

Copy image to upgrade device /dev/md0
3999616+0 records in
3999616+0 records out
2047803392 bytes (2.0 GB) copied, 121.793 s, 16.8 MB/s


all done, now rebooting

Broadcast message from root@MyBookLive (pts/0) (Thu Oct 18 06:04:42 2012):
The system is going down for reboot NOW!
1 Like

nfodiz, Thank You!

Worked like a charm, and furthermore my original connectivity problem is solved as well!

srdjan83, you are very much welcome and thank you for reporting back :slight_smile:

This is unbelievable! Same screwup happened to me and I got my data back! I didn’t expect that! Thank you sir :slight_smile:

Yeah man my pleasure :slight_smile: