mly — Mylex AcceleRAID/eXtremeRAID family driver

       The mly driver was written by Michael Smith <msmith@FreeBSD.org>.

       This manual page was written by Michael Smith <msmith@FreeBSD.org>.

       The driver does not yet provide an external management interface.

       Enclosures are not named or otherwise identified in event messages.

Debian                                           August 10, 2004                                          MLY(4)

       The  mly driver provides support for Mylex AcceleRAID and eXtremeRAID-family PCI to SCSI RAID controllers
       with version 6.00 and later firmware.

       Logical devices (array drives) attached to the controller are presented to the SCSI subsystem  as  though
       they  were  direct-access  devices  on  a  virtual SCSI bus.  Physical devices which are not claimed by a
       logical device are presented on SCSI channels which match the physical channels on the controller.

Controllerinitialisationphasemly%d:controllerinitialisationstartedmly%d:initialisationcomplete

       The controller firmware has started initialisation.  Normally this process is performed by the controller
       BIOS, but the driver may need to do this in cases where the BIOS has failed, or is not  compatible  (e.g.
       on non-x86 systems).

       mly%d:drivespinupinprogress

       Drive startup is in progress; this may take several minutes.

       mly%d:mirrorracerecoveryfailed,oneormoredrivesofflinemly%d:mirrorracerecoveryinprogressmly%d:mirrorracerecoveryonacriticaldrive

       These error codes are undocumented.

       mly%d:FATALMEMORYPARITYERROR

       Firmware detected a fatal memory error; the driver will not attempt to attach to this controller.

       mly%d:unknowninitialisationcode%x

       An unknown error occurred during initialisation; it will be ignored.

   Driverinitialisation/shutdownphasemly%d:can'tenablebusmasterfeaturemly%d:memorywindownotavailablemly%d:can'tallocateregisterwindowmly%d:can'tallocateinterruptmly%d:can'tsetupinterrupt

       The  system's  PCI  BIOS  has not correctly configured the controller's PCI interface; initialisation has
       failed and the driver will not attach to this controller.

       mly%d:can'tallocateparentDMAtagmly%d:can'tallocatebufferDMAtagmly%d:can'tallocatecommandpacketDMAtagmly%d:can'tallocatescatter/gatherDMAtagmly%d:can'tallocates/gtablemly%d:can'tallocatememorymailboxDMAtagmly%d:can'tallocatememorymailbox

       A resource allocation error occurred while initialising the driver; initialisation  has  failed  and  the
       driver will not attach to this controller.

       mly%d:BTLrescanresultcorrupted

       The  results  of  a scan for an attached device were corrupted.  One or more devices may not be correctly
       reported.

       mly%d:flushingcache...

       The controller cache is being flushed prior to detach or shutdown.

   Operationaldiagnosticsmly%d:physicaldevice%d:%donlinemly%d:physicaldevice%d:%dstandbymly%d:physicaldevice%d:%dautomaticrebuildstartedmly%d:physicaldevice%d:%dmanualrebuildstartedmly%d:physicaldevice%d:%drebuildcompletedmly%d:physicaldevice%d:%drebuildcancelledmly%d:physicaldevice%d:%drebuildfailedforunknownreasonsmly%d:physicaldevice%d:%drebuildfailedduetonewphysicaldevicemly%d:physicaldevice%d:%drebuildfailedduetologicaldrivefailuremly%d:physicaldevice%d:%dfoundmly%d:physicaldevice%d:%dgonemly%d:physicaldevice%d:%dunconfiguredmly%d:physicaldevice%d:%dexpandcapacitystartedmly%d:physicaldevice%d:%dexpandcapacitycompletedmly%d:physicaldevice%d:%dexpandcapacityfailedmly%d:physicaldevice%d:%dparityerrormly%d:physicaldevice%d:%dsofterrormly%d:physicaldevice%d:%dmiscellaneouserrormly%d:physicaldevice%d:%dresetmly%d:physicaldevice%d:%dactivesparefoundmly%d:physicaldevice%d:%dwarmsparefoundmly%d:physicaldevice%d:%dinitializationstartedmly%d:physicaldevice%d:%dinitializationcompletedmly%d:physicaldevice%d:%dinitializationfailedmly%d:physicaldevice%d:%dinitializationcancelledmly%d:physicaldevice%d:%dwriterecoveryfailedmly%d:physicaldevice%d:%dscsibusresetfailedmly%d:physicaldevice%d:%ddoublecheckconditionmly%d:physicaldevice%d:%ddevicecannotbeaccessedmly%d:physicaldevice%d:%dgrosserroronscsiprocessormly%d:physicaldevice%d:%dbadtagfromdevicemly%d:physicaldevice%d:%dcommandtimeoutmly%d:physicaldevice%d:%dsystemresetmly%d:physicaldevice%d:%dbusystatusorparityerrormly%d:physicaldevice%d:%dhostsetdevicetofailedstatemly%d:physicaldevice%d:%dselectiontimeoutmly%d:physicaldevice%d:%dscsibusphaseerrormly%d:physicaldevice%d:%ddevicereturnedunknownstatusmly%d:physicaldevice%d:%ddevicenotreadymly%d:physicaldevice%d:%ddevicenotfoundatstartupmly%d:physicaldevice%d:%dCODwriteoperationfailedmly%d:physicaldevice%d:%dBDTwriteoperationfailedmly%d:physicaldevice%d:%dmissingatstartupmly%d:physicaldevice%d:%dstartrebuildfailedduetophysicaldrivetoosmallmly%d:physicaldevice%d:%dsensedatareceivedmly%d:sensekey%dasc%02xascq%02xmly%d:info%4Dcsi%4Dmly%d:physicaldevice%d:%dofflinemly%d:sensekey%dasc%02xascq%02xmly%d:info%4Dcsi%4D

       The reported event refers to the physical device at the given channel:target address.

       mly%d:logicaldevice%d(%s)consistencycheckstartedmly%d:logicaldevice%d(%s)consistencycheckcompletedmly%d:logicaldevice%d(%s)consistencycheckcancelledmly%d:logicaldevice%d(%s)consistencycheckcompletedwitherrorsmly%d:logicaldevice%d(%s)consistencycheckfailedduetologicaldrivefailuremly%d:logicaldevice%d(%s)consistencycheckfailedduetophysicaldevicefailuremly%d:logicaldevice%d(%s)automaticrebuildstartedmly%d:logicaldevice%d(%s)manualrebuildstartedmly%d:logicaldevice%d(%s)rebuildcompletedmly%d:logicaldevice%d(%s)rebuildcancelledmly%d:logicaldevice%d(%s)rebuildfailedforunknownreasonsmly%d:logicaldevice%d(%s)rebuildfailedduetonewphysicaldevicemly%d:logicaldevice%d(%s)rebuildfailedduetologicaldrivefailuremly%d:logicaldevice%d(%s)offlinemly%d:logicaldevice%d(%s)criticalmly%d:logicaldevice%d(%s)onlinemly%d:logicaldevice%d(%s)initializationstartedmly%d:logicaldevice%d(%s)initializationcompletedmly%d:logicaldevice%d(%s)initializationcancelledmly%d:logicaldevice%d(%s)initializationfailedmly%d:logicaldevice%d(%s)foundmly%d:logicaldevice%d(%s)gonemly%d:logicaldevice%d(%s)expandcapacitystartedmly%d:logicaldevice%d(%s)expandcapacitycompletedmly%d:logicaldevice%d(%s)expandcapacityfailedmly%d:logicaldevice%d(%s)badblockfoundmly%d:logicaldevice%d(%s)sizechangedmly%d:logicaldevice%d(%s)typechangedmly%d:logicaldevice%d(%s)baddatablockfoundmly%d:logicaldevice%d(%s)readofdatablockinbdtmly%d:logicaldevice%d(%s)writebackdatafordiskblocklost

       The event report will include the name of the SCSI device which has attached to the device if possible.

       mly%d:enclosure%dfan%dfailedmly%d:enclosure%dfan%dokmly%d:enclosure%dfan%dnotpresentmly%d:enclosure%dpowersupply%dfailedmly%d:enclosure%dpowersupply%dokmly%d:enclosure%dpowersupply%dnotpresentmly%d:enclosure%dtemperaturesensor%dfailedmly%d:enclosure%dtemperaturesensor%dcriticalmly%d:enclosure%dtemperaturesensor%dokmly%d:enclosure%dtemperaturesensor%dnotpresentmly%d:enclosure%dunit%daccesscriticalmly%d:enclosure%dunit%daccessokmly%d:enclosure%dunit%daccessoffline

       These events refer to external enclosures by number.  The driver does not attempt to name the enclosures.

       mly%d:controllercachewritebackerrormly%d:controllerbatterybackupunitfoundmly%d:controllerbatterybackupunitchargelevellowmly%d:controllerbatterybackupunitchargelevelokmly%d:controllerinstallationabortedmly%d:controllermirrorracerecoveryinprogressmly%d:controllermirrorraceoncriticaldrivemly%d:controllermemorysofteccerrormly%d:controllermemoryhardeccerrormly%d:controllerbatterybackupunitfailed

       These events report controller status changes.

       Controllers supported by the mly driver include:

       •   Mylex AcceleRAID 160
       •   Mylex AcceleRAID 170
       •   Mylex AcceleRAID 352
       •   Mylex eXtremeRAID 2000
       •   Mylex eXtremeRAID 3000

       Compatible Mylex controllers not listed should work, but have not been verified.

       mly — Mylex AcceleRAID/eXtremeRAID family driver

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

             devicepcidevicescbusdevicedadevicemly

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

             mly_load="YES"