Recovering Original FW - Tested

summary:

Hello This is based on http://mybookworld.wikidot.com/backup-images-of-mybook, but tested and fully functional.

Recovering Original FW - Tested

PCnity 1192990737|%e %b %Y, %H:%M %Z|agohover

Hello

I recently screwed my friend's MyBook World Edition (750 GiB) so I had to recover it completely. I didn't know that there should be some system partition, so i formated the whole drive with ext3 and copied many Gigs of stuff on that partition (no undelete was possible).

THERE IS NO OFFICIAL RESCUE PROCEDURE AVAILABLE FROM WESTERN DIGITAL! THIS IS A REAL BIG SHAME!!! I DO NOT RECOMMEND THIS PRODUCT!
Gigabit NAS??? FORGET IT!!! It can not use the bandwidth of 100 mbps network… The Gigabit port is just for fun.

After googling the net i found this site and tried this manual: http://mybookworld.wikidot.com/backup-images-of-mybook But it didn't work at all… I also found this how to http://www.ismprofessional.net/pascucci/documenti/mybook/mybook-hacking-en.html, but its about getting a GNU/Debian Lenny on the MyBook… Not the original system. (The friend of mine is NOT Linux compatible :)

From the Debian Lenny how to i realized that the backup images would probably work, but there is also some special boot loader… Or 2 :) and they weren't within the download of original rescue…

I've got this damn thing working by asking another friend to do me a favor… "dd if=/dev/sda of=/somewhere/rescue.img bs=512 count=48194" :) So i had a copy of the space between the start of disk to the start of the first partition.

The steps of recovery

100% Functional for ALL DISK SIZES.

1. Remove the HDD from MyBook World Edition and connect it to your PC. In this manual i refer to the disk as /dev/sda1

cd ~
su root [enter root passwd]

2. Download the rescue files [57 MiB]

wget http://szabados.sk/mybook_we_rescue.zip
unzip mybook_we_rescue.zip
cd rescue

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

dd if=/dev/zero of=/dev/sda bs=1M count=3000

4. Create the first 3 system partitions

sfdisk /dev/sda < SDA_PTAB

5. Create the last partition at the end of the disk

cfdisk /dev/sda

At the end of the disk 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.

Some Linux distributions do automounting new partitions… So umount them if possible.

umount /dev/sda1
umount /dev/sda3
umount /dev/sda4

6. Format 4th partition with no space reserved for UID 0

mkfs.ext3 -m 0 /dev/sda4

You need about 4 GiB of free space for this rescue procedure, if you do not have enough follow the steps bellow.

You do not have to do this if you have enough free space…

mkdir /mnt/sda4
mount /dev/sda4 /mnt/sda4 -t ext3
cd ..
mv rescue /mnt/sda4
cd /mnt/sda4/rescue

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

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

8. Unpack and copy the contents of the 1. system partition

You'll need cca 3 GiB of free space.

bunzip2 SDA1_IMA.BZ2
dd if=SDA1_IMA.BZ2.out of=/dev/sda1

If you see a message like this: "I/0 or other error, bailing out. Possible reson follows. No space left on device" Follow the "Low Space rescue" described at step 6 and then continue from where you stooped

9. Unpack and copy the contents of the swap [2nd] partition

You'll need cca 100 MiB of free space.

bunzip2 SDA2_IMA.BZ2
dd if=SDA2_IMA.BZ2.out of=/dev/sda2

If you see a message like this: "I/0 or other error, bailing out. Possible reson follows. No space left on device" Follow the "Low Space rescue" described at step 6 and then continue from where you stooped

10. Unpack and copy the contents of 3rd system partition

You'll need cca 1 GiB of free space.

bunzip2 SDA3_IMA.BZ2
dd if=SDA3_IMA.BZ2.out  of=/dev/sda3

If you see a message like this: "I/0 or other error, bailing out. Possible reson follows. No space left on device" Follow the "Low Space rescue" described at step 6 and then continue from where you stooped

11. Turn off fsck for all [NON SWAP] system partitions

tune2fs -c -1 -i 0 /dev/sda1
tune2fs -c -1 -i 0 /dev/sda3
tune2fs -c -1 -i 0 /dev/sda4

12. Edit /etc/fstab

mkdir sda1
mount -t ext3 /dev/sda1 sda1
nano sda1/etc/fstab

/dev/md4 MUST BE REPLACED BY /dev/sda4!

Save it by pressing CTRL + X, Y, ENTER.
Or use any other editor you like… [Nano is quite simple]

umount sda1

DO NOT FORGET THIS!

13. poweroff the computer

Plug the drive back to MyBook and be happy its running again ;)

PLEASE READ

KNOWN PROBLEMS

1. The lights go on, but MyBook do not listen on any network address
2. The DATA partition does not mount automaticly

1) This problem is because of some coruption in the 3rd partition… Also MyBook shows to be connected only to 100 mbps on gigabit network.

HOW TO FIX —> FOLLOW STEP 10 of the manual above

2) This is because the 4th partition isn't recognized as md4 but as sda4…

HOW TO FIX —> FOLLOW STEP 12 of the manual above
DO NOT FORGET TO UMOUNT THE PARTITION CORRECTLY!

If you have another problem, start from scratch… This manual at its actual state is 100% OK

last edited on 1195090269|%e %b %Y, %H:%M %Z|agohover by PCnity + show more

Re: Recovering Original FW - Tested

floris 1192992604|%e %b %Y, %H:%M %Z|agohover

Whoops at step 5:
mkfs.ext3 /dev/hda3
mkfs.ext3 /dev/hda4
I hope readers will catch that one before acting.

Re: Recovering Original FW - Tested

PCnity 1192994538|%e %b %Y, %H:%M %Z|agohover

Fixed.

last edited on 1194393677|%e %b %Y, %H:%M %Z|agohover by PCnity + show more

