I bought this WD NAS over ten years ago and it has ran fine up until about six weeks ago
when it died. Windows 7 just no longer sees the mapped out drives in My Computer. There
were no sounds coming from the spinning drives just nothing. So I decided it was a WD
enclosure problem and not a hard drive problem. So I pulled the hard drives from their
enclosure and connected one of them to a “USB to SATA Adapter”, then plugged it into my
computer. The computer made a sound of a USB device being plugged in, but nothing
showed up in My Computer window. My conclusion is that I would have to look elsewhere
for my answer if I wanted my data back.

So I started my research on the internet, and found there are a lot of people with the
same problem and no support or fix from WD to correct it. I found that some people had
success with Linux. I have an older DELL laptop laying around so I loaded Linux Mint 20
“Ulyana” – Cinnamon (64-bit) on to this older DELL. I can at least see the drive now in
the My Computer window but can’t get into it. When I try, I get the error message “Unable
to mount location”.

In the past six weeks I have read and tried countless internet posts, most of them have
been Terminal Window stuff without any success. I know there is a solution out there, I
just need someone’s help to find it.

If you are willing to take on this challenge, you will find that I’m highly motivated to
retrieve my data. I promise to check this forum every day and try your suggested key
strokes and post results.

Shown below are two looks at both drives “Disks” & "sudo fdisk -l". I’m hoping that if
someone is willing to help me this will be useful to you.

Thank You in Advance
TSQMAN-1

Information from Linux Mint Disks Command -Disk Number 1

Model: WDC WD20EADS-00R6B0 (01.00A01)
Size: 2.0 TB (2,000,398,934,016 bytes)
Partitioning: Master Boot Record
Serial Number: WD-WCAVY2497662
Assessment: Disk is OK, one bad sector

