Recovering Original FW - Tested

Re: Recovering Original FW - Tested

Mon, 22 Jun 2009 14:37:44 +0000

For some reason, the MAC address is stored in the boot sector. The MBWE2 uses the mac that's in the boot sector, and doesn't read it from the hardware… You can create a little script that fixes it…

 # I also figured out (by having two rescued MBWE2's on the same network) that the MAC address that the # MBWE2 gives out is stored in the boot loader, and NOT taken from the actual Network Adapter. To fix # This, I set up a script that runs at every boot that sets the MAC address to whatever is on the # sticker on the back of the MBWE2. vi /root/macaddr.sh Once it's up, hit the letter "i" for insert and enter in the following 3 lines ip link set eth0 down ifconfig eth0 hw ether XX:XX:XX:XX:XX:XX ip link set eth0 up Then hit Escape, then type in :wq (to write the file and quit out of vi) chmod 755 /root/macaddr.sh ln -s /root/macaddr.sh /etc/init.d/S11macaddr.sh

Hope this helps.

-ET

Re: Recovering Original FW - Tested

Fri, 19 Jun 2009 13:35:48 +0000

Can I Apply this procedure to my My Book World Edition (white light) 1TB for reset HD to factory default without any hack inside?

Re: Recovering Original FW - Tested

Tue, 09 Jun 2009 17:34:22 +0000

Hello.

any one tryed this on a mbwe 2tb single drive, just wanna know if it works?

Re: Recovering Original FW - Tested

Sun, 31 May 2009 16:58:41 +0000

I changed this article, cleanup things, hopefully it will work for everybody (at least it work for me:)

Re: Recovering Original FW - Tested

Wed, 04 Mar 2009 05:27:40 +0000

for some reason, the link to the rescue files arent working. ive tried several times and keep getting no response.

root@ubuntu:~# wget http://szabados.sk/mybook_we_rescue.zip
04:49:31 http://szabados.sk/mybook_we_rescue.zip
=> ‘mybook_we_rescue.zip’
Resolving szabados.sk… 81.89.49.190
Connecting to szabados.sk|81.89.49.190|:80… connected.
HTTP request sent, awaiting response… 404 Not Found
04:49:32 ERROR 404: Not Found.

so i found a copy on the internet, not sure if it will work tho but it does download. but when i try to unzip, i get…

root@ubuntu:~# unzip mybook_we_rescue.zip.1
Archive: mybook_we_rescue.zip.1
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of mybook_we_rescue.zip.1 or
mybook_we_rescue.zip.1.zip, and cannot find mybook_we_rescue.zip.1.ZIP, period.

wat am i doing wrong?? please someone, i really need help in rescuing my mbwe 1tb nas.

thanx.

Re: Recovering Original FW - Tested

Sun, 01 Feb 2009 14:10:01 +0000

hi ,

I'm a newbie to linux, but followed the procedure to recover my 1TB version using the link http://mybookworld.wikidot.com/rescue-procedure . I was able to get by book started, also installed ssh, webserver, active book using the links in this site. When started copying files ,MBWE started complaining that i do not have enough space to copy. I'm sure i did not copy at least 10GB of files. can some one tell me where to check the disk space and how to recover my full disk space. Any help is highly appreciated. Thank you.

Re: Recovering Original FW - Tested

Sun, 01 Feb 2009 10:32:04 +0000

It the software you recommended able to restrore libgcc_s.so.1 and libgcc_s.so back to the orginal directory?

Re: Recovering Original FW - Tested

Fri, 30 Jan 2009 03:33:09 +0000

Okay, I followed everything in this procedure till the end, and everything looks fine. However, when I mounted sdf1 (my drive is f) and when I looked at the scripts (.sh) inside /etc/init.d/, I noticed many of these shell scripts contain weird and unreadable sybmols. I have no idea why this is happening.. Is this normal?

When I plugged my WD back to the case, it is still not booting up…

Please help!!

TIA

Re: Recovering Original FW - Tested

Thu, 29 Jan 2009 04:37:29 +0000

First, thank you all for the rescue procedure. But I ran into a problem even at step 3! It says "dd: opening ‘/dev/sdf’: No medium found" It seems that my Linux box cannot access the HD at all… I used a SATA-to-USB adapter, and I did see sdf being added to /dev/ right after I plugged in the usb cable. Anyone has idea to fix this???

TIA!!

NVM… stpuid me… my power cable is not fully connected… thats' why…

Re: I think I am in big trouble

Sat, 17 Jan 2009 00:27:28 +0000

Hi,

Yes, I know I have wiped out the first 3G data in my hard drive. The problem is that is the only thing I know. When I try to get the rest of my data back, I don't know how to set up the recovering software. The software ask my to set up the "Starting Sector", "Cluster Size", "Start Cluster" and I have no idea what does that means. I know I must to calculate it, I know if I want to save the rest of my data, I must tell the recovery to skip the first 3G space I have wiped out. Since I don't know "how many sector = 3G??", and how many cluster size I need to select, which start cluster I need to select in order to get the best recovery, I do need to ask for help here because I know you guys are all better then me.

I am not computer guy, I am just a filmmaker which make video and film for living, I know I may sound like a idiot and I am sorry for my stupidity of my lacking knowledge of computer. Please help me out here and let me know more information about how to save my data and also save my job.

thank you so much

Re: I think I am in big trouble

Fri, 16 Jan 2009 23:05:12 +0000

The clue lies in the count=3000, you've essentially wiped the first 3GB of you HDD.
If you read the guide and the title of the step you've just done it becomes quite clear:

3. Zero fill the first 3 GiB of space on disk

Re: I think I am in big trouble

Fri, 16 Jan 2009 21:46:05 +0000

Hi,

I do think there is one part you guys can help me here. I just got 2 data recovery software but I don't really know how many data I have already erase from my hard drive. Both of the data recovery software asking me where I want to start search lost data (starting sector). Since I use this command "dd if=/dev/zero of=/dev/sda bs=1M count=3000" to wipe out first few sections of my hard drive, I assumed that there are a section of my hard drive full of "0", the question is, I don't know how big……