Re: Recovering Original FW - Tested

Zium 1192994614|%e %b %Y, %H:%M %Z|agohover

You could also add the link to this post on the main page of howto's

Re: Recovering Original FW - Tested

ionoff 1193036503|%e %b %Y, %H:%M %Z|agohover

Good Job,
I'll make the wiki change when I can find the time to document your success and steps.

I am going to also automate a restore for single drive world editions using only the file images, I just need the time to do it.

last edited on 1193327926|%e %b %Y, %H:%M %Z|agohover by ionoff + show more

Re: Recovering Original FW - Tested

Freshman 1193341619|%e %b %Y, %H:%M %Z|agohover

Why 'hda' not 'sda' are here? Could you clarify?

mkfs.ext3 /dev/hda3
mkfs.ext3 /dev/hda4

Re: Recovering Original FW - Tested

floris 1193351322|%e %b %Y, %H:%M %Z|agohover

The problem was the text had some /dev/hda strings. After I posted that whoops message PCnity replied he edited the text.

last edited on 1193351386|%e %b %Y, %H:%M %Z|agohover by floris + show more

Re: Recovering Original FW - Tested

PCnity 1193716643|%e %b %Y, %H:%M %Z|agohover

Yes… It was just a typo…

Follow the manual at its actual state. I went step by step after zero filling the drive… IT WORKS! :)

Re: Recovering Original FW - Tested

Freshman 1194301354|%e %b %Y, %H:%M %Z|agohover

Hi,

I have problem on step 11):

11) Edit /etc/fstab
mkdir sda1
mount /dev/sda1 sda1
nano sda1/etc/fstab

$ sudo mount /dev/sda1 sda1
mount: unknown filesystem type 'linux_raid_member'

Any suggestions?

Re: Recovering Original FW - Tested

PCnity 1194391440|%e %b %Y, %H:%M %Z|agohover

Soory… Yes… :)

mount /dev/sda1 sda1 -t ext3

or

$ sudo mount /dev/sda1 sda1 -t ext3

Re: Recovering Original FW - Tested

Freshman 1194469134|%e %b %Y, %H:%M %Z|agohover

Great!!! It works again
I have managed to connect to the web-interface (DHCP adrressing):

Device Name:      MyBookWorld
Firmware:     01.01.18
Drive Status:     OK

Before I crash it again what are the safest ways to?

1. Get SSH working (with mionet disabling)
2. Get smart-spindown working (if present)

Thanks a lot for the forum's fellowship!

Re: Recovering Original FW - Tested

Freshman 1194466924|%e %b %Y, %H:%M %Z|agohover

Hello PCnity,

following your new nice how-to. Just small addition (or it only under my dedicated Ubuntu computer?):

after step
5. Create the last partition at the end of the disk
and before step
6. Format 4th partition with no space reserved for UID 0
I use to unmount sda4 because formatting did not work:

$ sudo mkfs.ext3 -m 0 /dev/sda4
mke2fs 1.40-WIP (14-Nov-2006)
/dev/sda4 is mounted; will not make a filesystem here!

Going forward…

Re: Recovering Original FW - Tested

PCnity 1194484491|%e %b %Y, %H:%M %Z|agohover

/dev/sda4 shouldn't be mounted this time… So umount is ok.
It is possible that you system did mount all possible disk partitions automaticlay…

Re: Recovering Original FW - Tested

piotrus 1195755525|%e %b %Y, %H:%M %Z|agohover

Exellent howto ! Works like a charm. Thnx !

Re: Recovering Original FW - Tested

2ge 1243789121|%e %b %Y, %H:%M %Z|agohover

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

Re: Recovering Original FW - Tested

kknapp 1193340741|%e %b %Y, %H:%M %Z|agohover

This link is gone http://szabados.sk/mybook_we_rescue.zip

is there any chance we can get a working one?

Re: Recovering Original FW - Tested

Zium 1193341769|%e %b %Y, %H:%M %Z|agohover

I've the file here, where can i post it ?

Re: Recovering Original FW - Tested

kknapp 1193357930|%e %b %Y, %H:%M %Z|agohover

You could just drop it on rapidshare or one of the others then post a link here, it would help a bunch.

Re: Recovering Original FW - Tested

ionoff 1193377910|%e %b %Y, %H:%M %Z|agohover

http://rapidshare.com/files/65242458/mybook_we_rescue.zip

Re: Recovering Original FW - Tested

kknapp 1193408570|%e %b %Y, %H:%M %Z|agohover

Thanks, I just tested the rescue.img and I get the LED's to light up but still no activity on the NIC and no files seem to have been modified.

If you extract the files for sda1 and look in 'usr/www/nbin/dm_formatInternal.sh' line 70 is "dd if=$OLD of=$DEV bs=512 count=48194" which copies the first 16MB from the original drive to a new drive. I believe this is what is needed to get these images to work.

Re: Recovering Original FW - Tested

PCnity 1193658370|%e %b %Y, %H:%M %Z|agohover

Hello
The link i posted is already working… I had a problems with servers.

I used to recover the drive a bigger image [5 GiB] from another WD MyBook WE. I'll try to make new images from my setup.

"dd if=$OLD of=$DEV bs=512 count=48194" This is done in the 6th step. There is no problem. The MyBook must be booting if the lights went up. A problem will be somewhere at /dev/sda1 or /dev/sda3.

It would be very helpull if could someone post their images here. I havent got the mybook at home, but i'll try also.

Re: Recovering Original FW - Tested

PCnity 1193661360|%e %b %Y, %H:%M %Z|agohover

Hello

I crashed that MyBook again for testing purpouses… And found out that the gz archive of files from /dev/sda3 wast ok. Now follow the steps one more time, or just recover the 3. partition.

Re: Recovering Original FW - Tested

PCnity 1194484861|%e %b %Y, %H:%M %Z|agohover

