Recent Forum Posts
From categories:
page »

I have problem with my dashboard. The problem is because i don´t know for tht reason the firmware was upgraded by dashboard automatical, but the now there a lot of problems with dashboard. I can access by dashboard and ssh but i can not update the firmware by dashboard in automatic or manual mode is imposible.
How can i restore the firmware original?
How can i update the unit firmware by ssh?

Hi i have recently replaced the original drive with another one.
now i can access the management web page, ping the ip, access with ssh, but i cant browse it..any idea about it?

Hey Ronster. I have the same problem and I found on another post that the partitions that have the data on them are not ext3 or 4. they are XFS. If you launch terminal and enter "mount -t xfs /dev/md4 /media/xyz" it will be able to read the files. I know your post it 4 years old so maybe you found this a while ago but just thought I'd post my solution so it may be used by anyone else having this issue. Happy data recovery everyone!

First thanks for the how-to, it seems pretty straight forward and easy to follow.
I have the previous model, to be more exact the WD My Book Live Personal Cloud Storage 2 TB Network (Item model number WDBACG0020HCH-EESN).
Would it work the same way?
Should I use a different configuration?

Thanks in advance

Hello guys, I got this device with two dead 500GB disks.
I disassembled the entire device for check some power error and there was one capacitor wrong, so I resolder it.
I tried to create recovery from this web on two 1TB WD disks.
After plug it to mainboard and plug power is light only one diode on LED/BUTTON BOARD.
Please is there any instruction for restore system on new disks??
And what will be doing, if is system restored badly??
Im really despred, because it is really good piece of device and it will be really shame throw it away :(

I want to sync part of my storage with google drive.
I found about grive.
but couldnt find anyone with experience with installing that on a MBL.

do you think it'd be safe, just following the instructions on the lbreda page?



really appreciate if somebody can compile this module and publish it on the mbwe-bluering feed, only is included in the default asterisk18


hy glx i had followed your indstructions, and now i can see my new 1TB drive.
after that i have successfully updated the standard firmare but now i see wd anywhere access is "not registered"…have you got same problem?
(ah i didn't recover the old mac address)


Re: replace drive with Clonezilla by 0zzy0zzy, 13 Apr 2014 12:55


I have been running a White Light MBWE 2TB edition in RAID 1 (so for clarity, 1TB RAID capacity) for some time and am very happy with it.

Reading around the forum it occurred to me that the one data security risk I didn't have covered was failure of the housing itself. I may be wrong, but I got the feeling I would have trouble putting the HDDs in another (non-MBWE) housing and being able to use the drives straight off.

To cover this I bought a second identical MBWE housing on ebay. The theory is if my current MBWE housing fails, I can just remove the HDDs as a pair from the faulty one, slot them in the second housing, and start it up. I've not needed to test that theory yet. However…

I'd now quite like to commission the second housing as another NAS with larger, maybe 4TB, drives. If I can do this I'll probably move all the data onto the larger NAS and then keep the original as a spare housing, as per the plan above. I'm not sure this is possible but here goes. The plan is as below:
[To make this easier I'll refer to the four HDDs as 1A, 1B (these are the 1TB drives in the current NAS), and 4A and 4B (these are 2 new 4TB drives I need to buy)]
1. purchase 2 off matching 4TB drives (4A and 4B).
2. remove 1A from current NAS and insert in new NAS with 4B.
3. boot new NAS, login to it, and rebuild RAID as per WD instructions using NAS software using 1A as data source.
4. remove 1A from new NAS and replace in old NAS.
5. boot old NAS and confirm all ok, rebuild RAID if required using 1B as data source.
6. insert 4A in new NAS and boot, login to it and rebuild RAID as per WD instructions using NAS software using 4B as data source.
7. erase all data on new NAS and format drives from scratch, hoping this gives a 4TB capacity.

Once I'm past step 5 and I'm happy the data is OK, I can fiddle with the second NAS, and the drives in it, all I want.

I figure step 6 may not be required. The reason for rebuilding the RAID in the new NAS in step 3 is basically just to get the OS onto the drive 4B. Once it is there I may be able to format the drives without rebuilding the RAID (again) on the new NAS.

If this isn't possible with larger drives, presumably it would work with 1TB drives instead of 4TB to give a second NAS, but I would like to increase capacity.

I don't know if this has been tried as a process, but I would like to hear from anyone who has tried this, if it worked or not.

I have two spare HDDs that I can use to test the above, but they are hardly matching, a 1TB and an 80GB. I could use these to test up to step 3 at least yo avoid possibly wasting the cost of 2 x 4TB drives.



2nd MBWE White Light by KenDicksonKenDickson, 11 Apr 2014 14:06

Hi all,
a critical security alert has been raised regarding openssl :

A security Vulnerability has been announced that affects specific versions of OpenSSL.
OpenSSL versions 1.0.1 through 1.0.1f contain a flaw in their implementation of heartbeat functionality.

• OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
• OpenSSL 1.0.1g is NOT vulnerable
• OpenSSL 1.0.0 branch is NOT vulnerable
• OpenSSL 0.9.8 branch is NOT vulnerable

In order to check your openssl version you can connect via putty ( ssh) to the mybook, then type the following command :

openssl version

i have checked the following mybooks :

Mybook live :

openssl version
OpenSSL 0.9.8g 19 Oct 2007 (Library: OpenSSL 0.9.8m 25 Feb 2010)

Mybook Whitelight :
~ # openssl version
OpenSSL 0.9.7e 25 Oct 2004

It looks like the mybooks, may have an older version of openssl, which is not affected by this security issue, but please,
check on your own devices your openssl version.

HeartBleed Security issue by TeinturManTeinturMan, 11 Apr 2014 07:26

I experience similar issue. Start with a My Book Blue Rings wo hard drive, performed successfull recovery on a blank Western Digital 320GB drive to version 1.01.18. Tested for one day accessing PUBLIC share without problem. Created 2 additional users and their share. Then went for update: set security to none for ALL shares and ALL users and disable WD Anywhere Access as stated in the notice before frimware update. After 30' firmware update completed. Now 2.00.18. Configured security again for all shares and users. But left WD Anywhere Access in Unregisterd state. (I want to use the MBWE blue rings (singe drive) only on home network and do not need access from the internet). The web interface works fine. As a next step I will delete all additional users and their shares, recreate them and test. DO I HAVE TO REGISTER THE MBWE to enable access? I realize that by now there are A LOT of MBWE using the same MAC address as the one from which the rescue images were taken, and that this COULD impact registration, which re-registration might be required after Firmware update. All advices are welcome!

I have tested out my setup as described above and the USB Serial port worked on first try, without anything special. I used screen as a shell (screen /dev/ttyUSB0 9600). My dongle's VID:PID is 067b:2303.

I hope this information is helpful for others in the same situation.

Ok, here are some updated on this issue:

I managed to compile the modules the OP talks about by using the first variant in this tutorial: To compile just these modules without doing "make modules" you'll need to do these steps as well:
1. make menuconfig -> Navigate to Drivers -> USB -> USB Serial [M] and enable FTDI [M] and Prolific 2303 [M]
2. from WD-MyBookWorld-v1.02.14-GPL/kernel/kernel-source/kernel-0.4.6 run the following commands:

make drivers/usb/serial/usbserial.ko
make drivers/usb/serial/pl2303.ko
make drivers/usb/serial/ftdi_sio.ko

Alternatively you can download the compiled drivers from here:

3. Copy your drivers to the mybook and follow the instructions in the first post here.

4. To create /dev/ttyUSB0, you'll need to run this command on the MyBook:

mknod /dev/ttyUSB0 c 188 0

I haven't actually tested the module yet, but I will post a feedback on that soon.

I hope you noticed the sticky called "Files" in the forum section called "My Book World Edition (blue rings)".
mybook_we_rescue.rar has all the files needed. It has rescue.img, SDA_PTAB, SDA1_IMA.BZ2, SDA2_IMA.BZ2, SDA3_IMA.BZ2. while
DOESN'T HAVE SDA3_IMA.BZ2 but two .tar.gz files instead. With the archives containing the .tar.gz I failed to rebuild my WD5000G032 and with mybook_we_rescue.rar and the Knoppix live CD I succeeded in a few hours. Knowing how to do it now, next time would take less than 30' to success. If you are still waiting for a working archive I hope mybook_we_rescue.rar works for you as well.

Re: replace drive with Clonezilla by glxglx, 08 Apr 2014 21:53

This forum is not as alive as it used to be, so sorry fo the delay.

Maybe you could try replacing


so the command becomes: sudo mount -t xfs -o ro,norecovery /dev/sdd4 /mnt/sdd4

This has helped me n the past with the same error. YMMV.


Re: Can't mount HDD by sandokanfirstsandokanfirst, 08 Apr 2014 01:21

I bought MBWL few years ago and never had problems with it. Optware installed with just Transmission, uShare and no-ip as extra.
When i move some files (usually movies) either wireless, LAN, or via the copy manager to USB, the transfer just stops. It sinks to 0/kb and makes windows hang for a minute, or i get "copy terminated" message on the web UI.
Those files were used to be not faulty and i'm sure of it.
I tried to copy on a pendrive a movie i already transfered some moths ago. I tried to remove all mods and forcing a firmware update but nothing.
Installed a newer version of samba and still having this issue I really have no idea what it might be! Also system never gets hot and disk is in "good" status.

Unable to transfer big-ish files by JowahJowah, 07 Apr 2014 02:57

I found the error …

First: In the table in "storage_disk_manage.php" the raw 'description' had to change to the wide 180px (was 260).
Second: The file en.xml (for me de.xml) must not changed … Changing the file de.xml won't work :-(

Now it works :-)

Looks like you might have not pasted the new info correctly and are missing a > or a </> end…check your work. I have this working for MBWE and if you need I can share my 3 files that work.

Something is wrong … but I don't know what ???

Fatal error: Cannot create references to/from string offsets nor overloaded objects in /proto/SxM_webui/admin/inc/wixXML.class on line 67

It seems that those 2 files are not to be found. any help?

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