In the data recovering software, I need to start searching and getting my data back from non-zero area, so according to the command bs=1M count=3000, is that means I have already put 3000MB "0" in the first part of my hard drive?? If this is truth, how should I select the start sector from my hard drive to save my lost data? According to my data recovery software, it says that they need me to put the start sector, but they have already know the cluster size is 4.00kb, and the volume size is 931GB (1T), the hard drive format is NTFS

So, would you please let me know what starting sector is good for me to try to get my data back?? I have tried to put start sector = 0, but recovery software didn't find anything. Somebody please help me, if I can not get any data back before Jan. 25th, I will lose my job

thank you so much

Re: I think I am in big trouble

Thu, 15 Jan 2009 18:15:17 +0000

Hello,
You have erased some part of the disk!
your only chance (small?) is to use a Data recovery tool on your Windows Desktop.
try searching google with data recovery tool , try to recover the files
you may not recover all the files, maybe nothing….

sorry, can't help more.

I think I am in big trouble

Thu, 15 Jan 2009 10:18:14 +0000

Hi,

During the procedure, I accidentally forgot to change the device name, so I put "dd if=/dev/zero of=/dev/sda bs=1M count=3000" which I am supposed to change /dev/sda to /dev/sdi, I know I am in big trouble, after reboot my computer, on of my hard drive in my pc gone. I know I must wipe out this hard drive with this command. This hard drive is not my operation system hard drive, but it store a lot of important files from my work. Is there any way to get this hard drive back or save data from this hard drive?

Please help me. One more thing I really want to say is, from the first day I get this WD Mybook World editing, my nightmare never stopped. I am not computer major or computer guy, my job is film production. I don't know why I waste my money buy this piece of shit and suffer for this very very bad hard drive and couldn't have a good sleep. Right now I just want to save the hard drive I accidentally erase by "dd if=/dev/zero of=/dev/sda bs=1M count=3000" command and put my WD Mybook World Edition 1T to the trash can.

please help me, if I can not bring my hard drive back (not the WD Mybook World Edition one, the other hard drive in my pc which I accidentally use "dd if=/dev/zero of=/dev/sda bs=1M count=3000" command to screw up), I will very possibly lose my job.

please help,

thank you so much

Re: Recovering Original FW - Tested

Thu, 11 Dec 2008 03:41:20 +0000

Recently I have been trying to fix my My Book World Edition II as it seems to have failed to start up. Since then I have tried using the rescue procedure while trying to avoid/skip formatting the 4th partition (/dev/sdb4). Now getting the My Book to boot up again was a success but it seems that the 4th partition is now unallocated space or empty, also MioNet or what have you is now showing a 3gig partition. Is there anyway to amend what I have done here or do I simply have to do the rescue procedure while including mkfs.ext3 -m 0 /dev/sda4 rather than skipping it.

Re: Recovering Original FW - Tested

Wed, 03 Dec 2008 08:59:56 +0000

fixed it ….. i had my drive mounted on /dev/sdb so assumed at step 12 you should change fstab to sdb4 …. i tried sda1 as in the instructions and it now works fine….. good instructions. I bought the empty world book enclosure off ebay for peanuts and had a spare 500GB drive …. and i now have a fully working worldbook …. cool

Re: Recovering Original FW - Tested

Tue, 02 Dec 2008 18:58:00 +0000

i dont think that the sdb4 drive is mounting …. the space that is allocated to to the shared folder appears to be similar to the space free on sdb1 …. how can i check and work out what is wrong?

Re: Recovering Original FW - Tested

Tue, 02 Dec 2008 14:13:41 +0000

i have gone through all this procedure twice and am having the same problem all stages work fine, it boots up is recognised by the network. I access the mybook internet admin tool and go through the configuration wizard, on the main page where it gives the details of the mybook under the storage heading there is nothing …. it lets me create a new share and i can mount this as a drive under windows xp, however it has only allocated 2.75GB of storage space?

What is wrong?

Re: Recovering Original FW - Tested

Sat, 02 Aug 2008 20:04:32 +0000

Hi,

