Recent Forum Posts
From categories:
page »

Didn't work for me (I hadn't read edavid) - but it doesn't seem to matter, subjectively my mbwe is marginally faster despite no 4k alignment.
What I did:
My mbwe blue-ring single 1Tb stopped working (I now suspect the power supply). I assumed it was the disk, the nearest available replacement was Green Caviar WD10EZRX (4k Advanced format).
I got the old disk working on the DVD cables of my dual-boot PC, with a spare power supply.
I put the new EZRX on a usb3 caddy.
I ignored all the advice on copying and (double checking sdb/c!) just did:
dd if=/dev/sdb of=/dev/sdc ibs=512 obs=4096 conv=noerror,sync
after 4+ hours I got successful completion but fdisk -l reported alignment problems.
I ran gparted check on all partitions - this did nothing
I loaded the drive in the mbwe and it ran fine.
Took it out and tried to align the partitions with gparted - and bricked the drive for mbwe.
Am now repeating the dd copy.
For those wanting to just upgrade then it should work to do my straight disk to disk copy then follow above instructions to re-size partition 4 and rebuild the raid (if you want it)

Start by going here…emby setup
Select the version of Debian that the MBL is using. If it is not listed you will have to compile Emby Server from their source packages for your version of Debian and hardware.

Re: install emby in MBL 3tb by tdmiketdmike, 03 Feb 2016 17:23

Hi all!

First of all let me thank Dav-M for that wonderfull guide!

Just updated my WD My Book Live to Twonky 8.2 with no problems.

One thing tho: I have a problem that occured some time ago and wasn't fixed by updating to 8.2:
When the NAS goes to sleep the Twonky server doesn't come back after the WD wakes back up again. It just disappears from all of my devices.
The twonky server settings page shows me that the server runs and doesnt' give me a hint why I cannot find it in my network.

The server reappears when I restart it from the twonky settings page or when i uncheck and check the twonky server under the WD settings page.

Any idea whats causing this behavior and how to fix it?


Someone with enough knowledge can help me, installing Emby server on my WD mybook of 3tb?
   I know that processing is fast, but I only run Emby to catalog my movies. it's possible ?
   Someone help me ?

install emby in MBL 3tb by ioriflyiorifly, 27 Jan 2016 21:42

Thanks for sharing this information.

I had a tough time trying to unmount sda4 to do a fsck. What worked for me was to unmount everything from the root with: umount *

I was then able to fsck successfully.


Recently found this site after owning my WD MBWE 1TB white light for a good 6 to 7 years. Recently, I've been investigating how I could get more out of the drive and I have been following the instructions on the site.

Problem is that I thought I had installed bash and stupidly decided to change the root line in my /etc/passwd file to:


Since then, I have been unable to SSH as root, su and sudo are "not found", and so I'm stuck.

So, I've followed the recover scenarios from anpe008's howto on unbrick/reset possible scenarios from the website.
Did 1, 2 & 3, no change.
I can't do 5 or 6 because I can't ssh as root.
So, scenario 7 (Restore Default Configuration) is my next move.

Before I flatten the device completely (scenario 7,) I would like to have a second opinion from someone out there on whether there is anything else i should try before I proceed with the complete wipe (or abandon any hope of doing anything interesting with the device.)

Appreciate any comments :-)


Re: Rsync
tdmiketdmike 16 Jan 2016 16:23
in discussion Forum / My Book Live » Rsync

My guess is No. I am guessing here but there are two things you need to do. Change the repo and then create a new directory for the optware.
1) Change and update the /etc/sources/list for the correct architecture for the MBL.
2) Create a directory named "optware-ng" or "optware-ng.arm"

Let us know how it goes.

Re: Rsync by tdmiketdmike, 16 Jan 2016 16:23
Re: Rsync
SteveB2L8SteveB2L8 13 Jan 2016 09:24
in discussion Forum / My Book Live » Rsync

Thanks for the info ! If Optware (normal) is already installed do i need to remove it before installing Optware-ng ?

MyBook Live 2T + FeaturePacks - MyBook World Edition (white light) 1T + Registered FeaturePacks - QNAP TS259 Pro+ 2T QTS 4.2

Re: Rsync by SteveB2L8SteveB2L8, 13 Jan 2016 09:24

Hi Peterzh, it's a MBL (only 1 HD) or MBL Duo ? Can you provide the model n° ?

MyBook Live 2T + FeaturePacks - MyBook World Edition (white light) 1T + Registered FeaturePacks - QNAP TS259 Pro+ 2T QTS 4.2

Hi, good to know 3tb Red works fine ( I will try the same, did you used some of the guide from the forum?) but please can you clarify your statement:

Worked perfectly with Ubuntu 12.04 firmware 01.02.06 on a desktop with direct connection to the drive.

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


MyBook Live 2T + FeaturePacks - MyBook World Edition (white light) 1T + Registered FeaturePacks - QNAP TS259 Pro+ 2T QTS 4.2

Have you remove the drives and wired then into a desktop via sata? Another option is to use a USB to Sata adapter. Works great for me for tons of projects. Let me know what's up.


Exactly the same problem here.. did you find out what to do?

Best Wishes, Pär

