Recent Forum Posts
From categories:
page »

Hi Teinturman,

I tried your script, which could actually do what I need, however, while it works well when invoked from the shell (/etc/init.d/S15wdc-heat-monitor start), it does not work when left to run after startup. It is almost as if the first time it is run it sets the fan at the correct speed, but after, even if present in the task list when I invoke ps aux, it does not run anymore, because the fan does not change its speed with the drive temperature. I cannot understand why, can you enligthen me?


Hi, I am having the same problem. Did you ever figure that out?

I was trying to achieve this with no luck yet. There is no direct rsync ssh access to ACD and the tools that I could find to run in linux requires either a python version I cannot make to work in WD live duo or a go implementation but compiling it for ppc32 is a pain and still couldn't solve it.

Has anyone managed to do this?

Amazon Cloud Drive by TioBorrachoTioBorracho, 03 May 2016 14:05

Yes you do want the disk running all the time. It's the stopping and starting of the disk which wears out the disk and makes it fail sooner. The only advantage of the disk sleeping is that it produces less heat - but you can fix that with a 80mm USB powered fan underneath the MBL.

MyBookLive Duo 4T
FeaturesPacks, Twonky, ownCloud

Try here: My MBWE stuff
So let me know it it works for you.

See link below:


There is one more issue.
If you've never updated the firmware the folder /var/upgrade does not exist.

So in the script bellow you have to check if that folder exists and then to run the unpack

  1. execute the file - it unpacks itself to /var/upgrade

<IF NOT EXIST CREATE THE FOLDER /var/upgrade similar as in the begining>


GUIDE 1) For those wanting to replace the script so the script will run by simply pressing the reset buton

1) Download from
2) Download the latest firmware from

3) Download 7zip from

4) Install 7zip and point it to the MyBookLive firmware “apnc-023205-046-20120910.deb” and double click and you will see “data.tar” where you will again double click and be presented with a “.” Double click the “.” then double click “cache volume” then double click “upgrade” and then highlight “rootfs.img” and hit extract

5) Copy rootfs.img to the root of your Public folder on the MyBookLive

6) Unzip from the zip file downloaded in step 1

7) Windows users download WinSCP from
7a) Mac users download CyberDuck from

8) Enable SSH access on your MyBookLive by going to

9) Windows users start WinSCP and enter the login info…Host: mybooklive Username: root Password: welc0me
9a) Mac users start CyberDuck to login to the MyBookLive using SFTP Host: mybooklive Username: root Password: welc0me Port: 22

10) Browse to /usr/local/sbin and copy from the MyBookLive to your computer so you have a backup

11) Copy that you unzipped in step 6 to /usr/local/sbin and when asked, overwrite the existing file

12) To execute the script press and hold the reset button on the MyBookLive for 5-6 seconds or until the LED starts blinking red

13) The LED will blink red while the script is restoring a fresh copy of the firmware to your MyBookLive

14) After several minutes, the drive should reboot and when you get to a solid green LED, access the dashboard and you should be asked to choose your language like you would if the drive was brand new

15) If your shares disappeared on the MyBookLive, fear not, the data is still there and you just need to recreate the shares under the dashboard again and all your data will be there

16) Please note, you will need to overwrite at /usr/local/sbin any time you restore or downgrade the firmware on the drive as it will overwrite the modified script file

[url=]informatica training in chennai[/url]

The recovery process finished after more than 30 hours:

Checking for bad blocks (read-only test):  99.94% done, 33:15:40 elapsed. (17407/0/0 errors)
Checking for bad blocks (read-only test): done                                                 
Warning: the backup superblock/group descriptors at block 229376 contain
    bad blocks.

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done 

mdadm: added /dev/sdb2

synchronize raid... done

copying image to disk... 
dd: writing to `/dev/md0': Input/output error
1646265+0 records in
1646264+0 records out
842887168 bytes (843 MB) copied, 875.909 s, 962 kB/s
cp: accessing `/mnt/md0/boot/boot.scr': Input/output error
./ line 359: /mnt/md0/etc/nas/service_startup/ssh: Input/output error
mdadm: stopped /dev/md0

all done! device should be debricked!

root@Microknoppix:/media/sda3/WD MyBook#

I connected the MyBook to one WS-C3560G-24PS switch (on port 23) in monitoring the port for a MAC address with "sh mac add int Gi0/23". The MAC address is written on the label (0090.a9b3.dab1) and I was expecting to see it after the DHCP negotiation…
The DHCP for that port vlan (VL10) is provided by the router (Cisco 3825 ISR G1) and I enabled the DHCP packets debug in order to see the requests.

Powered up the MyBook and after some initial Blue light, HDD cyclic activity, few Green light blinks and no debug output (on the router) at all, the light became Red and it was pretty much as before the recovery. I was waiting for the moment with no sigh of any disk activity… it took about 15 minutes.

At this point I pressed the reset button (for more than 4 seconds) and power cycled the device.
After few minutes stable Blue it started to produce regular Green blinks - every 6-7 seconds. Again - no DHCP requests, no MAC visible on the switch.

I'm not sure how to proceed further and I'm open for any ideas…

set the WD so that it never goes to sleep. Or have some program running on the WD so that it never sleeps - for example Transmission BT.

