A7V333 RAID freakage - help?

[sanaka]

<FONT color=#000000>Hi. I'm trying to set up a RAID1 array on my new Asus A7V333 using the onboard Promise controller with two new identical 80G Maxtor drives. Right now I'm booting to my old hard drive on a regular IDE channel (trying to leave it there 'til the array is set up, then Drive Image to the array).

With no array defined, when boot up reaches the 'no array defined press ESC to continue booting' stage, I hit ESC and the controller automatically creates an array and reboots! I cannot bypass the RAID controller without creating an array. It was doing it fine before, and I can't remember at what point it changed. This kind of lack of control makes me very insecure 8-o

With an array created (whether the automatic one or one I define), FDisk only sees my new drives as 10G! =:-\


Any ideas what's up here much appreciated.

Peace
Sanaka</FONT>

 

[LiLithTecH]

Do you plan to only use the 2-80gig drives in the array?

Then just Image one of them on the standard IDE controller and then
setup your array (remove both from the RAID controller)(remember to delete the current array)

If you plan on using all 3 drives, just build the array now. You cannot Image to an array.
The system needs to build the array.

 

[sanaka]

Thanks, that sounds like a workable work-around. I'd rather figure what the problem is though, seems like the BIOS is tweaked somehow. Yes, only the two drives in the array, was going to ditch the old drive once I got the data off of it. I figured once the array was acting like one drive I could use Drive Image to transfer data from old drive to new RAID 'drive' My main problem is that FDisk only sees the new drives as 10G each.

Peace
Sanaka