I bricked my 1TB single disk WE a few days ago while trying to get the gcc compiler back after firmware upgrade. I followed the updated instructions (http://mybookworld.wikidot.com/rescue-procedure) and it worked first time.

Brilliant, thanks guys.

Re: Recovering Original FW - Tested

Tue, 08 Jul 2008 19:05:56 +0000

Hello,

I am owner of a dead My Book World Edition II.

Does anyone know how I can recover my files by placing the 2 hdds to my desktop machine in RAID 0 as I have them configured on the My Book World Edition II NAS (1TB).

Each hdd has 4 linux partitions.

I didnt lost my files but I dont know how to access them in linux. Is there anybody that can tell me the procedure ? If I can access them in Linux I will be able to transfer them to another NAS of mine through the network.

Thank you

Re: Recovering Firmware

Fri, 27 Jun 2008 12:44:24 +0000

I have this line with fuel-gauge in the list by typing ps aux

root 668 0.0 2.4 1532 724 ? S 14:28 0:00 /bin/bash /usr/local/wdc/fuel-gauge

The Lan Port Leds are working too Orange lights permanent and the Yellow is blinking.

Here the full list if this helps :

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 1.1 1280 360 ? Ss 14:28 0:00 init
root 2 0.0 0.0 0 0 ? SN 14:28 0:00 [ksoftirqd/0]
root 3 0.0 0.0 0 0 ? S< 14:28 0:00 [events/0]
root 4 0.0 0.0 0 0 ? S< 14:28 0:00 [khelper]
root 5 0.0 0.0 0 0 ? S< 14:28 0:00 [kthread]
root 9 0.0 0.0 0 0 ? S< 14:28 0:00 [kblockd/0]
root 36 0.0 0.0 0 0 ? S 14:28 0:00 [pdflush]
root 37 0.0 0.0 0 0 ? S 14:28 0:00 [pdflush]
root 38 0.0 0.0 0 0 ? S 14:28 0:00 [kswapd0]
root 39 0.0 0.0 0 0 ? S< 14:28 0:00 [aio/0]
root 143 0.0 0.0 0 0 ? S< 14:28 0:00 [ata/0]
root 146 0.0 0.0 0 0 ? S< 14:28 0:00 [sata-endQ]
root 147 0.0 0.0 0 0 ? S< 14:28 0:00 [scsi_eh_0]
root 152 0.0 0.0 0 0 ? S< 14:28 0:00 [sata-endQ]
root 153 0.0 0.0 0 0 ? S< 14:28 0:00 [scsi_eh_1]
root 164 0.0 0.0 0 0 ? S< 14:28 0:00 [kcryptd/0]
root 165 0.0 0.0 0 0 ? S< 14:28 0:00 [kcryptd/0]
root 168 0.0 0.0 0 0 ? S< 14:28 0:00 [md3_raid1]
root 170 0.0 0.0 0 0 ? S< 14:28 0:00 [md2_raid1]
root 172 0.0 0.0 0 0 ? S< 14:28 0:00 [md1_raid1]
root 173 0.0 0.0 0 0 ? S< 14:28 0:00 [kjournald]
root 181 0.0 0.0 0 0 ? S< 14:28 0:00 [kjournald]
root 183 0.0 0.0 0 0 ? S< 14:28 0:00 [kjournald]
root 224 0.4 1.1 2144 356 ? S 14:28 0:05 /usr/sbin/sshd
root 487 0.0 0.0 0 0 ? S< 14:28 0:00 [khubd]
root 668 0.0 2.4 1532 724 ? S 14:28 0:00 /bin/bash /usr/local/wdc/fuel-gauge
root 676 0.0 0.7 560 232 ? S 14:28 0:00 /usr/local/wdc/heat-monitor
root 699 0.0 0.6 552 188 ? S 14:28 0:00 /sbin/keyring
root 758 0.0 4.7 1520 1432 ? SL 14:28 0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid
root 762 0.0 1.0 1284 320 ? S 14:28 0:00 /usr/sbin/inetd
root 766 0.0 1.0 740 328 ? S 14:28 0:00 /sbin/mDNSResponderPosix -f /etc/mDNSResponderPosix -b
root 769 0.0 2.2 1940 668 ? Ss 14:28 0:00 /usr/local/samba/sbin/nmbd -D -s/var/oxsemi/smb.conf -l/var/log
www-data 773 0.0 1.6 2488 504 ? S 14:28 0:00 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
www-data 777 0.8 16.3 8760 4924 ? S 14:28 0:10 perl /usr/www/lib/nasMaster.pl
root 785 0.0 1.0 1276 308 ? S 14:28 0:00 /usr/sbin/crond -c /etc/crontabs
root 799 0.3 25.6 30188 7716 ? S< 14:28 0:03 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 801 0.0 25.6 30188 7716 ? S< 14:28 0:00 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 802 0.0 25.6 30188 7716 ? S< 14:28 0:00 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 803 0.0 25.6 30188 7716 ? S< 14:28 0:00 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 823 0.0 2.2 6156 672 ? S 14:28 0:00 /usr/mionet/changeNotifySocket
root 828 0.0 2.5 1528 772 ? S 14:28 0:00 /bin/sh /usr/mionet/monitorCVM.sh
root 833 0.0 0.7 1276 232 ? S 14:28 0:00 udhcpc -n -p /var/run/udhcpc.eth0.pid -i eth0 -H MyBookWorld
root 838 0.0 1.1 1276 348 ttyS0 Ss+ 14:28 0:00 /sbin/getty -L ttyS0 115200 vt100
root 839 0.0 1.1 1272 356 ? Ss 14:28 0:00 /sbin/syslogd -n -m 0
root 840 0.0 1.1 1272 348 ? Ss 14:28 0:00 /sbin/klogd -n
root 841 0.0 2.2 6156 672 ? S 14:28 0:00 /usr/mionet/changeNotifySocket
root 842 0.0 2.2 6156 672 ? S 14:28 0:00 /usr/mionet/changeNotifySocket
root 843 0.0 2.2 6156 672 ? S 14:28 0:00 /usr/mionet/changeNotifySocket
root 845 0.0 2.2 6156 672 ? S 14:28 0:00 /usr/mionet/changeNotifySocket
root 853 0.0 25.6 30188 7716 ? S< 14:28 0:00 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 854 0.0 25.6 30188 7716 ? S< 14:28 0:00 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 855 0.1 25.6 30188 7716 ? S< 14:28 0:02 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 856 0.0 25.6 30188 7716 ? S< 14:28 0:00 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 857 0.0 25.6 30188 7716 ? S< 14:28 0:00 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 858 0.0 25.6 30188 7716 ? S< 14:28 0:00 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 859 0.0 25.6 30188 7716 ? S< 14:28 0:00 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 862 0.0 25.6 30188 7716 ? S< 14:28 0:00 /usr/mionet/bin/cvm -Djava.class.path=/usr/mionet/xml-apis.jar:/usr/mionet/crimson.jar:/usr/mionet/Senv
root 977 0.0 2.8 4736 864 ? Ss 14:33 0:00 /usr/sbin/sshd: saint [priv]
saint 991 0.8 2.0 4772 616 ? S 14:34 0:08 /usr/sbin/sshd: saint@pts/0
saint 992 0.0 3.3 1880 1004 pts/0 Ss+ 14:34 0:00 -sh
root 997 0.2 3.4 1588 1028 pts/0 S+ 14:34 0:02 -bash
root 1334 3.4 7.9 4632 2388 ? Ss 14:45 0:07 smbd -s/var/oxsemi/smb.conf -l/var/log -d0
root 1409 0.0 0.7 564 220 ? S 14:48 0:00 sleep 300
root 1421 0.0 0.7 564 220 ? S 14:48 0:00 sleep 30
root 1422 0.0 1.3 1400 412 pts/0 R+ 14:49 0:00 ps aux

Re: Recovering Firmware

Fri, 27 Jun 2008 11:54:11 +0000

http://mybookworld.wikidot.com/hacks-and-howto pick one from "getting in" i recommend telnet.
when u have ssh or telnet acces type "ps aux" and see if /usr/local/wdc/fuel-gauge is running.

on the leds again: Ethernet port on mbwe has leds! one is for link status(dark) other is for activity(light blinking).

Re: Recovering Firmware,sorrrry kevku !

Fri, 27 Jun 2008 11:10:50 +0000

All leds are working,I tested the PCB on other MBWE
I have not started to solder arround the leds.
Its not a problem with the leds or the pcb,it is a software problem

Hey Stark where is the topic for leds problem,I searched for it ?

I need infos or files to compare with my own on MBWE,there are files on the MBWE that are for the leds like the script in this forum,I do not know what to do with the script because im not LINUX stable.

Is it posible in Linux to remote configure my MBWE over Internet,like VNC in windows ?
Does anyone speak german here ?

Thanks

Re: Recovering Firmware,sorrrry kevku !

Fri, 27 Jun 2008 09:47:52 +0000

Since you had in your mind to solder on other leds, i expect that you got som knowledge about leds. I dont know how the leds on MBWE is connected, but i whould belive that they all have the same - (ground) so if you could mesure the voltage over the leds that dont work, you'll have figure out if it a hardware or software failure. :) If it's hardware failure (You'll got som voltage over a led thats dont light) then youll just replace it. but if thers non voltage there could be an problem in the connector or flat cable. or some software failure.

Ops, this isnt a topic for "led problem" :S

Re: Recovering Firmware,sorrrry kevku !

Fri, 27 Jun 2008 09:21:21 +0000

Sorry kevku ,I know this all,but it was not my MBWE.

1.)I have restored the MBWE for my friend becase he formated it to copy files on it .He atached the HD to windows computer.
He asks me every time if I have found out why the leds are not working.
2.) On my MBWE i cant start now to mod it.