Information on Partition 4 (It's the Largest and I Believe the Data is Here)

Size: 2.0 TB (1,997,081,543,168 bytes)
Device: /dev/sdb4
UUID: 8f7e3052-dbae-d664-7273-ee3ce6483360
Partition Type: Linux RAID auto
ConTents: Linux RAID Member (version 0.90.0)

Information from Terminal Window Command "sudo fdisk -l" -Disk Number 1

Disk /dev/sdc: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: EADS-00R6B0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0001cf00

Device Boot Start End Sectors Size Id Type
/dev/sdc1 64320 3984191 3919872 1.9G fd Linux raid autodetect
/dev/sdc2 3984192 4498175 513984 251M fd Linux raid autodetect
/dev/sdc3 4498176 6474175 1976000 964.9M fd Linux raid autodetect
/dev/sdc4 6474176 3907024064 3900549889 1.8T fd Linux raid autodetect

Information from Linux Mint Disks Command -Disk Number 2
Data is exactly the same as disk number 1 except what’s shown below.

Serial Number: WD-WCAVY2497155

Information on Partition 4 (It's the Largest and I Believe the Data is Here)

UUID: 3066fbfa-03fd-8233-4217-cbc4f1db6bbb

Information from Terminal Window Command "sudo fdisk -l" -Disk Number 2
Data is exactly the same as disk number 1 except what’s shown below.

Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors

Device Boot Start End Sectors Size Id Type
/dev/sdb1 64320 3984191 3919872 1.9G fd Linux raid autodetect
/dev/sdb2 3984192 4498175 513984 251M fd Linux raid autodetect
/dev/sdb3 4498176 6474175 1976000 964.9M fd Linux raid autodetect
/dev/sdb4 6474176 3907024064 3900549889 1.8T fd Linux raid autodetect

If you would like to read more background of my problem I'm facing please look in section 3 for "TSQMAN-1" on this forum.

I have tested your posting and the results are shown below do you anymore suggestions?

QUESTION for you: It looks like it had a problem with STEP #5 & STEP #7, where does the "/dev/md4" come from?

Thank You in Advance
TSQMAN-1

TITLE: How to Recover Data From WD My Book World Edition NAS Device
POSTED BY: netvizier 19 Sep 2008

STEP 1:---------------—
KEYED IN: sudo fdisk –l
REPLY MESSAGE:

Disk /dev/sdd: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: EADS-00R6B0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0001cf00

Device Boot Start End Sectors Size Id Type
/dev/sdd1 64320 3984191 3919872 1.9G fd Linux raid autodetect
/dev/sdd2 3984192 4498175 513984 251M fd Linux raid autodetect
/dev/sdd3 4498176 6474175 1976000 964.9M fd Linux raid autodetect
/dev/sdd4 6474176 3907024064 3900549889 1.8T fd Linux raid autodetect

STEP 2:---------------—
KEYED IN: sudo modprobe md
REPLY MESSAGE:

No Reply

STEP 3:---------------—
KEYED IN: sudo mknod /dev/md4 b 9 4
REPLY MESSAGE:

No Reply

STEP 4:---------------—
KEYED IN: sudo apt-get install mdadm
REPLY MESSAGE:

Reading package lists… Done
Building dependency tree
Reading state information… Done
mdadm is already the newest version (4.1-5ubuntu1.2).
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.

STEP 5:---------------—
KEYED IN: sudo mdadm —assemble /dev/md4 /dev/sdd4
REPLY MESSAGE:

mdadm: Found some drive for an array that is already active: /dev/md2
mdadm: giving up.

STEP 6:---------------—
KEYED IN: sudo mkdir /media/abc
REPLY MESSAGE:

No Reply

STEP 7:---------------—
KEYED IN: sudo mount /dev/md4 /media/abc
REPLY MESSAGE:

mount: /media/abc: can't read superblock on /dev/md4.

STEP 8:---------------—
KEYED IN: sudo chmod -R 777 /media/abc
REPLY MESSAGE:

No Reply

$ sudo modprobe md $ sudo mknod /dev/md4 b 9 4 $ sudo apt-get install mdadm $ sudo mdadm --assemble /dev/md4 /dev/sdb4 $ sudo mkdir /media/xyz $ sudo mount /dev/md4 /media/xyz $ sudo chmod -R 777 /media/xyz

cat /proc/mdstat

Sadly it came out that even thought my device should be available on /dev/md2, it could not be mounted.

This article came with a lot of help:
(sadly I cannot paste a link so please use google and search for "mdadm raid doesn't mount" and check an article on unix.stackexchange)

Using e2fsck showed that my superblock was damaged and that was why I could not mount the drive.
Finally make2fs showed backuped superblock which I was able to bring back using e2fsck.

After that, mounting /dev/md2 was possible.

Free Download a trial version and recover lost photo with few simple steps:

Step 1: Launch the program
Step 2: Select Media, File Format and Drive Region For Recovery
Step 3: Preview the scanning result
Step 4: Selectively recovery
Step 5: Select the location to save the files

I have read this and try follow every commands to recover my data from my dead drive.

I insert the comands:

sudo mknod /dev/md4 b 9 4
sudo apt-get install mdadm
but when try this one I got error:
sudo mdadm —assemble /dev/md4 /dev/sdb4

mdadm: cannot open device /dev/sdb4: No such file or directory
mdadm: /dev/sdb4 has no superblock - assembly aborted

I can I pass this ?

I'm using a distribution of ubuntu for this.

I never use linux.

thx for help

Your entry re using Linux to access a "dead" My Book World Edition was a lifesaver - thank you so much.

Your instructions didnt quite work for me, as my drive WD My Book World Edition 500GB (Blue Rings) would not mount ( I got the same load of b*ll*cks that others here have had ie wrong fs, bad option etc etc) - but the following did work:

Using Windows (in my case Win8) download Partition Assistant from here - w w w [dot] disk-partition [dot] com - its free! (Apparently I'm too low level to post links!!!)

Run the PA, identify your disc and then run the conversion utility "Convert GPT to MBR"

After it's has finished - about 30sec - go back into Linux and then run the mkdir and mount command lines as per your post.

Whoohoo - I could now see my files and copied them across to another disc. Problem solved :-)!

After so much searching of support pages and forum posts (including this one), and being a brand new total novice to Linux I cant believe how simple it all turned out to be - thank you so much again.

sdc1 had bad primary superblocks
as did sdc2 and sdc3 so the drive was unable to mount

using :
sudo xfs_repair -L /dev/sdc4

followed by:

$ sudo mknod /dev/md4 b 9 4
$ sudo apt-get install mdadm
$ sudo mdadm —assemble /dev/md4 /dev/sdb4
$ sudo mkdir /media/xyz
$ sudo mount /dev/md4 /media/xyz

I was able to retrive all data by browsing to /media/xyz.

I have a MBWE 4tb. It's got 2 drives and I don't recall what type of raid I had it setup to run. May have been stripe, IDK. I do know that one day after a power failure I could no longer access the shared folders (could access the usb drive attached). It still allowed for ssh and access via the webui, but no shared folders could be accessed even though I could see em. I came here looking for a solution, and after going through all the different linux instructions I noticed a link to some software another user suggested. I tried his suggestion but no dice. That didn't stop me, so i started googling recovery software and have found just the trick from the same company he had suggested.

The software I used is UFS Explorer Professional Recovery v5.6 (search for it on TPB or KAT)

Equipment needed:
I bought a dual sata dock, anyone will probably work, but i bought mine off ebay for $30 it's made by SIIG. Also picked me up a 4tb USB drive from newegg for $149, smokin deal but if you don't need all the data off your mybook you could use any usb drive you got laying around with enough space to hold the recovered data.

Installed the software to my pc, removed drives from MBWE and inserted into dock, hooked up USB drive, ran software and was able to see the old array listed as "MyBookWorld" and was able to extract all my folders onto the usb drive.

Easy as pie, give it a try. I'm backing up all my files right now. Will factory reset the MBE once i got all my data back and will be sure to keep a backup of everything important on a separate usb drive since there is a usb port right on the MBWE and I no longer trust this piece of crap NAS.

Probably the hardest part is getting the drive out of WD enclosure and into your computer. Once you have burned the ISO on to a DVD- and rebooted the computer up pops Zorin- a very cool looking OS.

Click the little arrow in the lower left- select accessories and then terminal. Enter the commands as Zaaphod listed them - and you will have your drive up and available.

I want to point out a shortcut here- if you are connected to a local network the network will show up when you boot from the DVD in to Zorin. Since you are booting from your DVD you don't really need the computer's normal operating system hard drive. You can temporarily take it out and put in your WD drive- boot from the DVD- mount the WD driver and copy over the network to an available drive- saves the hassel of finding a SATA cable and extra power connector unless they are handy.

This worked like a charm- thanks to all.

Kirk

I have installed Ubuntu and can boot into it with Wubi on my laptop, and I have the WD HD in an external USB SATA dock.

In Windows 7, the laptop sees the dock and the drive but since it does not see a windows partition, I cannot access it. When I boot into Wubi, I cannot see the drive though as it appears I cannot access USB.

How do I do that?

I ended up in the same situation as you today - and after a lot of experimenting and "well, I can't get to the data anyway so I may as well try some radical actions" I performed the following which has now allowed me to get to my drive. It assumes you never want to add it back into the My Book cradle again as you blat the superblock although there's probably a way of recreating that somehow.

Stop the raid array a) sudo mdadm --stop /dev/md4 Zero the raid superblock - this was the bit that gave me access back to it! b) sudo mdadm --zero-superblock /dev/sde4 Apparently last time I used it (when it failed) it wasn't a clean shutdown, so had to run the filesystem check to clean it c) sudo fsck /dev/sde4 Finally mount the file system d) sudo mount -t ext3 /dev/sde4 /mnt/mybook