The link on RapidShare is out of date! DO NOT USE IT.

Re: Recovering Original FW - Tested

lukasz 1193753650|%e %b %Y, %H:%M %Z|agohover

Hello I have tried Your procedure and files on the WB 500 - unfortunately sda3 partition does not mount automatically when the Mybookworld 500 WE is booting. Maybe it is conncected to the geometry of the drive as I have said I have the problem with the 500 not 750 version.

Anybody has the clean or unclen but complete image for the WE 500 version?

Re: Recovering Original FW - Tested

PCnity 1194391564|%e %b %Y, %H:%M %Z|agohover

This is not a problem of the disk size!

a) You have an error and didn't mean /dev/sda3 but /dev/sda4… —> FOLLOW STEP 12.
b) Try following step 10

last edited on 1194393818|%e %b %Y, %H:%M %Z|agohover by PCnity + show more

Re: Recovering Original FW - Tested

AndersHH 1194293253|%e %b %Y, %H:%M %Z|agohover

How can you set the IP address, subnet mask to manual before you reboot the mybook??..

I can see light in the outer circle, the switch has light, to network connection but can't find it by DHCP..

Can someone please help???
Eventually via mail, or MSN..

-AndersHH

Re: Recovering Original FW - Tested

PCnity 1194391771|%e %b %Y, %H:%M %Z|agohover

You have to erase the whole 3. partition and copy it from the image. It will work… I promise. ;)

I wrote the first manual after rescuing the MyBook… Then i zerofilled the disk again and found out that there was a problem… The lights went on, but it didnt boot corectly… Normaly mybook has a gigabit connection, in this case it shows only 100mbps AND HAS NO IP! So you CANT ACCESS IT AT ALL!

The whole error was the 3. partiotion… You have to copy it from the image in the http://szabados.sk/mybook_we_rescue.zip! It will work.

Re: Recovering Original FW - Tested

fybyfyby 1207597796|%e %b %Y, %H:%M %Z|agohover

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

fybyfyby 1207636647|%e %b %Y, %H:%M %Z|agohover

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

feinbein 1194730557|%e %b %Y, %H:%M %Z|agohover

Hi
I am new to this forum and just wondered why you are going through such a complicated way of restoring your device. Would it not be much easier to get someone to use g4u to make a clone of the original disk and find a way to get it to you? You could use g4u to play it back to your disk provided you have exactly the same model.
That would also be a very easy and comfortable way of installing Debian to mybook, wouldn't it?
Please tell me if I am getting something completely wrong here…
So, who can provide the images?

Re: Recovering Original FW - Tested

PCnity 1194919086|%e %b %Y, %H:%M %Z|agohover

I think that providing a 4+ GiB image is worse than making a few simple steps… But if i get the MyBook one more time to my hands, i put the image on the net.

Re: Recovering Original FW - Tested

feinbein 1195299527|%e %b %Y, %H:%M %Z|agohover

I think if one uses the hints about shrinking the image it shoud be possible to reduce the image size of a virgin MYBOOK 500GB to less than 500MB for the entire disk.
That would be a well acceptable size. Dont know about the debian image though.

Re: Recovering Original FW - Tested

shadowrazor 1194814240|%e %b %Y, %H:%M %Z|agohover

when i try step 4:

sfdisk /dev/sda < SDA_PTAB

he says: this disk is currently in use

does anyone have an idea?

Re: Recovering Original FW - Tested

PCnity 1194918859|%e %b %Y, %H:%M %Z|agohover

R U sure that the MyBook HDD is /dev/sda?

Try other livecd/rescue…

Re: Recovering Original FW - Tested

shadowrazor 1194978525|%e %b %Y, %H:%M %Z|agohover

ok, i solved that problem, it didn't work because i used capital letters. But now i have another problem

when i try: sudo bunzip2 sda1_ima.bz2

linux reponds with: "I/0 or other error, bailing out. Possible reson follows. No space left on device"

When I try to run it from an usb stick linux reponds with the same error, while I have atleast 200 mb free on the usb stick..

does anybody knows how that comes?

grtz

Re: Recovering Original FW - Tested

PCnity 1195005566|%e %b %Y, %H:%M %Z|agohover

SDA1_IMA.BZ2.out is about 3 GiB big :)

Could that be the problem? :)

Re: Recovering Original FW - Tested

AndersHH 1194904714|%e %b %Y, %H:%M %Z|agohover

I would just like to confirm that my mybook now works again!!!!!!

Thanks alot for the help everybody!!

-AndersHH :)

Re: Recovering Original FW - Tested

PCnity 1195006563|%e %b %Y, %H:%M %Z|agohover

I am quite sure now that the manual is perfectly working. Got positive feedback :)
So I created a new page and appended it to the side panel: http://mybookworld.wikidot.com/rescue-procedure

Hope it helps :)

Re: Recovering Original FW - Tested

ch07 1195049798|%e %b %Y, %H:%M %Z|agohover

Success story:
I bricked my MyBook WE (500GB) last week (first day I got it :-S —— STUPID!) but manage to get it up and running even if I am a total nOOb with Linux = terminal exercises: Downloaded the Ubuntu 7.10 live-cd and burned it. I hijacked a Windows XP machine because I needed the SATA-interface that I dont have in my Mac (Im a ordinary Mac-user 24/7) and understood that the Windows-disk was a NTFS-disk so I could not place the 3GB huge 'SDA1_IMA.BZ2.out'-file there. I disconnected the main Windows-disk and placed the cables on to the MyBook-disk. Fired up the PC, started Ubuntu from CD-ROM and I followed the instructions here above! After the step that I formatted the 4th partition ("6. Format 4th partition with no space reserved for UID 0") I mounted and copied the file 'mybook_we_rescue.zip' from a USB stick to this volume. And did everything from there which gave me the 3GB+ space I needed!