OK.

My PCBs are the same as amorsent`s

Led PCB:
REV C
PCBA 2061-701434

Main:
Copyright 2007
GALAXY. INC
PCBA 2061-701490
REV.

The Rescue works fine,but I get trouble because the leds(the 6 capacity leds,the inner ring) do not work,the 4 leds(the outer ring)works.
So ,I just wantet to know if other people here that have rescued their MBWE have the same problem with leds like me ?

By pressing the power button or by plunging in the cable with 12 Volts > MBWE boots up Normal,you can shutdown it by repressing the power button.(like it was when buyed)

I am mad abot this because I ordered other leds to install in it somewhere in the morse code or so.(for moding it)

Like this in a line,the circle stays .(like a thermometer)

1 2 3 4 5 6
gr gr gr ye ye re
0%---50%---100%

I was copying files on MBW and noone of the capacity leds goes on.

So I can`t start soldering and moding it.

That was my Story.

SO Kevku I know you and other members are hard workers that can solve the led problem.

So do not be MAD at me.

I hope you can help me.

THANKS

Re: Recovering Firmware

Fri, 27 Jun 2008 08:32:10 +0000

I have the single drive 1TB version purchased in December (I think). I don't think it has Ethernet LEDs unless they are burried deep inside the jack. The router LEDs indicate a connection but don't seem to indicate any activity.

The LED board says:
REV C
PCBA 2061-701434 -[white bar]

The main board says:
Copyright 2007
GALAXY. INC
PCBA 2061-701490- [white bar]
REV. [white bar]

My S/N:WCASJ0180352

People who have had success with this procedure: what do your boards say? Could mine be a new hardware version incompatible w/ these rescue files?

Would the USB slot indicate a successful boot or only power? The moment I plug it in, I hear the drive spin up and seek (could be a boot, but could be just a self test).

Pressing the power button seems to have no effect at all - drive keeps spinning.

Re: Recovering Firmware

Fri, 27 Jun 2008 06:51:19 +0000

ofcourse they should work. make sure your wire is connected. On the booting then again … depends if you have a 1 or 2 disk version. 2 disk version's fan makes whuzz if it boots up correctly. 1 disk version its harder… u can check Ethernet leds and power from usb slot (just throw something there).

E: on the leds again: well you could have a newer hardware revision mybook that might actually be not working with the old wdc_leds module (highly unlikely)

Re: Recovering Fake Firmware - Without support from WD or NOONE HERE !Boot your Computer without Mainboard ! It works !

Fri, 27 Jun 2008 03:34:46 +0000

Ah, Douglas Adams. You sir are a man after my own heart.

Anywho, I thought the LEDs are supposed to work after the rescue procedure. If it is normal for them to not work then perhaps my device is booting after all? But it doesn't show up in the DHCP Client table on my router. How can I tell if the device is actually booting? I am still unable to regain any functionality out of it whatsoever.

-Thanks

Re: Recovering Fake Firmware - Without support from WD or NOONE HERE !Boot your Computer without Mainboard ! It works !

Thu, 26 Jun 2008 20:29:19 +0000

This isn't a support channel. ppl on this site are are doing this from their own free time, they are not getting paid for this. you should have a little more respect for the work they have done. You should learn to understand the purpose of open source and community software. This forum is not dead and the rescue works. In order for us to give you help you should have a bit more motivation and dedication to set up your mybook the way you want and to learn how to solve issues and provide information about them.

So long, and thanks for all the fish.

Re: Recovering Fake Firmware - Without support from WD or NOONE HERE !Boot your Computer without Mainboard ! It works !

Thu, 26 Jun 2008 19:58:23 +0000

Ach ja !

OOOOhhhh noone gives a shit about the leds or WD anywhere access here anyway.
Because noone can figure it out how to restore it .
In this case rescue does not work .

