3112 SATA Raid controller - how to?

Aleksey Cheusov <[email protected]>
Newsgroups gmane.os.netbsd.help
Message-ID <[email protected]>
I have SATA Raid controller based on 3112 chip.
I configured it in BIOS as stripe. Boot NetBSD.
dmesg shows me the following.

  satalink0 at pci0 dev 8 function 0
  satalink0: Silicon Image SATALink 3112 (rev. 0x02)
  satalink0: SATALink BA5 register space disabled
  satalink0: bus-master DMA support present
  satalink0: primary channel wired to native-PCI mode
  satalink0: using irq 5 for native-PCI interrupt
  atabus2 at satalink0 channel 0
  satalink0: secondary channel wired to native-PCI mode
  atabus3 at satalink0 channel 1
  satalink0: port 0: device present, speed: 1.5Gb/s
  satalink0: port 1: device present, speed: 1.5Gb/s

  wd2(satalink0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
  wd3(satalink0:1:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)

  wd2 at atabus2 drive 0: <ST3320620AS>
  wd2: quirks 2<FORCE_LBA48>
  wd2: drive supports 16-sector PIO transfers, LBA48 addressing
  wd2: 298 GB, 620181 cyl, 16 head, 63 sec, 512 bytes/sect x 625142448 sectors
  wd2: 32-bit data port
  wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
  wd2(satalink0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)

  wd3 at atabus3 drive 0: <ST3320620AS>
  wd3: quirks 2<FORCE_LBA48>
  wd3: drive supports 16-sector PIO transfers, LBA48 addressing
  wd3: 298 GB, 620181 cyl, 16 head, 63 sec, 512 bytes/sect x 625142448 sectors
  wd3: 32-bit data port
  wd3: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
  wd3(satalink0:1:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)

Now I want to run

  disklabel -e /dev/<WHAT_DEVICE_HERE?>

The only message about raid from dmesg is

  "Kernelized RAIDframe activated"

What devices are associated with raid arrays (semi-hardware?)
in NetBSD?

-- 
Best regards, Aleksey Cheusov.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.