Then copied all data… and breathed a big sigh of relief. Western Digital, never again….

Hope this helps and it isn't too late.

1) sudo umount /media/xyz
2) sudo fsck /dev/sdb4

My english is very but I try to explain you my problem…

I have a MybookWorld edition II in JBOD mode. After a problem to access to my data in the volume on the disk 1 (the data of the volume on the disk 2 were OK), I reconfigure the raid in JBOD mode. Now I access to the volume on the disk 1 (the volume is empty, it's OK) but the data in the volume on the disk 2 are deleted. How am I recover my data in the volume of the disk 2?

Thanks for you help.

Timal

-I have run ddrescue and created an image
-I have run e2fsck on the image and the original drive and they both fail with a bad superblock when trying to repair or to mount.
-I have researched how to run e3fsck with an alternative superblock, but none of the 10 or more Superblocks are able to mount.
-It appears that the partition is completely gone when I run the testdisk tool on the drive. It does not see the 4th partition at all.
?I am wondering if I could manually add the partition into the table if I had the correct parameters…
?Would every drive of my model have the same partition parameters? I can see the first three partitions without issue and they are mountable. It appears that there is a read error on one sector of my drive.
-I tried using GRC SpinRite on the drive, but it wont run on the damaged partition. It sees the partition, but won't perform any repairs.
-I have easily spent 48 solid hours on this so far in research. I am needing some help and would be happy to provide screenshots if necessary.
Thanks in advance,
-Selfdestruct

mount: wrong fs type, bad option, bad superblock on /dev/md4,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

I got the same message and know I feel stock. Please help…

thank you.

I used USB2SATA convertor but before this,i had already tried the drive by plugging directly to sata

imageshack.us/photo/my-images/545/screenshothw.png/

1. sudo su
2. mkdir /media/xyz
3. mount -t xfs /dev/sdb4 /media/xyz

I woke up this morning, and ran the commands as i did several times yesterday, and my public/shared music folder is missing 99% of the files that were there last night?! I have no idea what happened or where they went?

What can I do besides start a new music collection?

Help Please!
Thanks
Walt

I'm trying to recover data from my single drive 1TB MBWE (white light). I'm stuck at step no. 10.

When I go "mount -t ext3 /dev/sdb4 /media/xyz" I get the following error:
mount: wrong fs type, bad option, bad superblock on /dev/sdb4,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

"dmesg | tail" shows me:
[ 15.184757] [drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0
[ 15.986859] [drm] nouveau 0000:01:00.0: Allocating FIFO number 1
[ 15.988379] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 1
[ 16.353379] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=0
[ 16.705944] tg3 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex
[ 16.705951] tg3 0000:02:00.0: eth0: Flow control is off for TX and off for RX
[ 16.706102] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 19.125673] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=0
[ 27.600012] eth0: no IPv6 routers present
[ 373.478031] EXT3-fs (sdb4): error: can't find ext3 filesystem on dev sdb4.

I guess that last line is the punch line :) Why can't it find the ext3 filesystem on my drive? How can I still recover my files from the drive?