Is 45 degrees realistic? I have a second mybook which has the original 3TB drive and it runs higher than that (55) when doing an rsync for an hour or two. I understand the warning cuts in at 68 degrees. Mostly this is low power, live "online" storage for my media centre. 99% of the time its streaming a single video. To me the advantage is I only need 1 mybook active for all my media but I'm currently running 2*3TB and 8TB gives me overhead for the next year or two. The heavy duty backup is done by an Intel based FreeNAS.

The disk is running in free air on the mybook mainboard currently at 44 degrees syncing with the FreeNAS after 2-3 days. What I'll probably do is make a simple enclosure/heatsink with some scrap 4mm aluminium diamond plate flooring I found in a dumpster if it runs a little hot for my liking. I'm not keen on an active solution. But I'm OK with 50 degrees or so during the sync process and a little less while streaming.

The disk is a low energy type and spins at 5900rpm designed for densely packed servers. It's also several generations ahead of the Green drive in the mybook (2011). But it has 6 platters so friction might be higher. The disk is impressively quiet. More so than the WD green to my ears but that might be related to old age.

I'll let you know because the cost and capacity is very tempting.

Please monitor the temps of the MBL with this new disk. The reason WD used the Caviar Green models was because the MBL enclosure doesn't dissipate heat very well. You might find that this new disk cannot handle the temps created inside the enclosure. Please monitor the temps and report back to us. If the temps get above 45C, you should consider placing a USB powered CPU fan under the MBL enclosure to drive air up through it. I had to do this with a MBL Duo that was in a confined space with limited circulation.

MyBookLive Duo 4T
FeaturesPacks, Twonky, ownCloud

Maybe this thread will help you: search this forum for -


I have a failing drive and am searching for a replacement on ebay, also wanting to increase the size of the array…please let us know if the procedure works.

If this is useful to anyone I managed to install this drive in an otherwise dead MBL using the second unbrick procedure using the 3TB image and then expanding it to 8TiB using the partition editor in Parted magic.

The only extra step was that before the resize the partition editor needed to do an automatic fix on the GPT. And the resize took about 15 minutes..

So I'm guessing if this works then *any* HDD works..

These disks are super cheap. They have issues with write performance but I use my MBL as an online media server so basically this is write once. The only issue is now the super slow ethernet performance 60Mbs tops :-( It's going to take a while to fill…

$ sudo modprobe md
$ sudo mknod /dev/md4 b 9 4
$ sudo apt-get install mdadm
$ sudo mdadm --assemble /dev/md4 /dev/sdb4
$ sudo mkdir /media/xyz
$ sudo mount /dev/md4 /media/xyz
$ sudo chmod -R 777 /media/xyz

This might not be enough. First thing with modern linux such as Ubuntu 14.xx which I have used you will not be able to check if md module is available. It is probably already build in the kernel so:
cat /proc/mdstat

should show at least something.
If you have attached the disk during boot, it should show assembled md devices (mine was /dev/md2)

Sadly it came out that even thought my device should be available on /dev/md2, it could not be mounted.

This article came with a lot of help:
(sadly I cannot paste a link so please use google and search for "mdadm raid doesn't mount" and check an article on unix.stackexchange)

Using e2fsck showed that my superblock was damaged and that was why I could not mount the drive.
Finally make2fs showed backuped superblock which I was able to bring back using e2fsck.

After that, mounting /dev/md2 was possible.


I am sorry for the belated response. Somehow or other, I did not get the notification of this posting.

Hopefully you have found the solution to your problem by now.

For those who may want to know this answer in the future, the answer is painfully simple.

  • You copy the data as mentioned before.
  • You follow the steps to "stitch" the array halves back together again.
  • You copy the data to the spare drive.
  • You run the e2fsck commands as noted above.
  • You copy the corrected data to a second spare drive.

At that point either - or both - of the spare drives should have the data you want.

What say ye?

Jim (JR)


The answer isn't all that complicated. We copy an excess of data and let the copying software clean up after us!


Because of the way the partition sizes are calculated, it's not always obvious exactly where one partition ends, and the next starts. If you are a real masochist, and wanted to take the time needed to calculate exact partition boundaries, go right ahead. However, we can "cheat" and let the software help us calculate all of this.

Based on what I could see looking at Gparted, DD, etc. I knew that the last system partition (#3) ended somewhere earlier than 811286 - exactly where, I don't know, but I know that 811286 is too large (i.e. it will include all of the system data, and a small fragment of partition 4.)

We don't care that a small part of partition 4 is included, because when we copy the fourth partition, we're going to copy it by name - for example /dev/sdb4 - and when we copy by name, the software knows exactly where the fourth partition starts. When it copies the data back into partition #4, it will copy over the small portion of data that is already there. Since it is, (should be!), exactly the same, everything is just fine.

By using this "cheat", we insure that we do not accidentally omit any important data from the last system partition by mistake.

What say ye?

Jim (JR)

Hi Jim — Great post. I know it's some years later, and I'm not using the blue ring, but what you've written is still gold. The only part I don't understand is how you came up with the value of count=8112826 when copying the "system area" of your good drive. I'm sure that the size of my system area is different and I don't want to screw this up. Regards, Aardevark

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