raid 0 showing as failed: both drives are fine

[idata]

My intel onboard raid device is showing my raid 0 volume as failed, both drives pass all health checks from both SMART and Seagate's detail scan tool. When I press CTRL+M to enter the raid configuration tool during start up it shows the following:

raid0 : failed

port 0: (boot SSD, this is expected)

port 1: non-member (should be the other member)

port 2: member disk

Shown Here:

http://dl.dropbox.com/u/23737082/ad-hoc%20phone%20photos/2012-11-15%2009.34.09.jpg http://dl.dropbox.com/u/23737082/ad-hoc%20phone%20photos/2012-11-15%2009.34.09.jpg

If I open the Intel configuration tool in Windows, it shows my Raid0 is failed, containing just 1 of the 2 drives. The second drive which SHOULD be part of the volume is just sitting there, healthy as can be. When I hover over the raid tool it looks like the Intel Controller is looking for the serial number of my drive with a bad string on the affixed on the end (:0)

Shown Here (wrong serial, well proper serial plus : 0 on the end)

http://dl.dropbox.com/u/23737082/ad-hoc%20phone%20photos/2012-11-15%2009.46.40.jpg http://dl.dropbox.com/u/23737082/ad-hoc%20phone%20photos/2012-11-15%2009.46.40.jpg

http://dl.dropbox.com/u/23737082/ad-hoc%20phone%20photos/2012-11-15%2009.46.35.jpg http://dl.dropbox.com/u/23737082/ad-hoc%20phone%20photos/2012-11-15%2009.46.35.jpg

Here is the controller seeing the 'non member disk' that should be a member in perfect health with the proper serial number sans the :O on the end

http://dl.dropbox.com/u/23737082/ad-hoc%20phone%20photos/2012-11-15%2009.49.35.jpg http://dl.dropbox.com/u/23737082/ad-hoc%20phone%20photos/2012-11-15%2009.49.35.jpg

So I have both the drives, the controller knows about the array, it just thinks the one drive that should belong has a longer serial number... What can I do to recover this array and bring it out of failed mode. Both disks passed deep scanning with multiple tools.

This all happened after a BSOD on windows 7 following the machine coming out of sleep.

Any tips on how to add the other drive back into member status of the array and bring the raid back would be valuable, I back these drives up to an off site storage, however I just dumped a bunch of gigs of videos from my cameras that had not finished backing up to offsite when it crashed, needless to say I always erase memory cards after dumping. The reason I was using raid-0 (anti-raid) was because I used it mainly for video storage and editing and enjoyed the extra throughput.

Thanks for reading.

[DYoun6]

I am having the same issue with my Western Digital HDDs. Happened right after a firmware update to the RAID controller.

I'm guessing the RAID is based on the serial number, so finding a way to edit the serial number in the RAID BIOS or modifying the actual drive serial number is going to be our only hope.

Let me know if you find or have already found something.

Thanks,

-- DawgTool

[Allan_J_Intel1]

Please bear in mind RAID 0 does not offer any redundancy at all, I regret to inform you that the only way to get drives back will be to recreate RAID structure from scratch.

Data and structure are no longer available.

Allan.