Recent Forum Posts
From categories:
page 1123...next »

Hello, I too have the same problem, did you get to fix it or find some method?

thank you very much

{
root@MyBookWorld:~# iptables -L
iptables v1.4.8: can't initialize iptables table ‘filter’: Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
}

Hi,
Sorry for my English but is not my native language…
So i want debrick the HDD of the MyBook LIve 2TB…
I formatted the HDD with NTFS Filesystem because i used it on my PC Desktop with Win 7 but now i really want to use it again like original MyBook Live.
I followed that guide but i don't know how to reset the right partitions on it.
Can anyone tell me what to do now?
i hope someone can help me.
Thank You
Giuseppe

Hello…did you manage to recover the files? None of the recovery software seems to detect the names of the folder and the files. Thanks

Hello,

I have a WD world book 1 TB White Light and I accidentaly deleted a share. I have a lot of data I require in that share. I have now taken the disk out of the casing and connected it to my Laptop using a SATA connector. I used a recovery software (EaseUS) which detected all the files from the deleted share but the folder names and file names are gone. It gets all the files sorted in order of type.

Is there anyway I can get the folder names back and the file names? Is there any other software I can use? Any help would be much appreciated.

Best regards
Jacka

Deleted Folder Share by JackK7000JackK7000, 11 Dec 2014 22:36

Okay, the instructions as provided by phil_post do not work, or are incomplete at best. His information is correct up until step 4, which is where I'll pick up.

(4) Write "bubble.sh" script:

While still logged on via Putty, at the ~# command, type your installation directory path. phil_post was using "cd /DataVolume/shares/Public/Software/BubbleServer" I personally used "cd /DataVolume/shares/Public/BubbleServer" and from this point forward, I will use this format; if yours is different, be sure to adjust accordingly when you see this directory referenced. Yours can be whatever. It is where ever you extracted the BubbleUPnPServer-distrib.zip file, and it seems that it should be on one of the original shares that came on the mybooklive.

~# cd /DataVolume/shares/Public/BubbleServer

Make sure that the launch.sh script is marked executable.

~# chmod +x launch.sh

Create the bubble.sh script.

~# vim bubble.sh

This will open vim and create a new file named bubble.sh While in vim remember that pressing [a] allows you to edit the text, [ESC] exits edit mode, and [:wq] exits vim saving changes. Paste exactly the following to the top of the new file:

#! /bin/sh
# /etc/init.d/bubble
#

cd /DataVolume/shares/Public/BubbleServer
java -jar BubbleUPnPServerLauncher.jar &

Although you may need to change "cd /DataVolume/shares/Public/BubbleServer" to reflect your chosen installation directory, as mentioned before. Hit [ESC] and then type [:wq]

Mark your newly created bubble.sh as executable.

~# chmod +x bubble.sh

Exit from your installation directory to the root prompt.

~# cd

It should now look like this again:
MyBookLive:~#

(5) Install BubbleUPnP Server

MyBookLive:~# DataVolume/shares/Public/BubbleServer/bubble.sh

This will now install your BubbleUPnP Server. After installation is complete, you can access the server's interface from your browser with the IP address for your mybooklive at port 58050, eg. 10.0.0.111:58050 or whatever. At the end of the installation, I also saw that the interface for the Twonky server is on port 9000. If you weren't aware of that either, that's how you access it.

Okay, seems like I got as far as cunyalen. I am also having error messages.

With sh launch.sh, it says:
The stack size specified is too small, Specify at least 1024k
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

With nohup sh launch.sh &, it says:
[1]+ Exit 1 nohup sh launch.sh
MyBookLive:/DataVolume/shares/Public/BubbleServer# chmod +x launch.sh
MyBookLive:/DataVolume/shares/Public/BubbleServer# nohup sh launch.sh &
[1] 10383
MyBookLive:/DataVolume/shares/Public/BubbleServer# nohup: ignoring input and appending output to ‘nohup.out’

Which doesn't seem to do anything at all. I don't know what to do now at all.

I think I may have figured it out.

At the prompt MyBookLive:~# you type "vim /etc/apt/sources.list" to open the sources list with the VIM text editor. Then you add to the list:

deb ftp://ftp.deb-multimedia.org wheezy main non-free
deb ftp://ftp.deb-multimedia.org wheezy-backports main

I think. I'll see what happens from this point and come back if I have more questions. BTW, what you were trying to do, eg. use Chromecast for non-native files via BubbleUPnP from a MyBookLive NAS is exactly what I'm trying to do. I think it will be a sweet setup if I can figure all this out. Thanks for providing this info at least, if nothing else.

Sorry, I'm really new to this kind of stuff. My question is, what exactly did you do after you signed in via Putty?

