mfi(4) [linux man page]

MFI(4)							   BSD Kernel Interfaces Manual 						    MFI(4)

NAME

     mfi -- LSI MegaRAID SAS driver

SYNOPSIS

     To compile this driver into the kernel, place the following lines in your kernel configuration file:

	   device pci
	   device mfi

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   mfi_load="YES"

DESCRIPTION

     This driver is for LSI's next generation PCI Express SAS RAID controllers.  Access to RAID arrays (logical disks) from this driver is pro-
     vided via /dev/mfid? device nodes.  A simple management interface is also provided on a per-controller basis via the /dev/mfi? device node.

     The mfi name is derived from the phrase "MegaRAID Firmware Interface", which is substantially different than the old "MegaRAID" interface and
     thus requires a new driver.  Older SCSI and SATA MegaRAID cards are supported by amr(4) and will not work with this driver.

     Two sysctls are provided to tune the mfi driver's behavior when a request is made to remove a mounted volume.  By default the driver will
     disallow any requests to remove a mounted volume.	If the sysctl dev.mfi.%d.delete_busy_volumes is set to 1, then the driver will allow
     mounted volumes to be removed.

HARDWARE

     The mfi driver supports the following hardware:

     o	 LSI MegaRAID SAS 1078
     o	 LSI MegaRAID SAS 8408E
     o	 LSI MegaRAID SAS 8480E
     o	 LSI MegaRAID SAS 9260
     o	 Dell PERC5
     o	 Dell PERC6
     o	 IBM ServeRAID M5015 SAS/SATA
     o	 IBM ServeRAID-MR10i
     o	 Intel RAID Controller SROMBSAS18E

FILES

     /dev/mfid?  array/logical disk interface
     /dev/mfi?	 management interface

DIAGNOSTICS

     mfid%d: Unable to delete busy device  An attempt was made to remove a mounted volume.

SEE ALSO

     amr(4), pci(4), mfiutil(8)

HISTORY

     The mfi driver first appeared in FreeBSD 6.1.

AUTHORS

     The mfi driver and this manual page were written by Scott Long <scottl@FreeBSD.org>.

BUGS

     The driver does not support big-endian architectures at this time.

BSD
								   May 12, 2010 							       BSD

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