So now I am a little bit richer with some Linux-terminal/environment knowledge (learned some other commands (cp etc ;-) ) as well!

So thanks PCnity for making this happen!

Btw. I realized that the MAC-address changed after all this so the one printed on the label of the housing is not the same anymore….I thought the MAC address is a fixed number… Can someone confirm this?

C :)

Re: Recovering Original FW - Tested

PCnity 1195089081|%e %b %Y, %H:%M %Z|agohover

Hello

I will rewrite the manual one more time to the system you did… Fetching and unpacking the files to the 4th partition ;) It could help more people.

Mac address is "written" in the network chip, but it is software changeable. I think that the OS reads the MAC address and then send Ethernet frames with its address… So it depends on the system if it uses the original MAC. I am not sure… Just thinking.

But i don't see any logic why would the MyBook system override the MAC :)

Re: Recovering Original FW - Tested

vincent31 1195821842|%e %b %Y, %H:%M %Z|agohover

Hello,

It seems the boot loader included in mybook_we_rescue.zip contains the MAC address from the dumped mybook.

I declared my official mac address into my DHCP server in order to reserve specifically an IP address.

As the MAC changed, it looked like the mybook was not pingable.
And the second problem is that this mac address need to be unique.

If you do a grep of the 2 last digits of the mac address in /proc/cmdline, you will find an hex sequence.
/proc/cmdline is not a file, but a view of the cmdline used bye the process, so you cannot change it.

I don't know how to modify it in the boot (using boottool, for example ?), but here is a small tip to change it through the system.

Go to /etc/init.d.

Change using vi the network_control.sh file :

ip addr flush eth0
ip link set dev eth0 up

into

ip addr flush eth0
ifconfig eth0 hw ether xx:xx:xx:xx:xx:xx
ip link set dev eth0 up

where xx:xx:xx:xx:xx:xx is the MAC address written on the mybook box.

Save the file, then power off and power on pressing the reset button.

If you type ifconfig -a, you will see your correct mac address.

Re: Recovering Original FW - Tested

PCnity 1197429315|%e %b %Y, %H:%M %Z|agohover

Why do you want to have a unique MAC address?

I see just one reason: Using more than one MyBook world in one network segment…

Re: Recovering Original FW - Tested

ETMegabyte 1245681464|%e %b %Y, %H:%M %Z|agohover

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

warspite 1195236821|%e %b %Y, %H:%M %Z|agohover

On the verge of using this method, but it seems all the people who used had single drives.
Anybody been able to use it on Raid1 config?

Won't the mdadm config be destroyed somehow?

Re: Recovering Original FW - Tested

PCnity 1197429368|%e %b %Y, %H:%M %Z|agohover

If you have a raid 1 config… Wipe just the failed drive. MyBook should recover the raid automaticly.

Re: Recovering Original FW - Tested

Hiker77 1200837127|%e %b %Y, %H:%M %Z|agohover

How to manage this option? How to build/mange RAID1 config from PC with mybook drive A mounted?

thankx!

Re: Recovering Original FW - Tested

Hiker77 1200519265|%e %b %Y, %H:%M %Z|agohover

Hi!
I've screwed my WEII 2TB. RAID 1 haven't been used (was mounted as 1 big partition on default).
Is that method of recovery suitible for 2 disk's WE? Second disk will be mounted automaticly? How to ensure that?

thanks!

last edited on 1200520063|%e %b %Y, %H:%M %Z|agohover by Hiker77 + show more

Re: Recovering Original FW - Tested

MacUser 1205949488|%e %b %Y, %H:%M %Z|agohover

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

Re: Recovering Original FW - Tested

Mazec 1201065338|%e %b %Y, %H:%M %Z|agohover

Hi, i got Mybook World II enclosure only, without disks. I decided to install 2x Samsung 200G HDs. Used the recovery procedure described many times here on disk A and device is living now. Disk B was completely erased, no partitions. Disabled MioNet, enabled SSH and Hinners Webif interface, all works.

Problem is, that MBWII doesnt recognize /dev/sda4, thus not showing drive size in web interface. Under WD web interface the option for changing raid level and add new disk dissapeared, only USB disconnect is visible.
What is confusing for me is if i put drive back to LiveCD machine and run "cfdisk /dev/sda it returns error about /sda3 bigger than physical size of HD. Is this normal? I suppose the disk should be readable all the time under LiveCD.

Yes,i repeated the step 12, but it seems its working only for single drive units, not for dual HDs.
Here is part of kernel msgs:

<6>ox800sata init
<6>ox800sata: 924 based sata core.
<6>ata1: SATA max UDMA/133 cmd 0x0 ctl 0x0 bmdma 0x0 irq 18
<6>ata1: SATA link up 1.5 Gbps (SStatus 113)
<7>ata1: dev 0 cfg 49:2f00 82:746b 83:7f09 84:4123 85:7469 86:be01 87:4123 88:00ff
<6>ata1: dev 0 ATA-7, max UDMA7, 390721968 sectors: LBA48
<6>ata1: dev 0 configured for UDMA/133
<6>scsi0 : ox800sata
<5> Vendor: ATA Model: SAMSUNG HD200HJ Rev: KF10
<5> Type: Direct-Access ANSI SCSI revision: 05
<6>ox800sata: 924 based sata core.
<6>ata2: SATA max UDMA/133 cmd 0x0 ctl 0x0 bmdma 0x0 irq 19
<6>ata2: SATA link up 1.5 Gbps (SStatus 113)
<7>ata2: dev 0 cfg 49:2f00 82:746b 83:7f09 84:4123 85:7469 86:be01 87:4123 88:00ff
<6>ata2: dev 0 ATA-7, max UDMA7, 390721968 sectors: LBA48
<6>ata2: dev 0 configured for UDMA/133
<6>scsi1 : ox800sata
<5> Vendor: ATA Model: SAMSUNG HD200HJ Rev: KF10
<5> Type: Direct-Access ANSI SCSI revision: 05
<5>SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 00 3a 00 00
<5>SCSI device sda: drive cache: write back
<5>SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 00 3a 00 00
<5>SCSI device sda: drive cache: write back
<6> sda:
<5>sd 0:0:0:0: Attached scsi disk sda
<5>SCSI device sdb: 390721968 512-byte hdwr sectors (200050 MB)
<5>sdb: Write Protect is off
<7>sdb: Mode Sense: 00 3a 00 00
<5>SCSI device sdb: drive cache: write back
<5>SCSI device sdb: 390721968 512-byte hdwr sectors (200050 MB)
<5>sdb: Write Protect is off
<7>sdb: Mode Sense: 00 3a 00 00
<5>SCSI device sdb: drive cache: write back
<6> sdb: sdb1 sdb2 sdb3 sdb4
<5>sd 1:0:0:0: Attached scsi disk sdb
<6>mice: PS/2 mouse device common for all mice
<6>md: linear personality registered for level -1
<6>md: raid1 personality registered for level 1
<6>md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
<6>md: bitmap version 4.39
<6>device-mapper: 4.6.0-ioctl (2006-02-17) initialised: moc.tahder|leved-md#moc.tahder|leved-md
<6>TCP bic registered
<6>NET: Registered protocol family 1
<6>NET: Registered protocol family 17
<6>md: Autodetecting RAID arrays.
<4>md: disabled device sdb4, could not read superblock.
<4>md: sdb4 has invalid sb, not importing!
<6>md: autorun …
<6>md: considering sdb3 …
<6>md: adding sdb3 …
<4>md: sdb2 has different UUID to sdb3
<4>md: sdb1 has different UUID to sdb3
<6>md: created md3
<6>md: bind
<6>md: running:
<4>raid1 run
<6>raid1: raid set md3 active with 1 out of 2 mirrors
<6>md: considering sdb2 …
<6>md: adding sdb2 …
<4>md: sdb1 has different UUID to sdb2
<6>md: created md2
<6>md: bind
<6>md: running:
<4>raid1 run
<6>raid1: raid set md2 active with 1 out of 2 mirrors
<6>md: considering sdb1 …
<6>md: adding sdb1 …
<6>md: created md1
<6>md: bind
<6>md: running:
<4>raid1 run
<6>raid1: raid set md1 active with 1 out of 2 mirrors
<6>md: … autorun DONE.
<6>kjournald starting. Commit interval 5 seconds
<6>EXT3 FS on md1, internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
<4>VFS: Mounted root (ext3 filesystem).

What i need is:
1) make /sda4 partition accessible
2) set raid to Linear

Can you please give me advices?

Re: Recovering Original FW - Tested

GovR 1201404882|%e %b %Y, %H:%M %Z|agohover

why does no1 reply with help regarding dual drive mybooks??? just like the guy above me, the same happend to me but using a 1tb world edition mybook.

Re: Recovering Original FW - Tested

Maz 1202006826|%e %b %Y, %H:%M %Z|agohover

Can this process be done in windows and if so how can i log into the drive

Re: Recovering Original FW - Tested

bewigged 1202125692|%e %b %Y, %H:%M %Z|agohover

I would like an answer to this too - I have a dual drive mybook, and am about to start - would like to avoid the problem if I can!

Re: Recovering Original FW - Tested

GovR 1202185080|%e %b %Y, %H:%M %Z|agohover

Better off in downloading Ubuntu, burn to cd, and run it as a LiveCD. Use terminal within Ubuntu. Make sure u login as root though on Ubuntu.

Re: Recovering Original FW - Tested

MacUser 1205949331|%e %b %Y, %H:%M %Z|agohover

Try my procedure given here (MacUser 15 Mar 2008)

Re: Recovering Original FW - Tested

disaster 1202219842|%e %b %Y, %H:%M %Z|agohover

Hi,

PCnity, You saved my life !!! Thx a lot !

For whose who don't have linux on their system, there is an excellent live cd at : http://www.sysresccd.org

I bring up to life my WB with this !

.dis@st3r.

Re: Recovering Original FW - Tested

tammersalem 1212881676|%e %b %Y, %H:%M %Z|agohover

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

kroner 1204125147|%e %b %Y, %H:%M %Z|agohover

For anyone new to this discussion, I can confirm that the recovery procedure is 100% accurate. For anyone who uses Windows and is concerned about files and folders on their mybook then I highly recommend checking out http://www.diskinternals.com/linux-recovery/ It will read and recover linux files from ext2/ext3 partitions. It is freeware dispite a registration popup window stating it is a trial version. I know because I checked with the company who told me to ignore it.

I used the rescue cd noted in the post above and connected my drive using SATA-to-USB cable after the cd loaded and recovered my drive without issue first time!

Kudos to all involved in making the images and working out the easy to follow procedures.

last edited on 1204125424|%e %b %Y, %H:%M %Z|agohover by kroner + show more

Re: Recovering Original FW - Tested

tammersalem 1213137836|%e %b %Y, %H:%M %Z|agohover

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!!!!

last edited on 1213300094|%e %b %Y, %H:%M %Z|agohover by tammersalem + show more

Re: Recovering Original FW - Tested

weikianng 1233484324|%e %b %Y, %H:%M %Z|agohover

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

Mobino 1204205210|%e %b %Y, %H:%M %Z|agohover

I also bought just the enclosure of a Mybook World 2 and purchased 2 250gb drives for it. I have the same problems as Mazec- no option to change raid level and sda4 not accesible. Can anyone create the rescue files for a twin drive model? Anyone?!…

Re: Recovering Original FW - Tested

Mobino 1204331785|%e %b %Y, %H:%M %Z|agohover