Thanks in advance,
urig

PS - Here's what "fdisk -l" gives me, just in case:

//Disk /dev/sda: 80.0 GB, 80000000000 bytes
255 heads, 63 sectors/track, 9726 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x9cce9cce

Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 4265 34147382 7 HPFS/NTFS
/dev/sda3 4265 9726 43872257 5 Extended
/dev/sda5 4265 9497 42029056 83 Linux
/dev/sda6 9497 9726 1842176 82 Linux swap / Solaris

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0001cf00

Device Boot Start End Blocks Id System
/dev/sdb1 5 248 1959930 fd Linux raid autodetect
/dev/sdb2 249 280 257040 fd Linux raid autodetect
/dev/sdb3 281 403 987997+ fd Linux raid autodetect
/dev/sdb4 404 121601 973522935 fd Linux raid autodetect//

I have the western digital my world book edition 2 4tb model set at raid0
I have ubuntu running off a cd on my laptop
I have both WD drives (drive A & B) connected to a sata to usb enclosure to my laptop

when I run fdisk -l & I get the following:

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0001cf00

Device Boot Start End Blocks Id System
/dev/sdb1 5 248 1959930 fd Linux raid autodetect
/dev/sdb2 249 280 257040 fd Linux raid autodetect
/dev/sdb3 281 403 987997+ fd Linux raid autodetect
/dev/sdb4 404 243201 1950274935 fd Linux raid autodetect

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0001cf00