I have ssh enabled, signed into my MBL via Putty as root with password welc0me, then it comes up with a command prompt looking thing:

MyBookLive:~#

What did you mean when you said:

I added 2 lines:
ftp address of deb-multipedia org/ wheezy main non-free & wheezy-backports main

MyBookLive:~# vim /etc/apt/sources.list

What did you type, where, and in what order?

Re: download problem by kevkukevku, 05 Dec 2014 18:12

there is a problem when downloading rar files, the servers give this error:
The file "mybook_we_rescue.part01.rar" has been blocked. The file is larger than the configured file size limit.
does anyone have these files?

download problem by loleanteloleante, 05 Dec 2014 16:30

ssh will not allow passwordless logins (using key pairs) unless the users home directory permissions conform to a specific criteria. But all users share a home directory which means that the criteria cannot be satisfied. I have tried adding a user in the usual Linux manner (adduser) but it gets deleted the next time the web interface is used (as you would expect I suppose). What I need to do is change the new user script that is run when adding a user in the web interface. Does anyone know where that script is so that I may edit it?

SSH access without password by willymacoywillymacoy, 04 Dec 2014 08:59

hi all.

every where i look the link for the WD_MYBOOK_WE_500GB_IMA.7z seems to be dead.

I was given a WD bluering dual with one disk in.. but i think someone wiped all the data on it first.. so no partitions ..
would like to get this going, as already have a white light, but pref the drive mirror for pic storage.

the only thing i dont have is the OS to get this booted.
can any one help ?

I just did an apt-get update and it was a pain in the ass to get it working properly. Unless you used dpkg -i —force-overwrite or forced apt-get to dpkg —force-overwrite you didn't install anything. Downloading and finding the GPG Keys was painful itself just to get apt-update to work correctly.

I managed to kill apache while updating, but ssh still worked for me. I also made sure to install openbsd-inetd and telnetd before I rebooted incase I killed ssh. Upgrading apache2 managed to erase /etc/apache2/sites-available/wdnas and wdnas-ssl. Luckily I have 3 of these and just restored from a backup. had to install php5-curl manually. I also had to add ~E_STRICT to the Cake bootstrap.php to get the website loading with the newer php5.

Started having this problem after things where fine for about a year. I run 3 of these in a lvm mdadm raid with a wndr3800 running openwrt as the server.
MBL uses a combination of lenny and squeeze debian. lenny was discontinued in 2012. All of a sudden the 3rd drive would just drop from the array. All these splice errors and smbd taking up the cpu and not responding when issuing a kill command. Upgraded to squeeze and samba 3.6.6. No problems so far. Was annoying due to GPG keys, circular dependencies and wdnas packages. Luckily I didn't brick the thing.

3.2 kernel and Wheezy would be nice.

You may try www.easycron.com, works quite well.

Re: New cronjob not working. by HamlinHamlin, 24 Nov 2014 16:39
iscsi support
yldourightyldouright 22 Nov 2014 16:26
in discussion Forum / My Book Live » iscsi support

I just acquired a WD MyBook Live Duo and have discovered that I can't see it with my OS (server 2008 R2). I tried enabling my Computer Browser, NETbios over TCP/IP v4 and SSD Discovery services only to discover I couldn't find it or point to it with iscsi like you can with any other SAN device. None of the other WD software seems to find it either and I've installed the SED driver. My next step is to try putty to SSH but I have no experience with this. Can someone point me to a guide where I can use Server 2008 R2 to talk to this device? Do all the MyBook Live devices use the 192.168.1.215 IP address?

iscsi support by yldourightyldouright, 22 Nov 2014 16:26

I think you're confusing two people (and two images). Matt's one was 9.7 GB, whereas Teinturman is the one who made available an image of 650 MB, for which he charges 10 euros.
Anyway, unless you can't spare the money or you are a hobbyist who likes the challenge to turn an underdevloped system into something wonderful, DON't BOTHER. This NAS is one of the most unreliable you will ever find. It's slow, hot, faulty firmware etcetera. Buy a synology Disk Station, or any other brand NAS, if you want data to be safe and like devoting your time to getting things done.
The WD MBWE is a waste of space and time. I've tried for three years to optimize it, and didn't get anywhere. It was a nice toy to get to know the idea behind a NAS, but I'm now going to use some mature product.

Sandokan

I have symptoms where the machine is on but loses LAN connection after a few days, except it doesn't even respond to ping. Perhaps the ethernet jack shuts down to save power? Here are two tricks I have used to maintain uptime:

Running WD Anywhere Backup.
Mounting the device through sshfs from another linux box.

Oh and for the record, the power supply for my oldest MyBookWorld white light is dying (under-volt). The supply was causing the MBW to reboot while in heavy use.

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