Recovering fstab for WD Mybook WE II (2TB)

summary:

mounting drive B

Recovering fstab for WD Mybook WE II (2TB)

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

Hello. I've brought my 2 TB device back to life using starting-from-scratch tread. SSH access now is working. I almost happy -)
But inner LED circle (capacity) on front is full and lighting all the time. I think it's because of drive B which is plugged in but not mounted.
And in the web interface I don't have any options in Drive Managment exept Safely Remove USB Drive.
When I am trying to mount sdb using "mount /dev/sdb sdb -t ext3" system responds as follows:
"mount: Mounting /dev/sdb on sdb failed: Device or resource busy"
I think it will work if I add /dev/sdb in fstab and reboot, but I'm not quite sure about other options I should pass through to make my WE II work as it use to work. (mtab and other stuff)

In the next step I want to make RAID-1.

Please help me with original fstab and maybe some other files which are refer to mounting two drives.

Great thanx!

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

Re: Recovering fstab for WD Mybook WE II (2TB)

d4nk17 1200788014|%e %b %Y, %H:%M %Z|agohover

hello, i just want to confirm this, you redid your 2tb world edition? i have a 1tb and will need to redo it probably.. :(
i have no access to it. and i don't want my extra money wasted because the drives aren't worth much…
if i can, i will just pop one in my xbox mybe someone wants the case…

Re: Recovering fstab for WD Mybook WE II (2TB)

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

Yes I did it! -)
Just plug your drive A from mybook to PC and boot any Linux-system live CD (I used flash-pen to boot). Then do all from http://mybookworld.wikidot.com/forum/t-23918/recovering-original-fw-tested.
You'll get you book working and access to it, but in my case it's unable to mount drive B -(
I just want to look original fstab and @mtab files from WE II, I'm sure it will help.

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

Re: Recovering fstab for WD Mybook WE II (2TB)

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

# <file system> <mount pt>       <type> <options>               <dump>  <pass>
/dev/root       /                ext3   rw,noauto,noatime       0       1
proc            /proc            proc   defaults                0       0
devpts          /dev/pts         devpts defaults,gid=5,mode=620 0       0
sys             /sys             sysfs  defaults                0       0
/dev/md2        none             swap   defaults                0       0
/dev/md3        /var             ext3   defaults,noatime        0       2
/dev/md4        /shares/internal ext3   defaults,noatime        0       2

rootfs / rootfs rw 0 0
/dev/root / ext3 rw,noatime,data=ordered 0 0
proc /proc proc rw 0 0
devpts /dev/pts devpts rw 0 0
sys /sys sysfs rw 0 0
/dev/md3 /var ext3 rw,noatime,data=ordered 0 0
/dev/md4 /shares/internal ext3 rw,noatime,data=ordered 0 0
usbfs /proc/bus/usb usbfs rw 0 0

Re: Recovering fstab for WD Mybook WE II (2TB)

aviadra 1202124249|%e %b %Y, %H:%M %Z|agohover

i have a MWII (1T ver) as well. i have rescued it… but i think the problem is that the images that we are using are from a MWI (1) device… that is y we dont have the RAID options.
i also belive that reading the original Fstab files as posted by kevku will not help as IMHO the RAID part comes into play before the mounting takes place.

can anyone help ?

Re: Recovering fstab for WD Mybook WE II (2TB)

marc13 1202654562|%e %b %Y, %H:%M %Z|agohover

I've just posted a message for asking if someone has a firmware for MWBEII ( firmware with RAID configuration in it):
http://mybookworld.wikidot.com/forum/t-40592/western-digital-medition-ii-2x500gb-with-raid#post-104896

If nobody give us it's RAID MWBEII,
I will post mine if I success undoing wrong modifications I've done in my firmware (maybe in one week).

Re: Recovering fstab for WD Mybook WE II (2TB)

FimbleRhodan 1203384130|%e %b %Y, %H:%M %Z|agohover

Ok, so I own two WD Mybook WE II (2x500) systems. My first system bricked on it's own, I did nothing that I know of, except copy files to it. It was out of box RAID 0. I have (had?) data on there that I really don't want to loose.

The second system I purchased in the hope that something had gone wrong with the motherboard. Alas that is not the case. I have verified that both of my systems will boot using the disks that came with the second system. The only thing I have done to the second system is to RAID 1 it, and to add an empty folder and one txt file.

So I found my way to this site, in the hopes that I might recover my system without loosing the raid 0 4th data partition. However, from what I have read about here… the Recovery process, it is unlikely to work for these dual harddrive systems with the given files. I have successfully mounted drive 'A' on my linux machine, and I can read from the first 3 partitions. the last partition, which will at least mount read-only will not support any other activities that I know how to accomplish.

Any chance I can somehow use the combination of these two systems to mount the raid 0 array once again? I debated replacing the first three partitions information with the rescue operations described on this wiki, but it looks like that process really does only work for the single drive configuration. I can presumably provide images of the raid 1 system…but still not clear on how to capture them. VERY curious to whether replacing partions 1, 2 and 3, but not 4 on both my drives would result in the desired outcome.

thoughts?

update .. new steps taken

Alright, so new steps that I've taken.
First, I've mis-spoken above. I've only been able to mount sda1, sda3 and sda4*. sda2 fails with the message saying something along the lines of no valid superblock or whatever. I'm not certain whether this is due to it being a swap partition or perhaps the root cause of my bricked nas.

Second, I've taken, using dd, images of sda1, sda2, sda3 and am in the process of sda4. I'm not sure how sda4 is going to turn out, as when I mount that partition, nothing is readable below public, even public says it's not a directory, which is must be…but I digress… anyway it reports itself about 910 gig, which is not too surprising as it is in theory node 0 of the two node raid 0 system. SO, the dd process has been running for about 4 hours…and it's only at 18gig. I only have a 500 gig drive I'm copying it too, so I'm hoping it cuts out before then…we'll see.

In the mean time, I've used the new nas, to build 1 new drive image, and am currently working on the second drive…so I will have two 'new' WD raid 1 drives with the almost out of box settings. Once it completes, I'm hoping to put this second set back in the linear mode (raid 0). At which point, I'm hoping I can put just image sda4 on this new drive(s) and get a boot from the nas, and maybe, just maybe get my raid 0 data back. I think it all depends on two things.

1. dd's ability to get the sda4 raid 0 data EXACTLY right, which is the point of dd, but I'm not sure when it comes to raid 0.
2. the hope the WD didn't do anything to sda1, 2 and 3 that sda4 will be depedent upon beyond booting…otherwise, it's been the waste of a bunch of $$ and a LOT of time.

Sorry for the strategy, but I put it here, because I'm working in the dark a bit, and hoping someone else has more experience or better suggestions.

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

Re: Recovering fstab for WD Mybook WE II (2TB)

The Sentinel 1205672402|%e %b %Y, %H:%M %Z|agohover

See my thread here for taking images of a 1TB (2-drive) system: http://mybookworld.wikidot.com/forum/t-45881/how-to-backup-wd-mybook-world-ed-ii-1tb

I've detailed how to back up the unit using linux (I've done so on an out-of-the-box drive).