MyBookLive Duo 4T
FeaturesPacks, Twonky, ownCloud

I would love to say huge thank you for the tutorial. Everything worked out well and I successfully installed Twonky 8.2 on my WD 2TB with the latest firmware update.
All video formats are playing without any problem on 65" Samsung Curved LED. With the old Twonky 5.1 nothing was playing.

The only issue right now is that WD doesn't wake up when TV is trying to access Twonky Server. Before it was working fine with old Twonky 5.1. The workaround is to access from my phone or laptop 192.168.1.XXX to wake up WD.

Any help would be appreciated.


Hi Dan! Thank you for the nice script.

I have one question about the execution of the last part, where the image is supposed to be written…

When started the script for a very first time it was asking for CURL. However, with CURL in place it started to work pretty smooth up to the writing point:

root@Microknoppix:/media/sda3/WD MyBook# ./ /dev/sdb

********************** DISK           **********************

script will use the following disk: 

Model: ATA WDC WD20EARS-00M (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Flags
 3      15.7MB  528MB   513MB                primary
 1      528MB   2576MB  2048MB  ext3         primary  raid
 2      2576MB  4624MB  2048MB               primary  raid
 4      4624MB  2000GB  1996GB  ext4         primary

is this REALLY the disk you want? [y] y

********************** IMAGE          **********************

checking:     010507
searching:    ./*/*01*05*07*.img
searching:    ./*/*01*05*07*.deb

downloading:  ./firmware/rootfs_010507.deb
confirm [y]:  y
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  154M  100  154M    0     0  1805k      0  0:01:27  0:01:27 --:--:-- 1881k

will extract: ./firmware/rootfs_010507.deb
confirm [y]:  y
extracting:   ./firmware/rootfs_010507.img

********************** IMPLEMENTATION **********************

everything is now prepared!
device:       /dev/sdb
image_img:    ./firmware/rootfs_010507.img
destroy:      false

this is the point of no return, continue? [y] y

mdadm: /dev/sdb1 appears to contain an ext2fs file system
    size=1999808K  mtime=Sun Apr  3 07:43:04 2016
mdadm: size set to 1999808K
mdadm: creation continuing despite oddities due to --run
mdadm: array /dev/md0 started.
mke2fs 1.42.5 (29-Jul-2012)
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):  42.72% done, 5:24:00 elapsed. (4500/0/0 errors)

At this point it started to work extremely slow and I verified the processes:

root@Microknoppix:/home/knoppix# pstree -al 3584
sudo -s
      └─ ./ /dev/sdb
          └─mkfs.ext3 -c -b 4096 /dev/md0
              └─badblocks -b 4096 -X -s /dev/md0 499951

Do you think that such a slow execution, with so many errors, can finally produce a successful debrick ?


The firmware (OS) is on the disks, not on the hardware. You need to image the disk(s) with the firmware. There are many ways to do this, but the easiest is to use one of the DeBrick guides that are posted on this forum or on the WD forum. You will need to create and adjust the partition table before you re-image the disk. Look around on this forum for how to install new disks, you are not the first to do this.

MyBookLive Duo 4T
FeaturesPacks, Twonky, ownCloud


I'm looking at buying a second hand mybook duo live, with no HDDs included.
Link - www26 [dot] trademe [dot] co [dot] nz/computers/external-storage/external-hard-drives/auction-1058613988.htm

I have the following questions
1. Does this version of mybook have onboard firmware, or does it store the 'os' on the HDD?
2. If everything is on the HDD, is there a downloadable image for this version of the mybook, and how hard is it to get up and running?

I intend to use this with 2x 3TB WD Green HDDs.


You mean that you installed ubuntu12.04 on MBWE I white light? How ? Do you succeeded to have a full working system?

He means that the desktop PC he used had Ubuntu 12.04 installed as Operating System. It is more than impossible to install Ubuntu on MBWE.

Hi, I would like someone to help me on how can I install a battery in MBWE. I have read this post "Adding a Realtime Clock" but it is a bit hard for me to understand, since I don't have deep knowledge in electronics. Can someone write a step-by-step guide? I would appreciate it very much.

1. Remove the plastic strip that seals the two major pieces of plastic together. Use a screwdriver to pry it out if you're having troubles. (I lost this strip years ago, so it doesn't show up in any photos.)

2. Separate the two major pieces of plastic by depressing the tabs on the top and bottom of the drive near the front curve. Pull forward on the curved piece of plastic fairly strongly for it to come apart.

3. Four screws hold the hard drive in the case. Two of these are easy to access, the other two are right behind the plastic. If you remove some of the screws holding the metal frame into the plastic, I think you will be able to lift the frame up high enough to reach the other two screws.

4. Unplug the cable from the end of the hard drive and lift the hard drive out of the case.

[url=]informatica training in chennai[/url]

Re: Restore original MBWE by marlonbrandomarlonbrando, 31 Mar 2016 11:29

Hi! Anyone has those images? Both mirrors are down…

My Book World Edition White Light I.
I upgraded from version 7.2.7 to version twonky-mss2-8.2.1. and everything is functional. License accepted.

I followed the first post "Upgrading to a newer version."

page »
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License