So that means for me I can throw away the housing .Its useless for me in this case .

Its like a clock without displaying hours because noone gives a shit about it here.
Whats the Time ? 1205 minutes after the sun came out,so calculate it.

This forum is dead.
Thanks for Nothing dude.

Re: Recovering Original FW - Capacity leds do not work anymore,WHY ??

Thu, 26 Jun 2008 17:00:27 +0000

get a grip dude. noone gives a shit about the leds or WD anywhere access here anyway.

Re: Recovering Original FW - Capacity leds do not work anymore,WHY ??

Wed, 25 Jun 2008 17:47:44 +0000

ONLY HIDDEN PROBLEMS AFTER RESCUE .EVERYTHING WORKS FIN TILL YOU FOUND OUT THE HIDDEN PROBLEMS AFTERALL.

I have problems now with the capacity leds ,after the rescue procedure.

Everything works only the capacity leds dont work.

FAULTY LINUX,RESCUE disables the capacity leds and WD Anywhere Acess.

Its better to buy an other USB 2.0/SATA enclosure for my disk and forget the MBWE forever ,format the disk to fat32 or ntfs for Windows and thats it.End of the LINUX MBWE .

WHAT ABOUT RESCUEING MY LEDS,WHERE ARE THE EXPERTS NOW ???????????

STARTING WD ANYWHERE IS NOT POSSIBLE !!!!

Re: Recovering Original FW - MAC changed how to restore ??

Wed, 25 Jun 2008 16:37:06 +0000

anyone?

Re: Recovering Original FW - MAC changed how to restore ??

Mon, 23 Jun 2008 17:11:14 +0000

