FreeBSD Manual Pages
AMR(4) FreeBSD Kernel Interfaces Manual AMR(4) NAME amr -- AMI MegaRAID PCI-SCSI RAID driver SYNOPSIS device pci device amr DESCRIPTION The amr driver provides support for American Megatrends MegaRAID Express, Elite and Enterprise family SCSI RAID controllers, including models rela- beled and sold by Hewlett-Packard and Dell. Supported controllers include: +o MegaRAID 320-1 +o MegaRAID 320-2 +o MegaRAID Series 418 +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 Elite 1500 (Series 467) +o MegaRAID Elite 1600 (Series 493) +o MegaRAID Elite 1650 (Series 4xx) +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/Di +o HP NetRAID-1/Si +o HP NetRAID-3/Si (D4943A) +o HP Embedded NetRAID 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 opera- tion 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 cor- rect 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; ini- tialisation 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 con- troller. 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>. FreeBSD 4.10 January 23, 2000 FreeBSD 4.10
NAME | SYNOPSIS | DESCRIPTION | DIAGNOSTICS | SEE ALSO | AUTHORS
Want to link to this manual page? Use this URL:
<https://www.freebsd.org/cgi/man.cgi?query=amr&sektion=4&manpath=FreeBSD+4.10-RELEASE>