Ok, I fixed the sda4 problem from above. My sata drive was third in my system therefore I had to change sda1/2/3 etc to sdc throughout the tutorial. I was also doing this at step 12, replacing md4 with sdc. When I tried replacing md4 with sda (AS THE TUTORIAL SAYS!) it worked! I thought I'd mention this in case anybody else makes that mistake. So I now have a functioning Double disk Mybook World 2 with only one disk in it. I would be sooooo greatful if someone could rip the web based drive manager off of the twin drive version so that I could set up raid. That one drive looks so lonley….Cheers to everybody on here who helped me revive my drive.

last edited on 1204331882|%e %b %Y, %H:%M %Z|agohover by Mobino + show more

Re: Recovering Original FW - Tested

alephsmith 1204332794|%e %b %Y, %H:%M %Z|agohover

I don't know if this would work, but have you tried updating the firmware through the webinterface? You can do that now seeing as you have all the working admin pages from the single disk version.

If it detects that it is a MBW2 it may automatically install the missing files you need.

Re: Recovering Original FW - Tested

Mobino 1204579960|%e %b %Y, %H:%M %Z|agohover

Hi. I updated my firmware succesfully but it didn't change the web manager and give me Raid options. It did make my drive unaccesable so I had to repeat this step in the rescue procedure - /dev/md4 MUST BE REPLACED BY /dev/sda4! Now if I copy anything large the fan kicks into loud mode, the copy freezes and both ring lights flash together just like it did when it finished the firmware update.

last edited on 1204580125|%e %b %Y, %H:%M %Z|agohover by Mobino + show more

Re: Recovering Original FW - Tested

Mobino 1204736130|%e %b %Y, %H:%M %Z|agohover

Ok I got it working again. Had to start from scratch though and lost everything I'd put on it. Doh! Most of it is recoverable. I had to rebuild my itunes library from my ipod. The rest I can download again. My ps3 is turning out to be a pretty good backup. This is turning out to me more hassle than I thought!

Re: Recovering Original FW - Tested

MacUser 1204390765|%e %b %Y, %H:%M %Z|agohover

Rescue procedure don't work with my book word edition II.
I have seen two different files (containing the number of disk), the interface is different and there is a problem with the big disks. The linuxbox file is also different in my case (because I have install some new functionnality ?)
For me, with the given rescue procedure, I have a problem with only one single disk. If I format the disk on ununtu, it has the good size, but after writting more than about 500Gb out of 1Mb, the partition become read only. If I format the disk on the western digital (using ssh), the disk size has only 500Gb.
One of my two disk contain the "original" but broken system. I have, after a lot of time find the solution to make it work. It is near to original one now, I hope. I have used rescue procedure you given on my own bad files but, after corrections, it seems to work now. I have reach the 750Gb today and the interface is good.
I will continue until the 1Tb disk will be full and after that I will try to place the second disk and make the raid 1 on.
Best will be to have original partition data but, if it works on my nas, I will give my current partition data.

Re: Recovering Original FW - Tested

MacUser 1205581913|%e %b %Y, %H:%M %Z|agohover