Device Boot Start End Blocks Id System
/dev/sdc1 5 248 1959930 fd Linux raid autodetect
/dev/sdc2 249 280 257040 fd Linux raid autodetect
/dev/sdc3 281 403 987997+ fd Linux raid autodetect
/dev/sdc4 404 243201 1950274935 fd Linux raid autodetect

while im a su, I type the following:

mknod /dev/md4 b 9 4
mdadm —assemble /dev/md4 —force /dev/sdb4 /dev/sdc4

at this point, I can see the raid 0 assembled in computer, it shows the 4tb and states 0.0 KB RAID-0 Array: 4.0 TB Filesystem
If i try to right click on the raid icon, it gives me an option to mount it and fails:error mounting: mount: /dev/md4: can't read superblock.

So at this point I can assemble the raid but I can't mount it… anyone can help me at this point would helpfull

I would just format the partitions but I have my wedding photos on it & they can't be replaced

I have Kroll data recovery software for Windows and am familiar with using it but I need to recover deleted files from my 2TB (one disk) Mybook WE. The drive mounts fine on the network but I can't mount it directly in XP or Win7. Is there any Ubuntu software I could use to recover the files after I boot into it using your instructions?

Thanks,

Mostiky

It's strange that I can access one out of five folders…could it be the bad sectors are in that folder area?

I get the feeling these drives are toast.

the initial modprobe command comes back with a FATAL error.

root@ubuntu:/# modprobe md
FATAL: Module md not found.

should I proceed with the other commands?

you sure that your disks are ok?
you need to assemble the RAID0 before mounting

modprobe md
mknod /dev/md4 b 9 4
mdadm —assemble /dev/md4 —force /dev/sda4 /dev/sdc4
then mount /dev/md4

also make a new thread or make a new post at the end of this one, it's hard to find you post inside here

modprobe md mknod /dev/md4 b 9 4 mdadm --assemble /dev/md4 --force /dev/sda4 /dev/sdc4

then mount /dev/md4

also make a new thread or make a new post at the end of this one, it's hard to find you post inside here

I am trying to recover files off of a MBWE I w/ two 500GB drives in RAID0. My WD drives show up as sda and sdc (sdb is my flash drive).

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00007c00

Device Boot Start End Blocks Id System
/dev/sda1 4 369 2939895 fd Linux raid autodetect
/dev/sda2 370 382 104422+ fd Linux raid autodetect
/dev/sda3 383 505 987997+ fd Linux raid autodetect
/dev/sda4 506 60801 484327620 fd Linux raid autodetect

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00007c00

Device Boot Start End Blocks Id System
/dev/sdc1 4 369 2939895 fd Linux raid autodetect
/dev/sdc2 370 382 104422+ fd Linux raid autodetect
/dev/sdc3 383 505 987997+ fd Linux raid autodetect
/dev/sdc4 506 60801 484327620 fd Linux raid autodetect

Using the "mount -t ext3 /dev/sda4 /media/xyz" command I am able to see certain folders. Interesting though I can only see the BACKUP folder, not any of the others (VIDEO, PICTURES, AUDIO, PUBLIC).

root@ubuntu:/# mount -t ext3 /dev/sda4 /media/xyz
root@ubuntu:/# chmod -R 777 /media/xyz
chmod: cannot access ‘/media/xyz/BACKUP/Personal/My Documents/Cisco(FTP). pdf.pdf’: No such file or directory
chmod: cannot access ‘/media/xyz/VIDEO’: Input/output error
chmod: cannot access ‘/media/xyz/PICTURES’: Input/output error
chmod: cannot access ‘/media/xyz/AUDIO’: Input/output error
chmod: cannot access ‘/media/xyz/PUBLIC’: Input/output error

I tried the mdadm method as well but was unsuccessful.