I have tried with and without editing /etc/fstab (although I don't understand the reasoning for this. Why does the device change?)

I would expect it to still boot even if it couldn't mount the data partition, am I right? For the moment I would be happy if it will boot, then I can sort out the data partition.
I think I also tried renaming md2 and md3 (md1 not listed in /etc/fstab) to sda2 and sda3 thinking that perhaps these had changed as well. I still don't understand why would one partition of the same drive be sda while the rest are md. Especially if we are restoring to the original configuration.

You asked what I do at point 5 and 6.
At point 5 I go ahead and create the partition. But as it is identical to my original partition the file system remains intact and mountable. So I skip step 6 and don't format.

One weird thing… sometimes the data partition will show up as if it was only a 500GB drive not 1TB. I think this has to do with the rescue.img as it contains a partition table from a 500GB drive and overwrites the partition table from step 4 & 5 (basically making step 4 & 5 pointless). I copy the rescue.img and THEN do step 4 & 5. This issue was addressed earlier on this page: lefgrter 10 Apr 2008, 07:39 -0-400

Also, should the swap partition be type fd or 82? I have it set to fd because that's what the one in the rescue files is set to, but if it's swap shouldn't it be 82?

Re: Recovering Original FW - MAC changed how to restore ??

Mon, 23 Jun 2008 04:03:37 +0000

Hi all my MAC changed to 00:90:a9:15:99:84 is it possible to restore it back to original one ????

How ??

Hi amorsent

have you edited /etc/fstab ??
have you changed the name of the last partition from md4 to sda4 and umounte sda1 ?(It can be it is alredy sda4 because you have alredy data on it)

what have you done at point 5 and 6 ?

where are the smart linux people now ? Help is needed here ?

Re: Recovering Original FW - Tested

Mon, 23 Jun 2008 00:26:49 +0000

Hello,

I am having trouble with this rescue procedure. I have attempted it several times (although not formatting the data partition in step 6). All my data appears to be intact and I'd like to keep it that way for now.

I've done all the other rebuilding steps - rescue.img and the first 3 partitions and everything seems to be in order. However, when I put it back together and plug it in it won't boot. The drive spins up but no lights and it doesn't show up on DHCP. Also the power switch seems to have no effect. I don't think that not reformatting the data partition would cause it to not boot entirely would it? I also don't think it's a hardware problem, but is there anyway I can check to confirm this? By the way I have the single drive 1TB model.

Thank's in advance for any help.

Re: Recovering Original FW - Tested by the Saint on 500Gb

Sun, 22 Jun 2008 15:05:24 +0000

Here the Konsole log: (In German)

[saint@ASUS ~]$ su
Passwort:
[root@ASUS saint]# cd
[root@ASUS ~]# wget http://szabados.sk/mybook_we_rescue.zip
2008-06-22 16:19:15 http://szabados.sk/mybook_we_rescue.zip
Auflösen des Hostnamen »szabados.sk«…. 81.89.49.163
Verbindungsaufbau zu szabados.sk|81.89.49.163|:80… verbunden.
HTTP Anforderung gesendet, warte auf Antwort… 200 OK
Länge: 59921779 (57M) [application/zip]
In »mybook_we_rescue.zip« speichern.

100%[====================================================================================>] 59.921.779 363K/s in 3m 55s

2008-06-22 16:23:26 (249 KB/s) - »mybook_we_rescue.zip« gespeichert [59921779/59921779]

[root@ASUS ~]# unzip myboo_we_rescue.zip
unzip: cannot find or open myboo_we_rescue.zip, myboo_we_rescue.zip.zip or myboo_we_rescue.zip.ZIP.
[root@ASUS ~]#
[root@ASUS ~]# unzip mybook_we_rescue.zip
Archive: mybook_we_rescue.zip
creating: rescue/
inflating: rescue/SDA2_IMA.BZ2
inflating: rescue/rescue.img
inflating: rescue/SDA_PTAB
inflating: rescue/SDA1_IMA.BZ2
inflating: rescue/SDA3_IMA.BZ2
[root@ASUS ~]# cd rescue
[root@ASUS rescue]# dd if=/dev/zero of=/dev/sdb bs=1M count=3000
3000+0 Datensätze ein
3000+0 Datensätze aus
3145728000 Bytes (3,1 GB) kopiert, 38,4534 s, 81,8 MB/s
[root@ASUS rescue]# sfdisk /dev/sdb < SDA_PTAB
Überprüfe, dass niemand diese Festplatte zur Zeit benutzt …
OK

Festplatte /dev/sdb: 60801 Zylinder, 255 Köpfe, 63 Sektoren/Spur

sfdisk: FEHLER: Sektor 0 hat keine MS-DOS-Signatur
/dev/sdb: nicht erkannte Partitiontabellentyp
Alte Aufteilung:
Keine Partitionen gefunden
Neue Aufteilung:
Einheit = Sektoren von 512 Bytes, Zählung beginnt bei 0

Gerät boot. Anfang Ende #Sektoren Id System
/dev/sdb1 48195 5927984 5879790 fd Linux raid autodetect
/dev/sdb2 5927985 6136829 208845 fd Linux raid autodetect
/dev/sdb3 6136830 8112824 1975995 fd Linux raid autodetect
/dev/sdb4 0 - 0 0 Leer
Warnung: Keine primäre Partition wurde als bootfähig (aktiv) markiert.
Dies spielt bei LILO keine Rolle, aber der DOS-MBR wird auf
dieser Festplatte nicht booten.
Die neue Partitionstabelle wurde erfolgreich geschrieben

Die Partitionstabelle wird erneut gelesen…

Wenn Sie eine DOS-Partition angelegt oder geändert haben, z. B. /dev/foo7,
dann nehmen Sie dd(1), um die ersten 512 Bytes auf 0 zu setzen:
„dd if=/dev/zero of=/dev/foo7 bs=512 count=1“ (siehe fdisk(8)).
[root@ASUS rescue]# cfdisk /dev/sdb
Festplatte wurde verändert.

WARNUNG: Wenn Sie eine DOS-6.x-Partition angelegt
oder verändert haben, dann schauen Sie bitte in die
cfdisk-manual-Seite nach weiteren Informationen

[root@ASUS rescue]# umount /dev/sdb1
umount: /dev/sdb1 ist nicht eingehängt
[root@ASUS rescue]# umount /dev/sdb3
umount: /dev/sdb3 ist nicht eingehängt
[root@ASUS rescue]# umount /dev/sdb4
umount: /dev/sdb4 ist nicht eingehängt
[root@ASUS rescue]# mkfs.ext3 -m 0 /dev/sdb4
mke2fs 1.40.8 (13-Mar-2008)
Warning: 256-byte inodes not usable on older systems
Dateisystem-Label=
OS-Typ: Linux
Blockgröße=4096 (log=2)
Fragmentgröße=4096 (log=2)
30277632 Inodes, 121081905 Blöcke
0 Blöcke (0.00%) reserviert für den Superuser
Erster Datenblock=0
Maximale Dateisystem-Blöcke=0
3696 Blockgruppen
32768 Blöcke pro Gruppe, 32768 Fragmente pro Gruppe
8192 Inodes pro Gruppe
Superblock-Sicherungskopien gespeichert in den Blöcken:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000

Schreibe Inode-Tabellen: erledigt
Erstelle Journal (32768 Blöcke): erledigt
Schreibe Superblöcke und Dateisystem-Accountinginformationen: erledigt

Das Dateisystem wird automatisch alle 23 Mounts bzw. alle 180 Tage überprüft,
je nachdem, was zuerst eintritt. Veränderbar mit tune2fs -c oder -t .
[root@ASUS rescue]# dd if=rescue.img of=/dev/sdb
48195+0 Datensätze ein
48195+0 Datensätze aus
24675840 Bytes (25 MB) kopiert, 1,69031 s, 14,6 MB/s
[root@ASUS rescue]# bunzip2 SDA1_IMA.BZ2
bunzip2: Can't guess original name for SDA1_IMA.BZ2 — using SDA1_IMA.BZ2.out
[root@ASUS rescue]# dd if=SDA1_IMA.BZ2.out of=/dev/sdb1
5879790+0 Datensätze ein
5879790+0 Datensätze aus
3010452480 Bytes (3,0 GB) kopiert, 506,879 s, 5,9 MB/s
[root@ASUS rescue]# bunzip2 SDA2_IMA.BZ2
bunzip2: Can't guess original name for SDA2_IMA.BZ2 — using SDA2_IMA.BZ2.out
[root@ASUS rescue]# dd if=SDA2_IMA.BZ2.out of=/dev/sdb2
208845+0 Datensätze ein
208845+0 Datensätze aus
106928640 Bytes (107 MB) kopiert, 1,58988 s, 67,3 MB/s
[root@ASUS rescue]# bunzip2 SDA3_IMA.BZ2
bunzip2: Can't guess original name for SDA3_IMA.BZ2 — using SDA3_IMA.BZ2.out
[root@ASUS rescue]# dd if=SDA3_IMA.BZ2.out of=/dev/sdb3
1975995+0 Datensätze ein
1975995+0 Datensätze aus
1011709440 Bytes (1,0 GB) kopiert, 37,4165 s, 27,0 MB/s
[root@ASUS rescue]# tune2fs -c -1 -i 0 /dev/sdb1
tune2fs 1.40.8 (13-Mar-2008)
Setze maximale Mount-Anzahl auf -1
Setze Intervall zwischen Checks auf 0 Sekunden
[root@ASUS rescue]# tune2fs -c -1 -i 0 /dev/sdb3
tune2fs 1.40.8 (13-Mar-2008)
Setze maximale Mount-Anzahl auf -1
Setze Intervall zwischen Checks auf 0 Sekunden
[root@ASUS rescue]# tune2fs -c -1 -i 0 /dev/sdb4
tune2fs 1.40.8 (13-Mar-2008)
Setze maximale Mount-Anzahl auf -1
Setze Intervall zwischen Checks auf 0 Sekunden
[root@ASUS rescue]# mkdir sda1
[root@ASUS rescue]# mount -t ext3 /dev/sdb1 sda1
[root@ASUS rescue]# dir
rescue.img sda1 SDA1_IMA.BZ2.out SDA2_IMA.BZ2.out SDA3_IMA.BZ2.out SDA_PTAB
[root@ASUS rescue]# vi sda1/etc/fstab (EDITED WITH VI)
[root@ASUS rescue]# umount sda1
[root@ASUS rescue]#

I hope this helps non-linux users.

Thanks

Re: Recovering Original FW - Tested by the Saint

Fri, 20 Jun 2008 12:14:55 +0000

Hi all

I removed the 500Gb disk from MBWE

I used Open Linux (Mandriva) on my PC for first time cause I using Windows XP (I am new to Linux)

Installed the Original Firmware (following exactly the instructions) on 1Tb disk from MBEE (MyBook Essentilal Edition / USB 2.0 )

Installed the 1000Gb disk in MBWE

(In my case I have to use sde1 ,sde2 ,sde3 ,sde4 instead of sda1 ,sda2,sda3 ,sda4 » Linux sytem ??!! but I solved it)

It works well !

Now I have a MBWE with 1Tb and MBEE with 500Gb

Thanks

It works ! ! !

Re: Recovering Original FW - Tested

Tue, 10 Jun 2008 22:43:56 +0000

Hi kroner, I'm doing a rescue using you r same setup (system rescue CD and a SATA-to-USB cable).
All my partitions are showing up under /dev/sdb1-4. The problem is that whenever I try to mount the partitions, I get an "mount: /dev/sdb1 already mounted or /media/sdb1 busy".
Obviously I don't need to mount, but it's noted.

Then I went through the steps and at step 4, I got this error

 Checking that no-one is using this disk right now ... BLKRRPART: Device or resource busy This disk is currently in use - repartitioning is probably a bad idea. Umount all file systems, and swapoff all swap partitions on this disk. Use the --no-reread flag to suppress this check. Use the --force flag to overrule all checks.

I'm a bit confused because I'm positive that none of these partitions are mounted. See output of mount:

 tmpfs on / type tmpfs (rw) /dev/loop0 on /mnt/livecd type squashfs (ro,relatime) /dev/sr0 on /mnt/cdrom type iso9660 (ro,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec) udev on /dev type tmpfs (rw,nosuid,relatime,size=10240k,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,gid=5,mode=620) tmpfs on /lib/firmware type tmpfs (rw) tmpfs on /usr/portage type tmpfs (rw) usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)

