AMR(4) MidnightBSD Kernel Interfaces Manual AMR(4)

NAME

amr — MegaRAID SCSI/ATA/SATA RAID driver

SYNOPSIS

device pci
device amr

DESCRIPTION

The amr driver provides support for LSI Logic MegaRAID SCSI RAID controllers and legacy American Megatrends MegaRAID SCSI RAID controllers, including models relabeled and sold by Dell and Hewlett-Packard.

HARDWARE

Controllers supported by the amr driver include:

MegaRAID SCSI 320-1E

MegaRAID SCSI 320-2E

MegaRAID SCSI 320-4E

MegaRAID SCSI 320-0X

MegaRAID SCSI 320-2X

MegaRAID SCSI 320-4X

MegaRAID SATA 300-4X

MegaRAID SATA 300-8X

MegaRAID SATA 150-4

MegaRAID SATA 150-6

MegaRAID i4 133 RAID

MegaRAID SCSI 320-0

MegaRAID SCSI 320-1

MegaRAID SCSI 320-2

MegaRAID SCSI 320-4

MegaRAID Series 418

MegaRAID Enterprise 1200 (Series 428)

MegaRAID Enterprise 1300 (Series 434)

MegaRAID Enterprise 1400 (Series 438)

MegaRAID Enterprise 1500 (Series 467)

MegaRAID Enterprise 1600 (Series 471)

MegaRAID Elite 1500 (Series 467)

MegaRAID Elite 1600 (Series 493)

MegaRAID Elite 1650 (Series 4xx)

MegaRAID Express 100 (Series 466WS)

MegaRAID Express 200 (Series 466)

MegaRAID Express 300 (Series 490)

MegaRAID Express 500 (Series 475)

Dell PERC

Dell PERC 2/SC

Dell PERC 2/DC

Dell PERC 3/DCL

Dell PERC 3/QC

Dell PERC 4/DC

Dell PERC 4/IM

Dell PERC 4/SC

Dell PERC 4/Di

Dell PERC 4e/DC

Dell PERC 4e/Di

Dell PERC 4e/Si

Dell PERC 4ei

HP NetRAID-1/Si

HP NetRAID-3/Si (D4943A)

HP Embedded NetRAID

Intel RAID Controller SRCS16

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 controller.

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 Virtual 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), 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〉.

MidnightBSD 0.3 May 30, 2005 MidnightBSD 0.3