freebsd stable - Nov 2004 - No RAID for VT8237?

Can someone tell my why there is no RAID support for the VT8237 SATA
controller, when the chipset is listed as supported in the ata man page?
I've wasted enough money and time buying hardware and hoping that a
particular onboard ATA raid chips is supported. I understand that the
manufacturers may not release the data required to write a driver, and
that they keep changing specs around, but if we could at least have
documentation stating which of the common onboard raid chipsets are
supported. The motherboard in question is a gigabyte GA-K8VM800M. FreeBSD
5.3 detects the chipset, but shows the drives individually, not as an ar
array.

On Tue, 30 Nov 2004 15:19, Mike Jakubik wrote:
> documentation stating which of the common onboard raid chipsets are
> supported. The motherboard in question is a gigabyte GA-K8VM800M. FreeBSD
> 5.3 detects the chipset, but shows the drives individually, not as an ar
> array.
Did you define the array in the BIOS?

I am not sure how good 5.3 is at defining arrays (man atacontrol says 
atacontrol create should work but I've never used it). I doubt sysinstall
has
ATA RAID creation support.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20041130/33754234/attachment-0001.bin

Mike Jakubik wrote:
> Can someone tell my why there is no RAID support for the VT8237 SATA
> controller, when the chipset is listed as supported in the ata man page?
> I've wasted enough money and time buying hardware and hoping that a
> particular onboard ATA raid chips is supported. I understand that the
> manufacturers may not release the data required to write a driver, and
> that they keep changing specs around, but if we could at least have
> documentation stating which of the common onboard raid chipsets are
> supported. The motherboard in question is a gigabyte GA-K8VM800M. FreeBSD
> 5.3 detects the chipset, but shows the drives individually, not as an ar
> array.
> 
> 
Mike,

I'm not sure what the status of RAID on a VT8237 is, but is it possible 
the array(s) is(are) there and you are not noticing them?

Most of these lower end PATA/SATA "RAID" controllers are doing their 
work in software. As such you will be able to see (not to mention mount, 
modify, etc...) the physical RAID components in addition to the actual 
array.

For example, I have a Promise controller in my system with two RAID 1 
arrays defined:

   ~ > ls /dev/ar?
   /dev/ar0        /dev/ar1
   ~ > sudo atacontrol status ar0
   ar0: ATA RAID1 subdisks: ad4 ad6 status: READY
   ~ > sudo atacontrol status ar1
   ar1: ATA RAID1 subdisks: ad5 ad7 status: READY

However, I can also physically see the components:

   ~ > ls /dev/ad?
   /dev/ad4        /dev/ad5        /dev/ad6        /dev/ad7
   ~ > sudo atacontrol list
   ATA channel 0:
       Master: acd0 <SONY DVD RW DRU-700A/VY02> ATA/ATAPI revision 5
       Slave:       no device present
   ATA channel 1:
       Master: acd1 <TOSHIBA DVD-ROM SD-R1202/1020> ATA/ATAPI revision 5
       Slave:       no device present
   ATA channel 2:
       Master:  ad4 <Maxtor 6Y120P0/YAR41BW0> ATA/ATAPI revision 7
       Slave:   ad5 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI revision 5
   ATA channel 3:
       Master:  ad6 <Maxtor 6Y120P0/YAR41BW0> ATA/ATAPI revision 7
       Slave:   ad7 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI revision 5
   ATA channel 4:
       Master:      no device present
       Slave:       no device present
   ATA channel 5:
       Master:      no device present
       Slave:       no device present

IIRC sysinstall shows the RAID components before the arrays, when it 
comes time to choose a disk or disks to install on.

-Ash