Recovering procedure for My Book World Edition II
After making some tests, it seems that my MyBookWorldEd2 is alive again in raid 1 mode.
I have find two different files between MyBookWorldEd given rescue procedure and my machine (/etc/default-settings wdg1nc vs wdg2nc and /var/oxsemi/nas.ini system_type=1NC vs system_type=2NC) and probably there is others.
So I give my MyBookWorldEd2 partition data so you can restore your NAS. Passord is original one 123456 and one user (Benoit) having password also 123456 has been added and also an ssh access. The NAS have the ip 192.168.0.20. There is also some few files which are not exactly the same as the original files… sorry. I hope that someone can give original one soon…
I recommand to use Ubunto 6.06 live CD (which support RAID). You don't have to install it on your machine.
Changes on the original procedure (I do not warrenty that the procedure will work on your MyBookWorldEd2, it's just a framework that I hope can help peoples to retreave their NAS).
Step 0: save your data, all data will be lost (sorry !)
Step 1: use sudo su instead of su
Step 2: mkdir rescue2
cd rescue2
Download with your browser with rapidfile: http://rapidshare.com/files/99696765/sdc.tar.html
tar xf sdc.tar
rm sdc.tar
Rename the files (sdc to sda or sdb so you avoid to write to a bad disk !). The names are not exactly the same has to one's given in the MyBookWorldEd procedure.
Step 3,4,5: follow the MyBookWorldEd procedure
Step 6: I have seen that with MyBookWorldEd procedure, I get a file system corrupted. So I have replace this format by the following instructions. I'm not sure that this
is important.
replace the mkfs… by those two steps:
bunzip2 sdc1.img.bz2
dd if=sdc1.img of=/dev/sdc4
Be carefull, your of=/dev/sdc4 should be /dev/sda4. Notice also that we copy partition 1 to the partition 4. This is not a mistake, it's just to be sure to have a
good raid1 file system, well recognize by the NAS.
Step 7: bunzip2 sdc.img.bz2
dd if=sdc.img of=/dev/sdc
or sda, or sdb…
Step 8,9,10,11: follow the MyBookWorldEd procedure (using my given files)
Step 13: mkdir sdc1
mount -t ext3 /dev/sdc1 sdc1
nano sdac/etc/fstab
/dev/md4 MUST BE REPLACED BY /dev/sda4 (not sdc4 : when it will be replaced on the NAS, it will be mounted as sda).
Save it by pressing CTRL + X, Y, ENTER.
Or use any other editor you like… [Nano is quite simple]
IMPORTANT:
nano sdc/etc/mdadm.conf
/dev/md4 MUST BE REPLACED BY /dev/sda4 (not sdc4 : when it will be replaced on the NAS, it will be mounted as sda).
Save it by pressing CTRL + X, Y, ENTER.
umount sda1
DO NOT FORGET THIS!
Step14: Power off the computer and plug the drive to MyBookWorldEd2.
Step15: Restart MyBookWorld with one disk.
Step16: On your remote machine, in linux or mac, in a terminal: (for Windows, use an equivalent)
ssh 02.0.861.291|tioneB#02.0.861.291|tioneB
123456 (for the passord) I hope that you will be connect but I don't know because data are copyed and I don't know how ssh works exactly.
su
umount /dev/sda4
mkfs.ext3 -m 0 /dev/sda4 (not sdc4, we are now on the NAS).
mount /dev/sda4 /share/internal
reboot
exit
exit
Step17: After this, PUBLIC directory on /share/internal will be created automatically (but I don't know if it's immediately or not, try to access with samba or not).
I have try to copy data from the second drive at this step. But unfortunately, it was erased and I don't know why. You can try some thing here to avoid this
problem, there is probably a solution. (check step 19 for ideas).
Step18: Make step 1 and 3 for the second drive. I was in raid so I have tryed to copy the data of the second disk.
Step19: Following ideas: mount /dev/sda4 /share/internal as written in the procedure (I'm not sure I have do it).
Maybe try to umount /dev/sda4, and change /etc/fstab : replace /dev/sda4 to /dev/md4 !!!!!!!!!! (see why later).
Step20: Stop you NAS (you can use the NAS button or halt it by unix command in ssh) and place the second disk in the NAS.
Step21: Restart the NAS.
Step22: In a browser type http://192.168.0.20/
Click on Drive management
Name: admin
Password: 123456
Click on Change drive type.
If Secure volume (RAID-1) is not selected, you have a problem. Verify step 13, mdadm.conf is probably not correct.
Click on Cancel
Click on Format New Internal Drive
Then format the drive by clicking on the corresponding button.
Step23: Please wait until the drive has finish formatting and synchronising are done. (If format is refused, it is probably because you are in ssh).
It takes hours (maybe 6, or more if you have a 2*1TB).
Step24: ssh 02.0.861.291|tioneB#02.0.861.291|tioneB
123456
su
nano /etc/fstab
/dev/sda4 MUST BE REPLACED BY /dev/md4 (if it has not been already done by the NAS).
Save it by pressing CTRL + X, Y, ENTER.
Or use any other editor you like… [Nano is quite simple]
IMPORTANT:
nano /etc/mdadm.conf
/dev/sda4 MUST BE REPLACED BY /dev/md4 (if it has not been already done by the NAS).
Save it by pressing CTRL + X, Y, ENTER.
mount /dev/md4 /share/internal (after some times (or a reboot or something like that) PUBLIC directory will be added by the NAS.
reboot
exit
exit
Step25: Now the MyBookWorldEd2 should be full functionnal. I have try to write some data on the RAID, remove one disk, write some bad data on it (using step 1 and 3
so the drive will be recognize as bad). All data has been restored. It seems to work. If you have time, before using step 1 and 3, write some other data in
PUBLIC directory to check better if it's work, I have not do it. (and I can't do it anymore, I have already a lot of data important on the disks).
You can now remove Benoit user and create your and, more important, change the two passwords.
You can also now change drive type to Large Single Volume (Linear) if you prefer, it will probably work.
I hope I have not forget something, and that this procedure will help to retreave you NAS.
Thanks to say me if it works or not and correct the procedure if needed.

Re: Recovering Original FW - Tested

kroner 1205502991|%e %b %Y, %H:%M %Z|agohover

Just a suggestion, as I have had some issues with my 500GB box and will be recovering it once again !!

When I have done the recovery before, as well as changing /dev/md4 > /dev/sda4 as described, I also edited the post_network_start.sh script and disabled mionet BEFORE I shutdown and connected the drive back into the enclosure. This ensured that I was able to do the ssh hack without errors about the drive being in use. What I was proposing is for the rescue images to be updated to include all these basic but essential bits already setup ? That way if people do have to rescue their book then once the procedure is finished they can immediately log in via ssh with a default root password of 'rescue' or something and start installing apps etc straight away instead of having to redo the whole martin hinner hack etc, etc.

Good idea or bad idea?

Re: Recovering Original FW - Tested

Z80 1205506745|%e %b %Y, %H:%M %Z|agohover

Hi everybody,
thank god I didn't brick my device yet, but just in case, I have some questions about a two-disk device.
I am proficient enough with unix to see that the procedure which is described here restores an MBW with one disk, while changing the mount of the last partition from RAID to plain ext3 file system (the edition of /etc/fstab does that).
But did anyone follow this procedure to restore a two-disk device with any success? Since the last partition of the rescued disk is no longer mounted as RAID, I doubt that the RAID will be restored automatically.
Obviously, I don't want to test it myself, as long as my device is OK. But can I sleep well in the knowledge that this procedure will work for me, once the gods struck?
Or is it possible to restore the first three partitions of both disks, clear /etc/fstab to not mount the fourth partition at all, install the disks into the device and boot the device to do all the RAID management inside the MBW box by hand afterwards?
Z80

last edited on 1205506858|%e %b %Y, %H:%M %Z|agohover by Z80 + show more

Re: Recovering Original FW - Tested

MacUser 1205949923|%e %b %Y, %H:%M %Z|agohover

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

Z80 1205873608|%e %b %Y, %H:%M %Z|agohover

@kroner:
In my opinon, a very good idea.
Perhaps someone could also post images with updated firmware and anabled ssh and reinstalled gcc and nfs?
What do you think?
Z80

Re: Recovering Original FW - Tested

chelrob 1205897695|%e %b %Y, %H:%M %Z|agohover

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.

Re: Recovering Original FW - Tested

lefgrter 1207827566|%e %b %Y, %H:%M %Z|agohover

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

polanders 1207856944|%e %b %Y, %H:%M %Z|agohover

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

Xice 1208456102|%e %b %Y, %H:%M %Z|agohover

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

Xice 1208456857|%e %b %Y, %H:%M %Z|agohover

I have my pc running with windows XP

Re: Recovering Original FW - Tested

Xice 1208458037|%e %b %Y, %H:%M %Z|agohover

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

MacUser 1208596038|%e %b %Y, %H:%M %Z|agohover

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

Xice 1211830578|%e %b %Y, %H:%M %Z|agohover

cd ~
su root [enter root passwd]

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

Re: Recovering Original FW - Tested

GuiGou 1208972647|%e %b %Y, %H:%M %Z|agohover

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

MacUser 1209208123|%e %b %Y, %H:%M %Z|agohover

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

GuiGou 1209231669|%e %b %Y, %H:%M %Z|agohover

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

smccloud 1210769431|%e %b %Y, %H:%M %Z|agohover

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

Xice 1212689623|%e %b %Y, %H:%M %Z|agohover

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

Xice 1212690006|%e %b %Y, %H:%M %Z|agohover

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

Re: Recovering Original FW - Tested

MacUser 1212914651|%e %b %Y, %H:%M %Z|agohover

~ 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 by the Saint

The_Saint 1213964095|%e %b %Y, %H:%M %Z|agohover

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 by the Saint on 500Gb

The_Saint 1214147124|%e %b %Y, %H:%M %Z|agohover

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

last edited on 1214147253|%e %b %Y, %H:%M %Z|agohover by The_Saint + show more

Re: Recovering Original FW - Tested

amorsent 1214180809|%e %b %Y, %H:%M %Z|agohover

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 - MAC changed how to restore ??

The_Saint 1214193817|%e %b %Y, %H:%M %Z|agohover

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 - MAC changed how to restore ??

amorsent 1214241074|%e %b %Y, %H:%M %Z|agohover

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 ??

amorsent 1214411826|%e %b %Y, %H:%M %Z|agohover

anyone?

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

The_Saint 1214416064|%e %b %Y, %H:%M %Z|agohover

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 - Capacity leds do not work anymore,WHY ??

kevku 1214499627|%e %b %Y, %H:%M %Z|agohover

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

---

30-day pro trial.
2x WD Caviar SE WD5000AAJS RAID0 MBWEII
don't click

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

The_Saint 1214510303|%e %b %Y, %H:%M %Z|agohover

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 Fake Firmware - Without support from WD or NOONE HERE !Boot your Computer without Mainboard ! It works !

kevku 1214512159|%e %b %Y, %H:%M %Z|agohover

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.

---

30-day pro trial.
2x WD Caviar SE WD5000AAJS RAID0 MBWEII
don't click

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

amorsent 1214537686|%e %b %Y, %H:%M %Z|agohover

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 Firmware

kevku 1214549479|%e %b %Y, %H:%M %Z|agohover

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)

---

30-day pro trial.
2x WD Caviar SE WD5000AAJS RAID0 MBWEII
don't click

last edited on 1214549673|%e %b %Y, %H:%M %Z|agohover by kevku + show more

Re: Recovering Firmware

amorsent 1214555530|%e %b %Y, %H:%M %Z|agohover

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,sorrrry kevku !

The_Saint 1214558481|%e %b %Y, %H:%M %Z|agohover

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

last edited on 1214558713|%e %b %Y, %H:%M %Z|agohover by The_Saint + show more

Re: Recovering Firmware,sorrrry kevku !

stark 1214560072|%e %b %Y, %H:%M %Z|agohover

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

---

2 X MBWE 500gb
LED Display

Re: Recovering Firmware,sorrrry kevku !

The_Saint 1214565050|%e %b %Y, %H:%M %Z|agohover

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

kevku 1214567651|%e %b %Y, %H:%M %Z|agohover

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).

