FreeBSD Man Pages

MLX(4) FreeBSD Kernel Interfaces Manual MLX(4)
NAMEmlx -- Mylex DAC-family RAID driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your
kernel configuration file:
devicepcidevicemlx
Alternatively, to load the driver as a module at boot time, place the
following line in loader.conf(5):
mlx_load="YES"
DESCRIPTION
The mlx driver provides support for Mylex DAC-family PCI to SCSI RAID
controllers, including versions relabeled by Digital/Compaq.
HARDWARE
Controllers supported by the mlx driver include:
+o Mylex DAC960P
+o Mylex DAC960PD / DEC KZPSC (Fast Wide)
+o Mylex DAC960PDU
+o Mylex DAC960PL
+o Mylex DAC960PJ
+o Mylex DAC960PG
+o Mylex DAC960PU / DEC PZPAC (Ultra Wide)
+o Mylex AcceleRAID 150 (DAC960PRL)
+o Mylex AcceleRAID 250 (DAC960PTL1)
+o Mylex eXtremeRAID 1100 (DAC1164P)
+o RAIDarray 230 controllers, aka the Ultra-SCSI DEC KZPAC-AA (1-ch, 4MB
cache), KZPAC-CA (3-ch, 4MB), KZPAC-CB (3-ch, 8MB cache)
All major firmware revisions (2.x, 3.x, 4.x and 5.x) are supported, how-
ever it is always advisable to upgrade to the most recent firmware avail-
able for the controller.
Compatible Mylex controllers not listed should work, but have not been
verified.
DIAGNOSTICSControllerinitialisationphasemlx%d:controllerinitialisationinprogress...mlx%d:initialisationcomplete
The controller firmware is performing/has completed initialisation.
mlx%d:physicaldrive%d:%dnotresponding
The drive at channel:target is not responding; it may have failed or been
removed.
mlx%d:spinningupdrives...
Drive startup is in progress; this may take several minutes.
mlx%d:configurationchecksumerror
The array configuration has become corrupted.
mlx%d:mirrorracerecoveryinprogressmlx%d:mirrorraceonacriticalsystemdrivemlx%d:mirrorracerecoveryfailed
These error codes are undocumented.
mlx%d:physicaldrive%d:%dCODmismatch
Configuration data on the drive at channel:target does not match the rest
of the array.
mlx%d:systemdriveinstallationaborted
Errors occurred preventing one or more system drives from being config-
ured.
mlx%d:newcontrollerconfigurationfound
The controller has detected a configuration on disk which supersedes the
configuration in its nonvolatile memory. It will reset and come up with
the new configuration.
mlx%d:FATALMEMORYPARITYERROR
Firmware detected a fatal memory error; the driver will not attempt to
attach to this controller.
mlx%d:unknownfirmwareinitialisationerror%x:%x:%x
An unknown error occurred during initialisation; it will be ignored.
Driverinitialisation/shutdownphase:mlx%d:can'tallocatescatter/gatherDMAtagmlx%d:can'tallocatebufferDMAtagmlx%d:can'tallocates/gtablemlx%d:can'tmakeinitials/glistmappingmlx%d:can'tmakepermanents/glistmappingmlx%d:can'tallocateinterruptmlx%d:can'tsetupinterrupt
A resource allocation error occurred while initialising the driver; ini-
tialisation has failed and the driver will not attach to this controller.
mlx%d:errorfetchingdrivestatus
The current status of all system drives could not be fetched; attachment
of system drives will be aborted.
mlx%d:device_add_childfailedmlx%d:bus_generic_attachreturned%d
Creation of the system drive instances failed; attachment of one or more
system drives may have been aborted.
mlxd%d:detaching...
The indicated system drive is being detached.
mlxd%d:stillopen,can'tdetach
The indicated system drive is still open or mounted; the controller can-
not be detached.
mlx%d:flushingcache...
The controller cache is being flushed prior to detach or shutdown.
Operationaldiagnostics:mlx%d:ENQUIRYfailed-%smlx%d:ENQUIRY2failedmlx%d:ENQUIRY_OLDfailedmlx%d:FLUSHfailed-%smlx%d:CHECKASYNCfailed-%smlx%d:REBUILDASYNCfailed-%smlx%d:commandfailed-%s
The controller rejected a command for the reason given.
mlx%d:I/Obeyondendofunit(%u,%d > %u)mlx%d:I/Oerror-%s
An I/O error was reported by the controller.
mlx%d:periodicenquiryfailed-%s
An attempt to poll the controller for status failed for the reason given.
mlx%d:mlx_periodic_enquiry:unknowncommand%x
The periodic status poll has issued a command which has become corrupted.
mlxd%d:driveofflinemlxd%d:driveonlinemlxd%d:drivecritical
The system disk indicated has changed state.
mlx%d:physicaldrive%d:%dresetmlx%d:physicaldrive%d:%dkilled%smlx%d:physicaldrive%d:%derrorlog:sense=%dasc=%xasq=%xmlx%d:info%4Dcsi%4D
The drive at channel:target has been reset, killed for the given reason,
or experienced a SCSI error.
mlx%d:unknownlogmessagetype%xmlx%d:errorreadingmessagelog-%s
An error occurred while trying to read the controller's message log.
mlxd%d:consistencycheckstartedmlx%d:consistencycheckcompleted
A user-initiated consistency check has started/completed.
mlx%d:driverebuildstartedfor%d:%dmlx%d:driverebuildcompleted
A user-initiated physical drive rebuild has started/completed.
mlx%d:backgroundcheck/rebuildoperationstartedmlx%d:backgroundcheck/rebuildoperationcompleted
An automatic system drive consistency check or physical drive rebuild has
started/completed.
mlx%d:channel%dpausingfor%dsecondsmlx%d:channel%dresumingmlx%d:pausecommandfailed-%smlx%d:pausefailedforchannel%dmlx%d:resumecommandfailed-%smlx%d:resumefailedforchannel%d
Controller/channel pause operation notification. (Channel pause is not
currently supported on any controller.)
mlx%d:controllerwedged(nottakingcommands)
The controller is not responding to attempts to submit new commands.
mlx%d:duplicatedoneeventforslot%dmlx%d:doneeventfornonbusyslot%d
Corruption has occurred in either the controller's onboard list of com-
mands or in the driver.
SEE ALSOmlxcontrol(8)AUTHORS
The mlx driver was written by Michael Smith <msmith@FreeBSD.org>.
This manual page was written by Jeroen Ruigrok van der Werven
<asmodai@FreeBSD.org> and Michael Smith <msmith@FreeBSD.org>.
BUGS
The driver does not yet support EISA adapters. The DEC KZPSC has insuf-
ficient flash ROM to hold any reasonably recent firmware. This has
caused problems for this driver.
The driver does not yet support the version 6.x firmware as found in the
AcceleRAID 352 and eXtremeRAID 2000 and 3000 products.
FreeBSD 6.2 August 10, 2004 FreeBSD 6.2