arcmsr(4) [netbsd man page]
ARCMSR(4) BSD Kernel Interfaces Manual ARCMSR(4) NAME
arcmsr -- Areca Technology Corporation SATA/SAS RAID controller SYNOPSIS
arcmsr* at pci? dev ? function ? DESCRIPTION
The arcmsr 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 fol- lowing 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. BSD
March 3, 2008 BSD
Check Out this Related Man Page
AMR(4) BSD Kernel Interfaces Manual AMR(4) NAME
amr -- MegaRAID SCSI/ATA/SATA RAID driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device pci device scbus device amr Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): amr_load="YES" DESCRIPTION
The amr driver provides support for LSI Logic MegaRAID SCSI, ATA and SATA RAID controllers and legacy American Megatrends MegaRAID SCSI RAID controllers, including models relabeled and sold by Dell and Hewlett-Packard. LSI MegaRAID SAS controllers are supported by mfi(4) and will not work with this driver. HARDWARE
Controllers supported by the amr driver include: o MegaRAID SATA 150-4 o MegaRAID SATA 150-6 o MegaRAID SATA 300-4X o MegaRAID SATA 300-8X o MegaRAID SCSI 320-1E o MegaRAID SCSI 320-2E o MegaRAID SCSI 320-4E o MegaRAID SCSI 320-0X o MegaRAID SCSI 320-2X o MegaRAID SCSI 320-4X o MegaRAID SCSI 320-0 o MegaRAID SCSI 320-1 o MegaRAID SCSI 320-2 o MegaRAID SCSI 320-4 o MegaRAID Series 418 o MegaRAID i4 133 RAID o MegaRAID Elite 1500 (Series 467) o MegaRAID Elite 1600 (Series 493) o MegaRAID Elite 1650 (Series 4xx) o MegaRAID Enterprise 1200 (Series 428) o MegaRAID Enterprise 1300 (Series 434) o MegaRAID Enterprise 1400 (Series 438) o MegaRAID Enterprise 1500 (Series 467) o MegaRAID Enterprise 1600 (Series 471) o MegaRAID Express 100 (Series 466WS) o MegaRAID Express 200 (Series 466) o MegaRAID Express 300 (Series 490) o MegaRAID Express 500 (Series 475) o Dell PERC o Dell PERC 2/SC o Dell PERC 2/DC o Dell PERC 3/DCL o Dell PERC 3/QC o Dell PERC 4/DC o Dell PERC 4/IM o Dell PERC 4/SC o Dell PERC 4/Di o Dell PERC 4e/DC o Dell PERC 4e/Di o Dell PERC 4e/Si o Dell PERC 4ei o HP NetRAID-1/Si o HP NetRAID-3/Si (D4943A) o HP Embedded NetRAID o Intel RAID Controller SRCS16 o Intel RAID Controller SRCU42X DIAGNOSTICS
Driver initialisation/shutdown phase amr%d: memory window not available amr%d: I/O window not available The PCI BIOS did not allocate resources necessary for the correct operation of the controller. The driver cannot attach to this controller. amr%d: busmaster bit not set, enabling The PCI BIOS did not enable busmaster DMA, which is required for the correct operation of the controller. The driver has enabled this bit and initialisation will proceed. amr%d: can't allocate register window amr%d: can't allocate interrupt amr%d: can't set up interrupt amr%d: can't allocate parent DMA tag amr%d: can't allocate buffer DMA tag amr%d: can't allocate scatter/gather DMA tag amr%d: can't allocate s/g table amr%d: can't allocate mailbox tag amr%d: can't allocate mailbox memory A resource allocation error occurred while initialising the driver; initialisation has failed and the driver will not attach to this con- troller. amr%d: can't obtain configuration data from controller amr%d: can't obtain product data from controller The driver was unable to obtain vital configuration data from the controller. Initialisation has failed and the driver will not attach to this controller. amr%d: can't establish configuration hook amr%d: can't scan controller for drives The scan for logical drives managed by the controller failed. No drives will be attached. amr%d: device_add_child failed amr%d: bus_generic_attach returned %d Creation of the logical drive instances failed; attachment of one or more logical drives may have been aborted. amr%d: flushing cache... The controller cache is being flushed prior to shutdown or detach. Operational diagnostics amr%d: I/O beyond end of unit (%u,%d > %u) A partitioning error or disk corruption has caused an I/O request beyond the end of the logical drive. This may also occur if FlexRAID Vir- tual Sizing is enabled and an I/O operation is attempted on a portion of the virtual drive beyond the actual capacity available. amr%d: polled command timeout An initialisation command timed out. The initialisation process may fail as a result. amr%d: bad slot %d completed The controller reported completion of a command that the driver did not issue. This may result in data corruption, and suggests a hardware or firmware problem with the system or controller. amr%d: I/O error - %x An I/O error has occurred. SEE ALSO
cd(4), da(4), mfi(4), sa(4), scsi(4) AUTHORS
The amr driver was written by Mike Smith <msmith@FreeBSD.org>. This manual page was written by Mike Smith <msmith@FreeBSD.org> and Jeroen Ruigrok van der Werven <asmodai@FreeBSD.org>. BSD
March 29, 2006 BSD