root@ubuntu:/# mdadm -Cv /dev/md4 -l0 -n2 -c64 /dev/sda4 /dev/sdc4
mdadm: /dev/sda4 appears to contain an ext2fs file system
size=968655104K mtime=Mon Nov 1 07:06:32 2010
mdadm: /dev/sda4 appears to be part of a raid array:
level=linear devices=2 ctime=Tue Mar 27 07:53:30 2007
mdadm: /dev/sdc4 appears to be part of a raid array:
level=linear devices=2 ctime=Tue Mar 27 07:53:30 2007
Continue creating array? y
mdadm: array /dev/md4 started.
root@ubuntu:/# mount -t ext3 /dev/md4 /media/xyz
mount: wrong fs type, bad option, bad superblock on /dev/md4,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Any suggestions of what I should try next? I can see some of the files when I mount the sda4 partition, but I need to see all of them.

#mdadm —stop /dev/md4
mdadm: stopped /dev/md4
#mdadm —assemble /dev/md4 /dev/sdb1
mdadm: /dev/md4 has been started with 1 drive (out of 2).
#mount /dev/md4 /media/nas

I guess the system is on a different partition (sdb2 I think), how do I change the setup so that I can access the system partition instead?

#mdadm —assemble /dev/md4 /dev/sdb2
mdadm: device /dev/md4 already active - cannot assemble it

Accessed the files and copying while I write.

FYI, I have a MyWorldBook with 2x 500GB drives, setup as a mirror raid. One day, the unit just wouldn't start up. Took out one of the drives and used a SATA - USB adapter to plug into my Windows machine. Found out that I could see the partitions, but of course couldn't mount nor access them in Windows.

Did a search on how to recover data and found this site, the instructions and your post, & the rest is history.

Thanks again.

root@live:/home/live# dmesg | tail
[ 676.150057] ata3: nv: skipping hardreset on occupied port
[ 681.210034} ata3: srst failed (errno=-16)
[ 681.210044] ata3: reset failed, giving up
[ 681.210050] ata3.00: disabled
[ 681.210082] ata3: EH complete
[ 681.210120] sd 2:0:0:0: [sdb] unhandled error code
[ 681.210125] sd 2:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=Driver_OK
[ 681.210132] sd 2:0:0:0: [sdb] CDB: Read(10): 28 00 00 7b ca e1 00 00 08 00
[ 681.210152] end_request: I/O error, dev sdb, sector 8112865
[ 681.210187] EXT3-fs: can't read group descriptor 4

root@live:/home/live#

any thoughts on how to recover this data?

live@live:-$ sudo su
root@live:/home/live# mkdir /media/xyz
root@live: /home/live# mount -t ext3 /dev/sdb4 /media/xyz
mount: wrong fs type, bad option, bad superblock on /dev/sdb4,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Any ideas?

second of all… $500 is a rediculous amount to pay to recover data from a perfectly good $149 drive… All nova1981 needed was correct instructions and he could easily do it himself. Western Digital My Book World Edditions have problems with their electronics, and it is VERY common for them to stop booting correctly, making your data completly inaccessible even though there is absolutly nothing wrong with your actual hard drive. This has happened to 3 out of 3 of the mbwe's that I have owned. Fortunatly the solution is way simpler than everyone is making it out to be, and from reading the entire thread, it seems that what is needed is for someone to explain the procedure in a way that someone who has never seen linux can understand.

I also got the fatal error when trying to run the command Sudo modprobe md but after actually looking up the command.. I discovered that this is only to install the modules into your operating system.. and this is completly un-nessecary on modern linux installations, because the modules needed are already there, and the error is caused because modprobe is NOT there…. but you don't need it.. so just skip that.

another thing everone seems to be not mentioning, is that you need to be a super-user or root-user to do the actual mount, or you just get an error. You all have to realize.. most people are reading this page because their Western Digital My Wold Book Edition NAS has failed and they are desperatly trying to recover their data from the perfectly good drive inside.. Most, like myself have never messed with linux, and it never even occurs to them that linux is CASE SENSITIVE… so you must type commands exactly.