Also, did you change the SDA_PTAB file from /dev/sda1 to /dev/sdb1 and so on? If you did SATA-to-USB then the partitions wouldn't be called sda, would they?

Any help here is greatly appreciated!

======================UPDATE===========================

I got past the above part by re-booting (although it happened several times). Now I'm getting the following error at step 11:

 root@sysresccd /mnt/sdb4/rescue % tune2fs -c -1 -i 0 /dev/sdb1 tune2fs 1.40.9 (27-Apr-2008) tune2fs: Bad magic number in super-block while trying to open /dev/sdb

I've skipped this part and went onto the next step and I get this error:

 root@sysresccd /mnt % mount -t ext3 /dev/sdb1 /mnt/sdb1 mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so

I've tried this about 5 times and I keep getting the same error. Is it because my hardrive is sdb rather than sda? Should that even make a difference (i've been switching out sda for sdb where appropriate)

really frustrated!!……………….

=====================UPDATE===========================

Right …. so I got through the entire process (having to reboot several times because of the above issues). Now I've tried my device and it's not booting up (or at least I think it isn't booting up). The network card is lighting up so I went back to step 10 again. Again it didn't fix the problem. Now I've taken out all partition information and started from scratch. I'm getting this error when using sfdisk:

 root@sysresccd /root/rescue % sfdisk /dev/sda < SDA_PTAB Checking that no-one is using this disk right now ... OK Disk /dev/sda: 121601 cylinders, 255 heads, 63 sectors/track sfdisk: ERROR: sector 0 does not have an msdos signature /dev/sda: unrecognized partition table type Old situation: No partitions found New situation: Units = sectors of 512 bytes, counting from 0 Device Boot Start End #sectors Id System /dev/sda1 48195 5927984 5879790 fd Linux raid autodetect /dev/sda2 5927985 6136829 208845 fd Linux raid autodetect /dev/sda3 6136830 8112824 1975995 fd Linux raid autodetect /dev/sda4 0 - 0 0 Empty Warning: no primary partition is marked bootable (active) This does not matter for LILO, but the DOS MBR will not boot this disk. Successfully wrote the new partition table Re-reading the partition table ... If you created or changed a DOS partition, /dev/foo7, say, then use dd(1) to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1 (See fdisk(8).)

Does anyone know if this is the issue?

HELP!!!!

Re: Recovering Original FW - Tested

Sun, 08 Jun 2008 08:44:11 +0000

~ is the home directory of the current user. On some apple mac keyboard, there is no ~ so you can use alt+n then space (alt is also known as the option key). You can also use $HOME instead of ~. When you are beginning the procedure, you use the pc. The root password is the password of the pc. It sometimes do not work (if there is no root user). In this case, use sudo su instead of su root.

Re: Recovering Original FW - Tested

Sat, 07 Jun 2008 23:34:36 +0000

Hi Guys,
I have a MBWE 1 TB version.
Long story short, someone was trying to install gcc on my machine, and ended up deleting the libgcc_s.so.1 file. Obviously my device is bricked now.

So now that I have no way of getting into the machine unless I use the rescue procedure, does anyone have any suggestions of how I can get my libraries back on the HD without having to go through the entire rescue proc?

disaster: Can you put a bit more info on how you used System Rescue CD?

Any help would be appreciated.

Re: Recovering Original FW - Tested

Thu, 05 Jun 2008 18:20:06 +0000

Do i need to set a jumper or something like that?

Re: Recovering Original FW - Tested

Thu, 05 Jun 2008 18:13:43 +0000

cd ~
su root [enter root passwd]

The ~ , must i use theire the "codename" of my disk

like cd /dev/sdb (in my case)

? And what root password, of the pc or from the HD? I did tried it but cant get anything to work :S

Re: Recovering Original FW - Tested

Mon, 26 May 2008 19:36:18 +0000

cd ~
su root [enter root passwd]

First step, what if i dont know my password anymore? :S

Re: Recovering Original FW - Tested

Wed, 14 May 2008 12:50:31 +0000

quick question, why does only /dev/md4 have to be replaced? shouldn't /dev/md3 and /dev/md2 need to be changed to /dev/sd3 and /dev/sd2?

Re: Recovering Original FW - Tested

Sat, 26 Apr 2008 17:41:09 +0000

Thank you for your answer.
So I'll backup everything before doing that, and will let you know how everything went !

—
GuiGou

Re: Recovering Original FW - Tested

Sat, 26 Apr 2008 11:08:43 +0000

You normally will lost all your data, so backup it before, after first stage.
You can try to skip 3 to 7 steps if you disk still have the good partitions (you can check it with cfdisk, but don't modify anything).
In step 12, you will probably don't have to do that : /dev/md4 MUST BE REPLACED BY /dev/sda4.
I hope your data will not forget if you do that.

Re: Recovering Original FW - Tested

Wed, 23 Apr 2008 17:44:07 +0000

Hi !
've got some problems with my MBWE 500Go,
and think gonna test the rescue procedure tonight.
One question, will I loose all the data I have on the hard disk ?!

Thank you for your help,
Best regards.

—
GuiGou

Re: Recovering Original FW - Tested

Sat, 19 Apr 2008 09:07:18 +0000

cd ~ and su root are unix/linux commands.
Executing those commands are not possible in Windows and it's not possible to read the disk file system by default : it is not ntfs but ext2/3 file system.
I suggest you to create an Ubunto 6.06 live CD (this version support also RAID so it is working for My Book World and My Book World II).
After that you just have to restart your machine and boot on the CD. You don't have to install Ubunto on an hard disk. Then, open a terminal…
I recommand to do an ls /dev/sd* before plug-in your usb disk and after, so you will know which letter you must use (it's not necessary sda).

Re: Recovering Original FW - Tested

Thu, 17 Apr 2008 18:47:17 +0000

Is theire anybody who wants to help me with my problem?
Put your MSN addres here or mail it to moc.liamg|spoonkduur#moc.liamg|spoonkduur please.

I speak dutch and english

Re: Recovering Original FW - Tested

Thu, 17 Apr 2008 18:27:37 +0000

I have my pc running with windows XP

Re: Recovering Original FW - Tested

Thu, 17 Apr 2008 18:15:02 +0000

I have linked my HD to my pc.
But how can I login?

cd ~
su root [enter root passwd]

where can i do this and how? With putty?

Re: Recovering Original FW - Tested

Thu, 10 Apr 2008 19:49:04 +0000

Many thanks to all involved in putting this procedure together, rescued my non-booting 500gb MBW first go without a hitch.

Re: Recovering Original FW - Tested

Thu, 10 Apr 2008 11:39:26 +0000

I have tryed the rescue guide on my MBW 1TB single drive, and i have experienced only one problem…
The file rescue.img is obviously take from a 500GB MBWand from the moment that i execute the step 7

the partition sda4 that i have created on step 5 is ruined and in the end i have a working MBW 1TB with a working space of 461 GB and 465 GB unallocated space!!!!! with some reading errors (I can't resize the partition with Gparted applicaton from Ubuntu!!!)
I have solved this problem by changing the steps order
After the step 4

4. Create the first 3 system partitions

sfdisk /dev/sda < SDA_PTAB

I have executed the step 7

7. Copy the contents of rescue.img to the disk

dd if=rescue.img of=/dev/sda

THEN gone to step 5

cfdisk /dev/sda

At the end of the disk go to sda4 and DELETE it… THEN follow the instructions below
there is much free space, create there a PRIMARY partition, set it to be TYPE=fd
This is because this manual is usable for all kind of disks big enough… So you can do this also with a 500G, 750G, 1000G or bigger disk. So the partition at the end is variable size dependent on the disk.

After that follow the rest of the guide without step 7 again

Thats it !!!

By the way, you saved my MBW. Thanks…!!!!!!!!!!!
Sorry for my grammar mistakes but english is not my native language

Re: Recovering Original FW - Tested

Tue, 08 Apr 2008 06:37:27 +0000

Hi, I got it working. Again I copied bit by bit partitions sda1, sda2 and sda3 (now without editing etc/fstab) and mybook is communicating again!

Thanks mister! ;-)

Re: Recovering Original FW - Tested

Mon, 07 Apr 2008 19:49:56 +0000

Hi I have problems with connecting to mbwe. I copied rescue.img, sda1, sda2 and sda3, but still no connection.

Is it possible to erase whole sda3 partition without touching sda4? Maybe this is the problem. I cannot erase whole disk, because sda4 is full of data.

Do you have any suggestions?

Thanks ;-)

Re: Recovering Original FW - Tested

Wed, 19 Mar 2008 18:05:23 +0000

I have post a procedure to restore the RAID, but not the data. I think that with some modification, it is probably possible to restore the data also.
Check on post MacUser 15 Mar 2008

Re: Recovering Original FW - Tested

Wed, 19 Mar 2008 17:58:08 +0000

In my case it do not work. Try my procedure given here (MacUser 15 Mar 2008)

Re: Recovering Original FW - Tested

Wed, 19 Mar 2008 17:55:31 +0000

Try my procedure given here (MacUser 15 Mar 2008)

Re: Recovering Original FW - Tested

Wed, 19 Mar 2008 03:34:55 +0000

Maybe someone can help me with this scenario…

My MBWE is up and running and I just want to back it down to the way it was before the firmware upfrage to 2.00.15.

Can I do just portions of this procedure to restore the firmare and gcc compiler and leave my shares intact?

I already tried restoring /usr from the backup image and that did not correct the gcc issues. I can't make or configure any programs.