---

30-day pro trial.
2x WD Caviar SE WD5000AAJS RAID0 MBWEII
don't click

last edited on 1214567806|%e %b %Y, %H:%M %Z|agohover by kevku + show more

Re: Recovering Firmware

The_Saint 1214570664|%e %b %Y, %H:%M %Z|agohover

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

last edited on 1214571239|%e %b %Y, %H:%M %Z|agohover by The_Saint + show more

Re: Recovering Original FW - Tested

827879 1215543956|%e %b %Y, %H:%M %Z|agohover

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 Original FW - Tested

dan7 1217707472|%e %b %Y, %H:%M %Z|agohover

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

jeffo 1228227221|%e %b %Y, %H:%M %Z|agohover

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

jeffo 1228244280|%e %b %Y, %H:%M %Z|agohover

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

jeffo 1228294796|%e %b %Y, %H:%M %Z|agohover

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

Strifey 1228966880|%e %b %Y, %H:%M %Z|agohover

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.

I think I am in big trouble

xlight63 1232014694|%e %b %Y, %H:%M %Z|agohover

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: I think I am in big trouble

TeinturMan 1232043317|%e %b %Y, %H:%M %Z|agohover

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.

Re: I think I am in big trouble

xlight63 1232142365|%e %b %Y, %H:%M %Z|agohover

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

alephsmith 1232147112|%e %b %Y, %H:%M %Z|agohover

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

xlight63 1232152048|%e %b %Y, %H:%M %Z|agohover

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: Recovering Original FW - Tested

hmfish 1233203849|%e %b %Y, %H:%M %Z|agohover

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…

last edited on 1233248040|%e %b %Y, %H:%M %Z|agohover by hmfish + show more

Re: Recovering Original FW - Tested

hmfish 1233286389|%e %b %Y, %H:%M %Z|agohover

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

naween18 1233497401|%e %b %Y, %H:%M %Z|agohover

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

zander7990 1236144460|%e %b %Y, %H:%M %Z|agohover

hi

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

nugga 1244568862|%e %b %Y, %H:%M %Z|agohover

Hello.

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

Re: Recovering Original FW - Tested

polve 1245418548|%e %b %Y, %H:%M %Z|agohover

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