Thanks for the reply. With a spanned array though, it still splits the
data across the 2 drives though right? Therefore, if one drive goes
down, I lost the data in both? I want to use them as if they were 2
regular(separate) drives. In Promise's BIOS utility (FastBuild), I can
only find and autobuild screen where it will allow RAID 0 or 1 only.
Any other thoughts would be appreciated.
You're missing my point, let me try again.
I took the liberty of downloading the Promise RAID MBFastTrak 133 Lite User
Manual (
ftp://211.78.163.2/product/it/mb/PDFzip/Manual/English/RAID_EM_A1.zip )
Notice on the bottom of page 56, it mentions FOUR different modes for your
defined arrays (Striping, Mirroring, Mirroring & Striping, and Spanning).
IOW, what the reference to Spanning is telling you is that you can use that
Promise controller to treat ONE or more HDs (up to four, since that's the
controller capacity, of course) as "spanned", or what's sometimes called
JBOD (Just a Bunch Of Drives). If you define a span, then all HDs defined
in that spanned array are treated as a single *logical* HD. IOW, if you had
a 30GB, 100GB, and 10GB HD on three IDE ports, you could create a spanned
array of all three HDs and it would appear to the OS/system as one, big
honkin' 140GB HD! Note, this is NOT a Stripe. In a Stripe, data is spread
evenly across multiple HDs. A spanned HD is simply treated as contiguous
space, space will be allocated to the next HD only once the current HD is
exhausted.
That said, notice that nothing prevents you from defining ONE HD as
spanned!!! That's the key to understanding how to define a single HD on one
IDE port. IOW, if you want four HDs, one on each IDE channel, master &
slave, to be just like a plain, ol' everyday non-RAID IDE controller, you
simply define FOUR spanned arrays in the setup, each w/ one HD.
Capesh?
Yeah, it's sort of ridiculous to make you go through all that work just to
get up to four single HDs configured on the IDE controllers, but that's the
way Promise does it. Other controllers, like those from Intel or Highpoint
don't make you do this. They assume unless defined as an array
specifically, the attached HD should be treated as a single non-RAID HD.
Jim