Guilherme said:
hi group
I have a problem
I have a motherboard INTEL DX58SO (i7)
I have a RAID 5 - 4 using HDS - one stopped
I put it in ignorance for "no-raid" in the raid manager.
I like this recuprerar RAID?
This partitioned as follows:
If I install windows on the system partition (200GB) RAID will recreate the partition of the files?
Please know who you want to contact my email:
skype: gui_routing
TKS all.
In this thread, a participant suggests going into
the RAID BIOS screen, and change from "no-raid"
back to the exact same RAID parameters as you used before.
You must use the same stripe size and so on. If you're
not in the habit of tuning things, then the default
values will likely be exactly what is required.
http://communities.intel.com/thread/3351
That works, as long as you do not move the drives
from one port to another. For it to work, the drives
must be put back on the same ports, as they were on
when the drives were working in RAID mode. For a RAID
with a large number of disks, where you randomly
reinstalled them, it could take some time to discover
the right connection order again.
Running TestDisk, as described below, can help verify
the RAID is now working. You do not need to boot into
the RAID array OS, to do this. A Linux LiveCD, run TestDisk
from there, can help verify you've done everything exactly
right. And then you can try booting from the RAID (if it
contained the OS).
*Never* run a RAID, without backup images !!!
*******
Similar recovery information in post #6 here.
http://forums.extremeoverclocking.com/showthread.php?p=3329132
1. Reset both HDs to non-member using Intel BIOS utility -
the utility warns that all data will be lost - in fact only
metadata is lost and can be recreated using steps below.
2. Create a new array with identical settings as the broken array.
It is critical that the HDs are in the array the same order as
before. I was reconnecting the drives several times and lost
track of correct order. Because of that I had to go through
the steps twice (I guessed wrong the first time).
3. Get TestDisk from
http://www.cgsecurity.org. I used Windows
version (I installed a new Vista on a separate HD for this purpose).
[ Testdisk can be run from a Linux LiveCD as well. ]
4. Run TestDisk according to steps on the web site. If your HDs
are connected in correct order, TestDisk should find the lost
partition(s) within a few seconds. It ran for several hours,
scanning my array and never found anything because I had HDs
were connected in wrong order. After I changed the order and
restarted from step #1 TestDisk found the missing partition
immediately.
5. Have the TestDisk write the fixed partition table to the drive
and reboot. [Note : If TestDisk found the partitions, chances
are at this point, everything is OK. Don't panic and start
writing stuff for nothing! In general, only use the write function
in TestDisk, when you're absolutely sure there is no
other available recovery option.]
6. Now all your data on the array should be readable but the
system might not boot (it didn't for me).
7. Run Vista repair from installation CD to fix the MBR.
[Note: When the author of this solution did step (5), that
is why step (7) is needed. Overwriting the MBR, loses the MBR
boot code.]
8. Last but not least, send a donation to Mr. Grenier,
the author of TestDisk. [Sage advice...]
*******
HTH,
Paul