Here is how I was able to recover 100% of my data from my failed My World Book Edition NAS.

1. Download a Linux operating system. I used Zorin http://zorin-os.webs.com use this link to download http://s5.histats.com/stats/r.php?715549&100&5501&urlr=&ibiblio.org/pub/linux/distributions/zorin/3/zorin-os-3-core-64.iso You can use other flavors of linux, but one based on ubuntu would probably make the instructions easier to follow. My reason for picking zorin was that there were only 3 download choices, while some others had tons and tons, and it was very confusing what I would need to get the job done… that, and well it does look cool! I may keep it around and play with it.

2. Burn the image to a DVD (not a CD, it won't fit) I could't get my dvd software to work so I downloaded the free trial program at http://www.nch.com.au/burn/burnsetup.exe it worked perfectly fine and was very easy to use. I just selected the option to write image to DVD and selected the image file I downloaded, and away it went.

3. Remove the hard drive from the My Book World Editon device I found a video here:
http://www.youtube.com/watch?v=6FlySnyJ0CQ there are lots of other sites that tell you how to get the case open, including this one.

install the drive in your computer on one of the SATA ports.. It would be a good idea to have a second drive also installed large enough to hold your data on another port. I installed a 1.5TB drive on one port and the 1TB drive from the failed My World Book Edition NAS on the another port, and of course the DVD drive needs to be plugged in as well. if you don't have enough sata cable you could install linux on the new drive, then remove the dvd drive and use that port for the other drive… some of your prompts will be slightly different, but other than that everything should work fine.

4. Boot the computer off the DVD. You do not need to install the new operating system, you can do everything you need to do running right off the DVD.

5. When it boots from dvd you should get a menu, choose the option to start the Live DVD This will start up the operating system.

6. once you are in, open the terminal program. You can find it by pressing the button in the lower left corner (similar to the windows start button) then going to Accessories then Terminal This will start something like a command prompt. but the prompt will be something like

live@live: -$

the $ is part of the prompt, you don't type the $ in the commands

7. You need to figure out which drive is which, type the following command and read the report

sudo fdisk -l
NOTE.. that is a LOWER CASE L in the above line… yea it's hard to tell what it is.

this will list the drives and their partitions. You will see something like:
device boot start end blocks id system
/dev/sda1 * 1 182402 1465137695+ 7 HPFS/NTFS

This is telling me my drive at loaction /dev/sda1 is a HPFS/NTFS drive.. one that I formatted on Windows XP pro.

device boot start end blocks id system
/dev/sdb1 4 369 2939895 fd Linux raid autodetect
/dev/sdb2 370 382 104422+ fd Linux raid autodetect
/dev/sdb3 383 505 987997+ fd Linux raid autodetect
/dev/sdb4 506 121601 972703620 fd Linux raid autodetect

This is what a My World Book Edition 1TB hard drive looks like. /dev/sdb4 is the partition we want to mount, you can see by it's huge size, it's where our data is all at. I will use /dev/sdb4 in my example, but you will have to subsitute wherever your drive is.

8. To mount the drive, we must be a root-user or super-user, so type the following command:

sudo su

the prompt will change from something like live@live:-$ to root@live:/home/live#

9. now create the directory to work with. Type the following:

mkdir /media/xyz

this reponse to this should be to just get a new prompt.

10. now to mount the drive. Type the following command:

mount -t ext3 /dev/sdb4 /media/xyz

don't forget to replace /dev/sdb4 with whatever your drive partition was.

This should mount the drive and you should notice a new hard drive icon suddenly appears on your desktop named xyz if you open it, there are all your files! If you don't see it on your desktop, there should be a new drive in your computer browser named xyz. now all you need to do is copy the entire drive to your other drive and you have recovered everything! when you are done you can just re-format the drive to something more useful and use it however you wish.. will probably work fine for many years to come as there was nothing ever wrong with the drive itself.

I did not need to do anything further than this.. I just highlighted everything and copied it, then selected my new drive and pasted it in there.. about 9 hours later, it was finished and I had a drive useable in my windows xp computer directly with all my data.

I did not set up any permissions or passwords on my drive, but if you did, I believe you would still need to use the command:

sudo chmod -R 777 /media/xyz

since I did not have any set, I have no way to test that though.

Good luck to everyone!

I unmounted the drive through the media window and re-mounted it using "sudo mount -t ext3 /dev/md4 /media/xyz". I was then able to change the permissions with "sudo chmod -R 777 /media/xyz" and I was then able to access the data.

Thank you very much for this useful information!

I have a WD II , 2 500GB drives with Raid 0, so I have 1 TB of storage. Basically, I wiped a folder located inside /shares/internal.

I have not to say that folder is very, very important… and, after a lot of, do this, do that… I just want to ask simple steps to do this:

I have an Ubuntu linux machine, testdisk, r-linux and a lot of tools that claim to recover linux files, so, I want to connect the two SATA drives from my WD II 1TB , 2 disk edition into my Ubuntu machine and MOUNT the drives so I can see plain and simple the data, and then be able to recover with those tools.

Assume I have all that connected, Ubuntu up, drives there…

HOW DO I MOUNT THE TWO DRIVES ????

just that …that simple task I want to do, I believe me… maybe I am missing something but I can't make it happen.

Hope some one can help with that… THANk YOU in advance!

Cheers!

This guy has a listing to check out your hard drive for 20.00 and if data is recoverable it only costs 500.00

The recovered folders /files are send back on a USB 2.0 external hard drive.

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=120506191215&ssPageName=STRK:MESELX:IT

I'm new at this…
When I type "sudo modprobe md" i get:
"FATAL: Module md not found"
I have an akasa SATA to USB unit.

I'm starting to panic, I have to get some files from the disk…

Please help me!

mount: wrong fs type, bad option, bad superblock on /dev/md4, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so

What i've do it:

#mdadm -Cv /dev/md4 -l0 -n2 -c64 /dev/sdb4 /dev/sdc4 mdadm: /dev/sdb4 appears to be part of a raid array: level=raid1 devices=2 ctime=Thu Feb 26 18:19:49 2009 mdadm: /dev/sdc4 appears to be part of a raid array: level=raid1 devices=2 ctime=Thu Feb 26 18:19:49 2009 Continue creating array? y mdadm: array /dev/md4 started. #mount -t ext3 /dev/md4 /mnt/array/ mount: wrong fs type, bad option, bad superblock on /dev/md4, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so # mdadm --examine /dev/md4 mdadm: No md superblock detected on /dev/md4.

Can anyone help me please? the data in MBWEII it's important!!!

if you configure with RAID 0 than you would need to connect both drive and recreate the metadevice mount point by issuing a command
#mdadm -Cv /dev/md4 -l0 -n2 -c64 /dev/sdb4 /dev/sdc4

hope this helps

After struggling for o few day with this recovery problem also.
got a work around by re creating the RAID with this command
$sudo passwd
this is to change the root password so you can su to change to root
$su
use your newly created root password

search in /dev is there a mount of sdb4

try running
#ls /dev | grep sd

if you can see it on the list
then continue with

#mdadm -Cv /dev/md4 -l1 -n2 -c64 /dev/sdb4 missing
asuming that you have WD Mybook world edition 1

then you can mount the md device using
#mount -t ext3 /dev/md4 </local_mountpoint>
#cd </local mountpoint>

hope this helps.

New problem though…

The command:

$ sudo mdadm —assemble /dev/md4 /dev/sdb4

Results in:

mdadm: cannot open device /dev/sdb4: No such file or directory
mdadm: /dev/sdb4 has no superblock - assembly aborted

This looks more like a MyBook problem.

~$ sudo apt-get install mdadm

And receive the following output:

Reading package lists… Done
Building dependency tree
Reading state information… Done
Package mdadm is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or is only available from another source
E: Package mdadm has no installation candidate

Thoughts? Is this an Ubuntu issue or a MyBook issue?