I'll soon post instructions for restoring these images (the 2nd drive is still being imaged as we speak).

last edited on 1205672627|%e %b %Y, %H:%M %Z|agohover by The Sentinel + show more

Re: Recovering fstab for WD Mybook WE II (2TB)

mre0 1208370722|%e %b %Y, %H:%M %Z|agohover

Could you also post your images? I was unable to restore my MBWEII (2x500MB) from keisan´s images. Also, your instructions to restore would be useful.

Re: Recovering fstab for WD Mybook WE II (2TB)

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

The problem with the rescue procedure as it is described elsewhere is that it is written by people who have only a single-drive MBW. I have read the instructions and from what I see I think there is a problem with it regarding two-disk devices.
At one point, PCnity (or one of the later editors) says to edit /etc/fstab and to change /dev/md4 to /dev/sda4. This is the reason why they have to do this:
1. Since they want a general rescue procedure, for differently sized disks, they cannot provide an image for the last partition.
2. They recommend installing the images for the first three partitions since they are all equall an all MBW disks.
3. They say to create the last partition, /dev/sda4 as big as the space remains.

So far so good, but: The first three partitions now match the raid specifications of the mdadm and are mounted as such. The last partition, build by hand, will not mount as raid (/dev/md4) and therefore must be mounted as it is, an ext3 partition. Therefore:

4. They say, you have to change /etc/fstab to enable the mounting of the last partition.

In the case of a single-disk device you end up with a device using the last partition directly, which should be fine. But if you have two disks, only one disk will be used by this procedure and no raid will be possible.

I didn't brick my device yet, so I cannot verify that the following procedure will work, since I didn't test it, but basically, to make this all work on a two-disk device you would have to modify the described procedure as follows:

After installing the first three patritions from images on both disks, create a fourth partition with ext3 file system on both of them. Be careful that the sizes are exactly equal in both cases.

Edit /etc/fstab on both disks and disable the line with /dev/md4 (put # in front of the line)

Install both disks into the device. I don't know if your device will boot now. Let's hope it does. If it does you have to do the following steps to enable the raid again:

Construct a new raid out of the /dev/sda4 and /dev/sdb4 partitions and let it be /dev/md4. Look here for help how to do this: http://www.linuxmanpages.com/man8/mdadm.8.php
I think something like this:
mdadm --create /dev/md4 --level=0 --raid-devices=2 /dev/sda4 /dev/sdb4
should do the trick.

If everything went right, try to create a new file system on the newly created raid:

mkfs.ext3 /dev/md4

Now try to mount the raid by hand:

mount /dev/md4 /shares/internal

If this works, enable the line in /etc/fstab containing the mount option of the raid. Reboot your device.

Disclaimer: As I said I didn't try this procedure yet, since I never bricked my device yet. It's not necessary a working solution. Try to follow it as described and if something fails, try to locate the reason and make a reasonable work-around. The crucial point is, that it's not enough to make a single ext3 partition, not even on both disks allone. You have to do this, then construct the raid and then create an ext3 file system on the raid again before this can work.

Hope this helps someone.

Z80

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

Re: Recovering fstab for WD Mybook WE II (2TB)

acfischer42 1210016388|%e %b %Y, %H:%M %Z|agohover

Hi,

I am in the process of recovering my Mybook right now and following these instructions it is back alive. Issues as stated above are that md4 is not setup correctly, but as well that the raid arrays for md1, md2 and md3 are not ok anymore as well. These are shown as one disk removed.

I fixed this part with: (do this for all md1, md2 and md3 respectively)

[root@MyBookWorld /]# mdadm /dev/md3 -a /dev/sdb3
mdadm: added /dev/sdb3

Information can be obtained after this with:

[root@MyBookWorld /]# mdadm —detail /dev/md3
/dev/md3:
Version : 00.90.03
Creation Time : Tue Mar 27 15:05:52 2007
Raid Level : raid1
Array Size : 987904 (964.91 MiB 1011.61 MB)
Device Size : 987904 (964.91 MiB 1011.61 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 3
Persistence : Superblock is persistent

Update Time : Mon May 5 21:13:22 2008
State : clean, degraded, recovering
Active Devices : 1
Working Devices : 2
Failed Devices : 0
Spare Devices : 1

Rebuild Status : 13% complete

UUID : cc0255b1:ab6a743e:140ccd5c:a2cc1275
Events : 0.288

Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
2 8 19 1 spare rebuilding /dev/sdb3

I have not fixed md4 yet, some error with mdadm RUN_ERROR, will keep you posted.

Edit:/ finally some progress on md4. seems that in RAID 1 configuration it works, but not in Raid 0. /var/log/messages contains

May 5 23:05:32 MyBookWorld user.info kernel: md: bind<sda4>
May 5 23:05:32 MyBookWorld user.info kernel: md: bind<sdb4>
May 5 23:05:32 MyBookWorld user.warn kernel: md: personality for level 0 is not loaded!
May 5 23:05:32 MyBookWorld user.info kernel: md: md5 stopped.
May 5 23:05:32 MyBookWorld user.info kernel: md: unbind<sdb4>
May 5 23:05:32 MyBookWorld user.info kernel: md: export_rdev(sdb4)
May 5 23:05:32 MyBookWorld user.info kernel: md: unbind<sda4>
May 5 23:05:32 MyBookWorld user.info kernel: md: export_rdev(sda4)

Does anyone have any idea on the personality 0? Is there a difference in mdadm between single disk and multi disk version?

@

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

Re: Recovering fstab for WD Mybook WE II (2TB)

bakerod 1215477647|%e %b %Y, %H:%M %Z|agohover

You need to use level=linear rather than level=0 (raid0 is striping mode, not linear mode).

Re: Recovering fstab for WD Mybook WE II (2TB)

Penguin64 1214070261|%e %b %Y, %H:%M %Z|agohover

I just bought an empty (no hard drives) WD MyBook WE II. I am just learning (through reading here) that I may not simply be able to pop a couple of HDDs in and away I go. I would like to be able to use this device with a couple of 500MB drives in RAID1. So my big questions are: Has anyone successfully recovered a WE II device with 2 drives working in RAID1? Is it worth it for me to pursue? I haven't purchased the HDDs yet and I've only sunk $30 in the case so far.