NAME
arcmsr —
Areca Technology Corporation SATA/SAS
RAID controller
SYNOPSIS
arcmsr* at pci? dev ? function ?
DESCRIPTION
Thearcmsr driver provides support for the PCI-X and PCI
Express RAID controllers from Areca Technology Corporation:
- ARC-1110 PCI-X 4 Port SATA RAID Controller
- ARC-1110ML PCI-X 4 Port SATA RAID Controller
- ARC-1120 PCI-X 8 Port SATA RAID Controller
- ARC-1120ML PCI-X 8 Port SATA RAID Controller
- ARC-1130 PCI-X 12 Port SATA RAID Controller
- ARC-1130ML PCI-X 12 Port SATA RAID Controller
- ARC-1160 PCI-X 16 Port SATA RAID Controller
- ARC-1160ML PCI-X 16 Port SATA RAID Controller
- ARC-1170 PCI-X 24 Port SATA RAID Controller
- ARC-1200 Rev A PCI Express 2 Port SATA RAID Controller
- ARC-1202 PCI Express 2 Port SATA RAID Controller
- ARC-1210 PCI Express 4 Port SATA RAID Controller
- ARC-1220 PCI Express 8 Port SATA RAID Controller
- ARC-1230 PCI Express 12 Port SATA RAID Controller
- ARC-1230ML PCI Express 12 Port SATA RAID Controller
- ARC-1231ML PCI Express 12 Port SATA RAID Controller
- ARC-1260 PCI Express 16 Port SATA RAID Controller
- ARC-1260ML PCI Express 16 Port SATA RAID Controller
- ARC-1261ML PCI Express 16 Port SATA RAID Controller
- ARC-1280 PCI Express 24 Port SATA RAID Controller
- ARC-1280ML PCI Express 24 Port SATA RAID Controller
- ARC-1680 PCI Express 8 Port SAS RAID Controller
- ARC-1680LP PCI Express 8 Port SAS RAID Controller
- ARC-1680i PCI Express 8 Port SAS RAID Controller
- ARC-1680x PCI Express 8 Port SAS RAID Controller
- ARC-1681 PCI-X 8 Port SAS RAID Controller
These controllers support RAID levels 0, 1, 1E, 3, 5, 6, and JBOD using either SAS or SATA II drives.
arcmsr supports management and monitoring
of the controller through the
bioctl(8) and
envstat(8) commands.
Please note, however, that to use some features that require special privileges, such as creating/removing hot-spares, pass-through disks or RAID volumes will require to have the password disabled in the firmware; otherwise a Permission denied error will be reported by bioctl(8).
When a RAID 1 or 1+0 volume is created, either through the bioctl(8) command or controller's firmware, the volume won't be accessible until the initialization is done. A way to get access to the sd(4) device that corresponds to that volume without rebooting, is to issue the following command (once the initialization is finished):
$ scsictl scsibus0 scan any any
The arcmsr driver will also report to the
kernel log buffer any error that might appear when handling firmware
commands, such as used by the
bioctl(8) command.
EVENTS
The arcmsr driver is able to send events
to powerd(8) if a volume or any drive connected to the volume is not
online. The
state-changed
event will be sent to the
/etc/powerd/scripts/sensor_drive script when such
condition happens.
SEE ALSO
intro(4), pci(4), scsi(4), sd(4), bioctl(8), envstat(8), powerd(8), scsictl(8)
HISTORY
The arcmsr driver first appeared in
NetBSD 5.0.
AUTHORS
The arcmsr driver was originally written
for OpenBSD by David Gwynne.
It was ported to NetBSD and extended by
Juan Romero Pardines.