Question : WD Mybook world II (Raid 1 - mirror) won't boot

I lost connection to this device and during my attempt to reset 2nd time, the device would not boot.  It would never get to lighting the blue rings.  HD is spinning, I replaced the power cord and adapter but still no go.  I tried to recover using R-Studio Free Linux Recovery but it recovered files as unorganized -- I should've known this.  After studying and trying, I ended-up installing Ubuntu 10 on my pc.  It still would not mount via USB, Sata interface.  I got a dual mount usb sata docking station and after many different attempts, it mounted after auto updating the Ubuntu system.  I got permission enabled folders unlocked using the following command:
$ sudo mount /dev/mdN /media/xyz
$ sudo chmod -R 777 /media/xyz
I learned mdN depends how it is connected but you can find that out using the Ubuntu DiskUtility.
After accessing the folders, I discovered that I was missing some files (latest).  With many more attempts, tinkering, occassionally those files that I was missing showed up but lost during copying procedure.  Much later I learned, I can start and mount the drives separately from the Ubuntu Disk Utility.  In doing so, I learned one drive seemed to have the latest copies of all.  By the way, using Ubuntu Disk Utility it showed both drives were in good health.  So what happened?  Did the WD mybookworld OS Corrupt?  Why couldn't I get to at least the web intereface to check the status of Raid or anything?  Can I salvage this?  With so much data I don't want to take the time to copy, merge, and setup another drive manually for each permission and so on.. any suggestions?

Answer : WD Mybook world II (Raid 1 - mirror) won't boot

It could very well take over a day, perhaps longer.  The reason is that every bad block on the surviving disk can take up to approx 30 seconds.  You could have thousands of them.  Just wait it out.  By failing to  let it continue, you halted system in degraded mode. The firmware isn't very intelligent so it could have confused it to the point of failure.  I've seen such rebuilds take 3-4 days, FYI.  Be patient.