Software Problems
MBWE is Online but not Visible Through Windows Networking
Samba is not currently running or has loaded using the incorrect config. Run the following command as su to manually start it.
/usr/local/samba/sbin/smbd -D -s=/var/oxsemi/smb.conf
[HOW TO] recover/unbrick/reset the WD Mybook (While Light) - Possible scenarios
* I) Different reset types/levels and their impact
* II) Possible scenario table to indentify what reset types you can use in your current situation
* III) Extra info: admin password reset, Useful commands in telnet
http://mybookworld.wikidot.com/forum/t-175889/how-to-recover-unbrick-reset-the-wd-mybook-while-light-possible-scenarios
Hardware Problems
Read error in shares, read only files, lost permissions (in shares - md4)
The following commands will reformat the drive and restore the shared directories, but not their contents. All data will be lost.
- backup the shares directory structure,
- remove all files
cd /shares
rm -r internal/*/*
tar cpsf /root/internal.tar internal
- reformat the drive, don't reserve free block
umount /shares/internal
mkfs.ext3 -m 0 /dev/md4
mount /shares/internal
- restore the shared directories
- cd /shares
tar xf /root/internal.tar
rm /root/internal.tar
Threads about theses problems :
http://mybookworld.wikidot.com/forum/t-54162/read-only-ext3-errors
http://mybookworld.wikidot.com/forum/t-50207/cannot-delete-files-read-only-dev-md4-on-mybook-we-i-1tb
http://mybookworld.wikidot.com/forum/t-52374/loosing-permissions-overnight
http://mybookworld.wikidot.com/forum/t-55527/large-file-copy-problem-solved
+++MyBook disconnects during data transfer
I would like to share my experiences with the My Book WorldEdition with you, this might save you some time.
Shortly after the first usage I was not able anymore to safe larger data volume. The drive would disconnect after a short time and could not be addresses anymore either thru Windows nor Linux. It required a reset (restart unit with power up).
I noticed the website “mybookworld.wikidot.com” and figured my Linux knowledge was sufficient to try to figure out what happened.
I followed M. Hinner’s advise to connect the drive thru SSH like this:
Connect with Shared Storage Manager (Web interface)
Add user under tab “File Sharing” (write down username and password)
Set CIS sharing to none for all users (tab “File Sharing”)
Use network settings and set network address to automatic (very important, does not work with fixed IP)
Check IP address of your MyBook in “System Summary” and write down.
Follow M. Hinner’s instruction
http://martin.hinner.info/mybook/sshaccess.php
Use LINUX system, I used UBUNTU, use terminal window.
Enter
ssh username@IP MyBook (very important, username in CAPITAL letters)
Your are requested to enter password, use the one you wrote down while adding new user
Enter
su
Enter
umount /dev/md4
Check partition with e2fsck –c /dev/md4
If the system reports error then reformat with mkfs.ext3 -m 0 /dev/md4
If not, looks it is more serious and out of my competence.
Once you finished the operations above, power down your MyBook, restart and log in thru Shared Storage Manager
Thank you to all the contributors of the web site, I would not have been able to recover MyBook without them.
Light will not turn on
If your MyBook World Edition begins turning on when it is plugged in but never finishes booting up (ie: light does not come on) then you may want to try unplugging it from the ethernet cable and try again. Be sure to be patient with it, as it does take anywhere from 10 seconds to a minute to turn on the light sometimes.
"The drive is currently busy" Error
Many people have experienced problems with upgrading the firmware where they receive message stating that the firmware can't currently be updated because the drive is currently busy. Here are some excerpts of their problems and/or solutions.
Firmware 01.01.18 (The drive is currently busy)
I purchased a WD MyBook World Edition 500 with 01.01.18 firmware. I added the admin password and created an account called bill. I then went to the firmware upgrade page. I get
"Applying new firmware
The drive is currently busy. Please stop using all shares and try again."
Has anyone else seen this error on new units as of 9 /20/2007.
wd case number 092007-524-5152
got that error message too
Answer: Today I bought one with 01.01.18 Firmware and got that error message too. The first steps necessary can be quite tricky so here's how I did it.. First, find a windows station on your lan and instal the software provided on the CD included with the unit and register your machine. This will change the firmware somehow. You should have your admin account set up properly by doing this step. Next, restart your mybook. Then you should be able to upgrade the firmware. BUT you still won't be able logging in via ssh! The admin account won't work. You must still enter the web interface and on the tab "File Sharing -> User Management" create a new account. It will be that one you use in logging in. After doing this there shouldn't be problem spawning the shell…
Issue 10/21/07: I cannot get around this issue with 01.01.18
I have tried doing everything you said here - I installed MioNet, I registered the machine, and I've restarted the mybook several times. No matter whether I try directly accessing Hinner's firmware or just click "Upgrade the System Firmware" from the web gui, I still get the "currently busy" error. I also tried making WDAnywhere access inactive in case that was the issue. It is clear that I don't have an sshd running on the mybook.
another answer
Another answer: I bought one today with the same fw version. However, as I do not have access to a windows computer, I solved the problem by connecting to the samba share using konqueror (i.e. KDE file browser) and after closing that window I was able to do the firmware upgrade. Adding users can be done using the web interface. There is no need for windows to succesfully hack into your WD MyBook :-)
yet another answer
And yet another answer: By going to "General Settings -> WD Anywhere Access settings" and disabling the NAS I got rid of the nasty message and I could install SSH as stated. No need to use Win*.
no problems here
Another User: I just bought a 500Mb MBWE II with the 1.01.18 Firmware installed. Out of the box, I created a new user and ran the firmware update as per http://martin.hinner.info/mybook/sshaccess.php. It was successful, and I could ssh in after 2 minutes. I didn't create any shares or do anything else.
this worked for me
I went to Configure Network on the general settings tab, Configure Network Settings, on the wizard I left it on automatic and clicked finish or done or whatever and when I tried again it worked.
Worked for me too
Mine was set to a static IP. Changing to automatic disconnected all the PCs that had mappings to the MBWE and the firmware upgrade launched when I tried it again. I suppose changing the static IP address to a new static address would have worked as well.
I am running Firmware 02.00.15 and NO matter what I do when trying to install the Firmware for SSH access I get an error of "Firmware failed to download - try later ". Ihave rebooted several times, stopped NAS and still won't work. PLEASE HELP. Western digital said I have to call in for support which is a pay call. Its a bunch of crap. I have tried both sources for the firmware SSH upgrade with no success. Now I have files on there (3,500+) that I can't edit or delete, just view.
I can confirm the same behavior in 2.00.18, but I haven't lost files yet.
