Change_History_Readme.txt Driver File Contents (Linux_2.00.9-dup.zip)

This package contains version 2.00.9 of the MegaRAID SCSI drivers for Linux that currently support the following controllers:

320-1 [520]
320-2 [518]
I4 [511]
SATA 150-4 [523]
SATA 150-6 [523]
320-2X [532]
320-4X [531]

Binary driver images have been compiled for:

Redhat 8.0
Redhat 9.0
Redhat AS 2.1
Redhat EL 3.0
SLES 8.0
SuSE 8.1
SuSE 8.2

Source is included for other kernel versions.
RPM package included for kernel updates or installing into existing Linux systems.

Utilities included:

MegaMGR version 5.17 (manage controller within the operating system)
MegaMON version 3.4 (monitoring of RAID arrays, notification of status changes)

Note: IA64 systems not supported in this package.

______________________________________________________________________________________
--------------------------------------------------------------------------------------

Driver History

### Version 2.00.9
Thu Sep 4 17:49:42 EDT 2003
i. For extended passthru commands, 64-bit scatter-gather list and 64-bit
mailbox address must only be used if the controller supports extended
CDBs and 64-bit addressing and the kernel is configured to support
memory beyond 4GB.
With 2.00.8 and previous drivers, if the controllers supports extended
CDBs but the kernel does not support high memory - the driver prepares
a 32-bit sg list but the mailbox address is chosen to be 64-bit. This
causes FW to incorrectly read 32-bit (8 bytes) sg list as 64-bit
(12 bytes) sglist. This would cause IO from non-disk devices to fail

### Version 2.00.8
Wed Aug 27 16:40:05 EDT 2003
i. Make sure the value of number of statuses, completed command id array,
and the mailbox status fields are updated in host memory before we
read and interpret them. For this to happen - mailbox numstatus and
command id array's first element are invalidated. The ISR busy waits
till valid values are obtained in these two fields. Now since the
status field is between these two fields it is assumed that status
values is sane when write to numstatus and completed id array is
complete
ii. while returning from the ioctl handler for the SCSI passthru commands
a direct access was made to the user address. Now the user structure
is copied in before the required field is accessed.
iii. Remove redundant volatile casts from pending command counter pend_cmds.

### Version 2.00.7
Fri Aug 1 11:01:11 EDT 2003
i. Adapter lock re-definition so that patch for kernels w/o per host lock
is less intrusive

ii. While in abort and reset handling, check for non-empty pending list is
invalid. The intent is to wait for pending commands in FW to complete,
not the pending commands with the driver

### Version 2.00.6
Wed Jul 30 11:35:31 EDT 2003
i. Declare the function prototypes used for "/proc" within the compiler
directives #ifdef CONFIG_PROC_FS. Similary, move global/local variable
declarations and code fragments related to /proc within the directives.

ii. Initialize host->lock with adapter->lock.

iii. Wait for mailbox status to become valid

iv. Right structure is passed to FW for 4-span read configuration command.

### Version 2.00.5
Thu Apr 24 14:06:55 EDT 2003
i. Do not use repeated allocations for "pci_dev" for internal
allocations. Allocate the handle at load time and set the DMA mask for
allocations below 4GB.

ii. Remove superfluous definitions, mid-layer /proc entry and synchronous
commands

iii. Logical drive numbers were incremented in passthru structure after
random-deletion operation! Also, the logical drive deletion command is
issued in polled mode because of the racy nature of interrupt based
operation.

iv. Add support for Intel's subsystem vendor id

### Version 2.00.4
Thu Apr 17 15:58:58 EDT 2003
i. Do not put the completed SCSI commands in a list. Complete them to
mid-layer as soon as we have completed them and reclaimed our
associated resources

ii. Break ISR functionality in two portions. The lower half serves as
interrupt acknowledgment sequence for the firmware. This half can also
be called from other places in the driver, e.g., the abort and reset
handlers.

iii. New abort and reset handling. In these situations, driver allows more
time for the firmware to complete outstanding requests instead of
failing handlers right-away.

### Version 2.00.3
Wed Jan 29 09:13:44 EST 2003
i. Change the handshake in ISR while acknowledging interrupts. Write the
valid interrupt pattern 0x10001234 as soon as it is read from the
outdoor register. In existing driver and on certain platform, invalid
command ids were being returned.

Also, do not wait on status be become 0xFF, since FW can return this
status in certain circumstances.

Initialize the numstatus field of mailbox to 0xFF so that we can wait
on this wait in next interrupt. Firmware does not change its value
unless there are some status to be posted

ii. Specify the logical drive number while issuing the RESERVATION_STATUS

iii. Reduce the default mailbox busy wait time from 300us to 10us. This is
done to avoid a possible deadlock in FW because of longer bust waits.

iv. The max outstanding commands are reduced to 126 because that's the
safest value on all FW.

v. Number of sectors per IO are reduced to 128 (64kb), because FW needs
resources in special circumstances like check consistency, rebuilds
etc.

vi. max_commands is no longer a module parameter because of iv.

### Version: 2.00.2
i. Intermediate release with kernel specific code

### Version: 2.00.1i
Wed Dec 4 14:34:51 EST 2002
i. Making the older IO based controllers to work with this driver

### Version 2.00.1
Fri Nov 15 10:59:44 EST 2002
i. Release host lock before issuing internal command to reset
reservations in megaraid_reset() and reacquire after internal command
is completed.

_____________________________________________________________________________________
-------------------------------------------------------------------------------------

How to Create a DUD

In MS-DOS:

Extract files to a temporary directory, verify the image is in 8.3 format (i.e. image.img is okay, dud-image.img is not),
go to a command prompt in the temp directory, insert a floppy, and execute the command rwfloppy -w imagename

In Linux:

Extract files to a temp directory, then use execute the command dd imagename

After driver update disk is created type "linux dd" at the boot prompt to be prompted for drivers during the installation.

________________________________________________________________________________________________________________________________
--------------------------------------------------------------------------------------------------------------------------------

History of MegaMgr

*************
THIS RELEASE
*************

[ LSI: Linux Megamgr(Megamgr+Megamgr.bin) : Ver5.17 : Oct-15-2003 : AmitP ]
{

Changes with respect to Ver5.16 : Jul-16-2003

This release is associated with the following Ids.
[though may not be directly reported for Megamgr]. The following
Ids are related to the problems faced due to the coercion issue
on different applications.

(1) LSIID100004134
(2) LSIID100004755
(3) LSIID100004756
(4) LSIID100004741

This release takes care of the Coercion issue related to the
physical drive size.

(A)Now the utility gets the drive size based on the following algorithm.

(1) Fire new f/w cmd 0xA4/0x57 to get the coerced drive size
from the f/w.

(a) If the cmd is successful, take the coerced drive size from f/w.
(b) If the cmd fails, proceed to number (2)

(2) Get the drive size by firing SCSI Disk Capcacity cmd[0x03/0x25]

(3) Fire SCSI SEEK cmd[0x03/0x0B] & try to seek 32 sectors beyond
the drive size returned by (2)

(a) If SEEK cmd is successful, don't coerce the drive size returned by
(2)
(b) If SEEK cmd fails, coerce the drive size returned by (2).

Note: This is a major change in the application and this needs to be
tested thoroughly. It will affect all the operations on the
physical drive(s) and the logical drive(s).

All options of the utility needs to be thoroughly tested on the
following types of f/w.

(A) New F/w with 0xA4/0x57 cmd implemented.
(B) Old F/w which returns the coerce drive size
(C) Old F/w which returns uncoerced drive size.

Thorough testing needs to be done before delivering it to the customer.
Expect some issues will be present which were not detected by the
developer.

(B) As per Gerry's suggestion, now the application does not check
for the size of the physical drive(s), if the user opts for
CC/Init/Rbld.

TESTING PERFORMED:
------------------
Testing done on a 493 card with the following f/w on it.

(a) New f/w : 112G
(b) F/w with coercion
(c) F/w without coercion.

File Details:
-------------

megamgr : script to invoke the binary ( 1,356 bytes)
megamgr.bin : actual binary (584,244 bytes)

}

*****************************
PREVIOUS RELEASES
*****************************

[ LSI: Linux Megamgr(Megamgr+Megamgr.bin) : Ver5.16 : Jul-16-2003 : AmitP ]
{
Changes: With respect to Ver 5.15 : Mar 27,2003
--------

(1) [#DFCT 56461]

"Automatic Configuration" option is removed from the config menu
for 40-ld cards. 8-ld cards remain unaffected.

(2) Utility supports random deletion of logical drive on supporting f/w.

(3) [#DFCT79146]

There was a cosmetic issue with the previous version of the utility.
If the user tried to exit without initializing the newly created
logical drive(s), the warning message given to the user said

"..Intialize the logical drive.."
in place of

"..Initialize the logical drive.."

corrected in this release.

(4) Now the utility gives the option to come back from the CC/Init/Rbld
progress menu, without aborting the operation.

Earlier, if the user pressed <ESC> from the CC/Initialization/Rebuild
progress showing menu, the utility aborted the ongoing operation
after getting the confirmation from the user.

Now if the user hits <ESC> from the CC/Initialization/Rebuild, the utility
gives the following options to the user

"Abort Above Operation"
"Go Back Without aborting operation"
"View Progress Bar Again"

And acts based on the option selected by the user.

File Details:
------------
megamgr : script to invoke the binary ( 1,356 bytes)
megamgr.bin : actual binary (583,476 bytes)

Developer Level Testing:
------------------------

Maximum testing done through the demo utility.
Minimal testing done on the actual utility on a 493 card with
2 physical drives on it.

Suggested Testing:
------------------
Random deletion feature is supported for the first time in this
component. This needs to be tested thoroughly for all the possible
options and verify that everything is working as desired and nothing
is broken because of this.

}

[ LSI : Linux : Megamgr.bin : Ver 5.15 : Mar-27-2003: Timir]
{
Changes:
-Raid3 support removed from SATA6+SATA4 card per AdamSatterfield's
request. Earlier specs document also said so.
The issue was reported at 9:50am,3-27-03 and attended around 11:00am,
3-27-03.

Earlier per plan, we were offering no-Raid3 if the card returned a
value=7 from GetMaxSpeed firmware command(0xA4/0x2F) to disallow the
feature on newer firmwares, but continue its support on older
firmwares.

SATA4/SATA6 cards are returning value=6 , so the only way left with
megamgr is to disallow Raid3 if the card type is SATA4/SATA6 too at
individual card level(i.e. compilation time decision).

-Reconstruction menu disallows R3 selection for ineligible cards - so
the message is changed from

"Raid-3 selection is not allowed on U320 Cards
Press Any Key To Continue",

to
"Raid-3 selection is not allowed on this Card",
Press Any Key To Continue",
to make it applicable to SATA cards too.

-megamgr script file is now fitted with commands to clear screen on
exit fromt the utility so that 'unicode stop' related msg/commands
are not visible on the screen.

Test Report:
Tested the above change on a SATA4 card in the lab for the above
change. Nothing beyond.

Test team should test the component thoroughly as said in release note
of version 5.14.

File Details:
1.tgz 240,608 03-27-03 11:52A

File '1.tgz' contains 'megamgr' + 'megamgr.bin' files
Copy 1.tgz to linux machine and extract megamgr + megamgr.bin files thru
'tar xvfz ./1.tgz' option and then run './megamgr' or 'megamgr' if megamgr
is copied in a valid path.
}

[ LSI : Linux : Megamgr.bin : Ver 5.14 : Mar-25-2003: Timir]
{
Changes:
-SATA-4-150 card support is added to show it in 'Port-x' form in places
for 'Channel-x Target-yy'.

-Battery is now in adapter menu per new scheme adopted by LSI to avoid
repeated variety of releases for different cards ( with battery , without
battery ). This option appears only on cards that have battery on it. For
cards with no battery this option will not show up at all. A card is
considered to have battery if its battery pack + battery module are present
at the time of going to adapter menu.

-Spelling mistake correction :
"Intialize" word is replaced by "Initialize"
this was evident at exit after creation of some logical
drive and leaving them uninitialized in that session. This was recently
reported by one OEM in Mar-2003 - so it's corrected.
-Default write policy for 518/520 card is changed as
Follow write policy of last logical drive created in this session
if no such logical drive
then
if 518/520 has battery and card is not in cluster mode
then WRITEBACK
else WRITETHRU
endif
endif
This is per Daniel Tesfu's request of 01-07-2003 for NEC.

Developer's Test Report:
:tested thru simulation in demomgr - nothing beyond
:not tested on SATA4 in absence of card and needed hardware and driver
:not tested on 518/520 at all in absence of related hardware resource
:Run megamgr on a 471-card with 2-SCSI Disks on it for init/config/cc
operations

Testing Suggested:
: Treat this release as a new release for SATA-4- product and so check the
utility menu-by-menu for any issues that might need be addressed at LSI.

File Details:
1.tgz 240,588 03-25-25 3:04P 1.tgz

This file contains 'megamgr' + 'megamgr.bin' files
Copy 1.tgz to linux machine and extract megamgr + megamgr.bin files thru
'tar xvfz ./1.tgz' option and then run './megamgr' or 'megamgr' if megamgr
is copied in a valid path.

}
[ LSI : Linux : Megamgr.bin & Megamgr : Ver 5.13 : Feb-03-2003: AmitP]
{
Changes:
--------
With respect to Ver 5.12 : Oct-11-2002

(1) There was a bug in the previous version of the utility.
If back-ground init was going on one logical drive, then
if the user tried to start check consistency/Init on some other
logical drive, it was failing.
Corrected in this release.

(2) Disallow R0-spanning as it's useless.
[Requested by Timir : 12-09-2002]

(3) Disallow partial array spanning.

Requested by Dougg : 12-09-2002.

(4) Allow the user to view ongoing REBUILD on all physical drive(s).
Earlier, user had to select the physical drive in the menu and then
select the view rebuild option to see ongoing rebuild(if any) on that
physical drive.

Now the utility gives the option to the user to view ongoing REBUILD on
ALL physical drive(s) on which REBUILD is going on.

[Requested by Farhan : 12-09-2002]

(5) There was a bug in the previous version of the utility. For getting the
predictive failure, it was firing 0x65 cmd on 40-ld cards also.

Predictive failure for 40-ld card is now found out from command
0xA4/0x0F on 40-ld card, 0x65 cmd for 8-ld card.

(6) Cosmetic change:
The utility gives the option to the user to view ongoing Init/BI-CC
by pressing F6/F7 keys respectively. If no BI-CC is going on any
logical drive, then earlier the utility was giving the message

"No Logical Drive Is Currently In Check Consistency State"

now the message is changed to

"No Logical Drive Is Currently In Check Consistency or Background Init State",

TESTING PERFORMED:
------------------
Most of the testing done through demo utility at developer's end.
Performed some minimal testing on a 493 card.

File Details:
-------------

MegaMgr : Script to invoke the binary : 1,277 bytes
MegaMgr.bin: Actual binary for the meagmgr: 564,244 bytes

}

[LSI : Linux : Megamgr.bin & Megamgr : Ver 5.12 : Oct-11-2002: AmitP]
{
Changes:
--------
With respect to Ver 5.11 : Aug-12-2002

(1) Changes made in the script "megamgr" to make it run
on Red Hat Linux 8.0
Earlier, display related problems were seen on Red Hat Linux 8.0.
These are removed in this release.

(2) As per request from Lee Vermont of LSI, Cluster value
(Standard/Cluster) is shown on the banner now, after the adapter
number.

Note: For IDE cards, we don't show the cluster value on the banner.
----

(3) As per request from Lee Vermont of LSI, display of initiator id
is added under adapter menu.
The value is only displayed and user is not allowed to change the value.

Objects->Adapter-x->
Gives the value of initiator id also now.

(4) The utility gives the user the option to view ongoing Init/CC
now.

Affected Menus are :

Managment Menu->Initialize->
and
Managment Menu->Check Consistency->

Now the bottom message also gives the option to the user to view
ongoing Init/CC by pressing F6/F7 keys respectively.

If no init/cc is going on, the message is given to the user.
Once the user enters the viewwing of Init/CC, the "ESC" key
has got the same functionality as in the normal init/cc menu.

(5) The utility also supports the SATA-6-150 cards now.

(*) A card will be treated as SATA card if
Vid/Did : 0x1000/0x1960
ssVid/ssDid : 0x1000/0x0523

(*) All the features which are
NOT allowed on IDE card, will also be NOT allowed on SATA card.

For example, On a SATA card :

(i) Battery Back Up -> NOP
(ii) SCSI Channel -> NOP
(iii)Format option is not supported for physical drives
(iv) In physical property showing box,"Media/Other Erros","SCSI Standard"
and "Predictive Failures" are not shown

(*) For SATA cards, banner will show "SATA:" in place of "(IDE)"

(*) Cluster state in banner will not be shown for SATA cards.

(*) In place of "Channel-x" "Port" will appear at all config/phys drv
menus for SATA card.

(*) Menus related to physical drive operation will show "Port-xx" in place
of "Ch/Id"
Like in PhysDrv Online/Offline/Rebuild/Rebuild Progress menu.

(*) While scanning the drives, the utility will scan for id 0 to 5 only
for SATA card and show the word "Port-x" in place of "Ch-x, Id-y".

Changed messages are for scan/spin-up/inquire spin-up/disk capacity

(*) In the bottom window box, in Config/Phys Drv related menus, "Port-x"
will be shown in place of "Ch-x Id-y".

TESTING PERFORMED:
------------------
Change no. 2,3,4 tested on a system with one 493 card on it.
SATA-6 related testing could be done only through demomgr,
as the the card with proper Vid/Did/ssVid/ssDid was not available
at developers end for testing.

File Details:
-------------

MegaMgr : Script to invoke the binary : 1,277 bytes
MegaMgr.bin: Actual binary for the meagmgr: 562,708 bytes

}

[LSI : Linux : Megamgr.bin & Megamgr : Ver 5.11 : Aug-12-2002: AmitP]
{
Changes:
--------
With respect to Ver 5.10 : Jul-19-2002

1. Disallow R3/R30 on U320-boards per request from PeterJ on 7-24-02
A Board is treated as U320 Board if both the conditions are true.
(a) MiscCmd/GetMaxSpeed(0xA4/0x2F) is successful
(b) The above cmd returns 0x07.
While reconstruction also, the utility does not allow the user to
create a Raid-3 on U320 bards.

2. Partial arrays are disallowed for boards in cluster mode.
(As per the request made by Lee Vermont : 07-24-02)

TESTING PERFORMED:
------------------
Testing done on a system with one 471 card for change no 2.
U320 related testing done through demomgr.

File Details:
-------------

MegaMgr : Script to invoke the binary : 690 bytes
MegaMgr.bin: Actual binary for the meagmgr: 555,092 bytes
}

[LSI: Linux : MegaMgr.bin : Ver 5.10 : Jul-19-2002: AmitP]
{
Changes:
--------
With respect to Ver 5.09 : Jan-25-2002

1. Support of x-term added.
Now the utility works on the normal as well
as the x-term of Linux.

2. Plus it has got enhancements/fixes done for other
OEMs/OSs during the time between the previous
release and this release.

Compiled on : Red Hat Linux release 6.2
------------

TESTING PERFORMED:
------------------
Tested the utility on a 471 card to see nothing is broken.

For x-term support, testing done on a normal terminal of
Red Hat Linux release 6.2.

And on a normal and x-term of Red Hat Linux release 7.2.
Further testing is suggested.

File Details:
-------------
MegaMgr : Script to invoke the binary : 690 bytes
MegaMgr.bin: Actual binary for the meagmgr: 553,812 bytes

}

[LSI : Ver 5.09 : Jan 25,2002 : Priya]
{
LSI: linux megamgr ver 5.09 1-25-02

Generic Changes:

1. SCSI Standard and QTag info not shown for IDE RAID card in phys drv
properties menu since 8-8-01 (Timir).

2. TargetId above 1 are not shown in phys drive menus as they make no
sense in the context of IDE-RAID card

3. Adapter type string in adapter menu: is now shown upto 40-chars
(earlier upto 32-chars) for all megamgrs.

4. Background Initialization/Consistency Checking is distinguished thru
0xA4/0x13 firmware command on eligible firmwares and distinctive message
is shown during selection of logical drive for Initialization/Consistency
checking.

Bug Fix:

a) Physical drive properties for "Error Counter" were showing wrong
values on T5 card - it was found to affect other cards also - fixed
in a generic way for all OEM/all megamgrs.

b) #logical drives configured string was not getting properly
initialized ending showing "old information" or "other card's
information" - corrected in this.

This was visible if you go to "Main->Initialize/Check Consistency"
immediately after making some configuration(different number of
logical drives than last one on this card).

c) Rebuild menu had problem in selection of FAILED drive for rebuild
candidate if the drive was a fiber device. Cursor movement was erratic.

d) There was a bug in automatic configuration function. Bug was removed
in earlier release of DELL on LINUX. Recompiled the source for AMI on
DOS to reflect the generic changes done to remove the bug.

File Details:
-rwxr-xr-x 1 root root 690 Jan 22 13:42 megamgr
-rwxr-xr-x 1 root root 648012 Jan 25 06:10 megamgr.bin
megamgr and megamgr.bin need be copied on Linux Machine
in the same directory and then marked
executable before running them.

TESTING DONE AT DEVELOPER'S END:
- Enhancements were tested by simulation program called demomgr.
- Change related testing was done via general navigation on the
simulator (demomgr) and with two RAID cards (a 493 card with RT64 f/w)
and a 438 card with GH89 f/w on it.
- Navigation of different menus was done and looked for any screen
corruption issues and found none.
- Compiled,Linked and Tested on RedHAt Linux 7.0.
}

[ AMI : Ver 5.08 : Aug 03,2001 : Priya]
{
AMI: linux megamgr ver 5.08 8-3-01
It takes care of proper display of IDE in banner according to the adapter
type. AMI version corresponding to DELL version 5.13 (07-24-01) released
by Amit Pandya.

File Details:
-rwxr-xr-x 1 root root 690 Mar 29 14:38 megamgr
-rwxr-xr-x 1 root root 549364 Aug 03 09:46 megamgr.bin

TESTING DONE AT DEVELOPER'S END:
Only the banner related stuff and the general view are checked thru demomgr
and megamgr utility.
}

[ AMI : Ver 5.07 : Mar 30,2001 : Timir]
{
AMI: linux megamgr ver 5.07 3-30-01
It takes care of CPU -hogging issue ( as reported by AMI-Test group thru
some Linux program 'top' ). Earlier version was having this problem because
of its constant wait for keyboard input from user.

File Details:
-rwxr-xr-x 1 root root 690 Mar 29 14:38 megamgr
-rwxr-xr-x 1 root root 509364 Mar 30 09:24 megamgr.bin

TESTING DONE AT DEVELOPER'S END:
Only the time related stuff is checked thru 'top' program during running
of megamgr on pressing a key and on no-pressing-of-key. Nothing beyond.

}

[ AMI : Ver 5.06 : Feb 28,2001 : AmitP]
{
Please refer to release details of Ver 5.05 : Feb 27, 2001
before going through this release.

Ver 5.05 incorporates some major changes in the utility. One change
was missing in 5.05, Release 5.06 only describes that change.

Details of 5.05 are given in this file, just below the details of
this release.

Changes : With respect to Ver 5.05 Feb 27,2001

1. DRAM size of 40-ld card is now shown upto 65535MB( earlier upto
255MB ) and upto 255MB on 8-ld card.

File Details:
--------------
This release contains two files.

(a) megamgr : Script ( 690 bytes)
(b) megamgr.bin: Binary (509,172 bytes)

TEST REPORT:
------------
Change related testing done only through demo utility.
Further testing is suggested.

}

[ AMI : Ver 5.05 : Feb 27,2001 : AmitP]
{
Changes:
--------
(With respect to ver 5.04 : May 24,2000)

1. Utility made compliant to new driver specifications
Ver 1.14B (as provided by VenkateshR)

(Document : Specification for Linux Application Rev 1.1/1.2)

Now the utility uses the MIMD IOCTL interface to talk
with the driver/firmware.

Old SCSI IOCTL interface is not supported now.

2. Utility comes in a form of a script now.
The script takes care of creation of node and after that
it calls the actual binary.

This release contains two files.

(a) megamgr (script) (b) megamgr.bin (binary)

Both of these should be present in the same directory
for invocation.

Change the execute permissions of script & binary by:

chmod +x ./megamgr
chmod +x ./megamgr.bin

And then invoke utility as:

./megamgr

The script "megamgr" is in UNIX format, care must be taken
not to edit this file on DOS systems else it will be converted
to DOS format.

3. Driver version 1.14 or above is a must to run the utility.
If lower version of driver is used, utility gives the message
and quits.

4. Configuration options:
----------------------
Automatic Configuration
Easy Configuration
New Configuration
View/Add Configuration
Clear Configuration
----------------------

are supported in the utility now.

5. Logical drive size - Once selected could not be increased in
New logical drive configuration menu.
Changed this feature to allow to reselect the free available
space at will.

i.e.

Logical drive size selection field in NewLogicalDriveConfiguration
menu is enhanced to allow user-mistake-and-go-back-to-leftover
-size-of the array.

e.g.
If a logical array has 2000MB and user selects 100MB as size
and again changes mind(before hitting ACCEPT option) and goes
back to size option to make it bigger than 100MB - it used to
give an error "Invalid logical drive size..." with older megamgr.
This is now allowed.

6. In earlier versions, if user tried to change already ONLINE or
HOTSPARE drive to online state, different messages were given that
the drive cann't be made online.
Now it gives a single message.

"Only FAILED Drive can be Changed to ONLINE"
"Press Any Key To Continue..."

File Details:
--------------
This release contains two files.

(a) megamgr : Script ( 690 bytes)
(b) megamgr.bin: Binary (509,172 bytes)

TEST REPORT:
------------
Tested the utility on a system with

a. one 471 & one 493 card
b. one 471 & one 438 card
c. one 471, one 493 & one 438 card

(Driver Version 1.14B)

Tried to test with 428 card, but the driver gives core
dump while doing "insmod".

--------------------------------------------------------
Utility Checks for driver version(which is in form of
decimal). If the driver version is lower than 1.14, it
gives the messages and quits.

Utility is not tested with Version 1.14A of driver.

--------------------------------------------------------

Further testing is suggested.
}

[ Linux Megamgr: AMI: Ver 5.04 : May 24-2000 : Rajesh Prabhakaran]
{
List Of Changes :

-To Check whether Driver Version is Greater then 1.07 If Version is less
the 1.08 this utility will not detect any adapters.

-To provide Substitute Keys
<F1> as <Shift> <1>
<F2> as <Shift> <2>
<F3> as <Shift> <3>
<F4> as <Shift> <4>
<F5> as <Shift> <5>
<F6> as <Shift> <6>
<F7> as <Shift> <7>
<F8> as <Shift> <8>
<F9> as <Shift> <9>
<F0> as <Shift> <0>
UPARROW as k (Just press k and no Shift or Ctl keys)
DOWNARROW as j (Just press j and no Shift or Ctl keys)
RIGHTARROW as l (Just press l and no Shift or Ctl keys)
LEFTARROW as h (Just press h and no Shift or Ctl keys)

TEST REPORT:
- Tested with Mega Raid device driver version 1.07 and 1.08
- Substitute keys checked.

FILE DETAILS
Size Date File Name
499572 May 24 17:23 megamgr

}

[ Linux Megamgr: AMI: Ver 5.03 : April 12-2000 : Timir Pandit ]
{
LIST OF CHANGES: ( With respect to Linux Megamgr ver 5.02 Feb-14-2000 )
-Make Hotspare is now working. Earlier it was crashing.

-Reconstruction progress reporting had some bug(in case of reconstruction
error it could show some wrong info ) - corrected .

-Searching Adapter phase shows a message and a revolving 'swing' if there is
lot of delays in it.
This is more evident if you run megamgr in absence of the driver.

-Running megamgr in absence of driver was unnecessarily allowing entry to
main menu and then exiting. Corrected in this.

-The utility is using now STATIC library to avoid linker issue (with dynamic
/shared libararies ) under different Linux flavors.

-It now Locks the firmware cmd's data area for ioctl protocol for its
memory use by the driver as per recommendation from driver developer
( Venkatesh of AMI-India).

-It allows the utility to be executed by super user only.

LINUX MEGAMGR FEATURES:
Supports 8-ld and 40-ld cards
RECONSTRUCT only RAID-x to RAID-y - it does not allow capacity
expansion option

FILE DETAILS
'megamgr' is a stripped uncompressed binary file(original size was
around 1300KB ).

-rwxr-xr-x 1 root root 498388 Apr 12 16:16 megamgr

TEST REPORT:
Tested minimally with one 471-card.
}

*****************************
PREVIOUS RELEASES
*****************************

[ Linux Megamgr: AMI: Ver 5.02 Feb-14-2000: Timir Pandit ]
{
LIST OF CHANGES:
1. Color related improvement for speed and esthetics.
It speeds up the overall execution of 40-ld megamgr
2. Correction made for progress bars of init/rbldrate menu.
3. Correction made for color/display of Horizontal Bar in phys
drive menu
4. Configuration Option is no more available
5. Make On/Off line : phys drv option shows drive number now in
Decimal if it's not on fiber chnl
in Hex along with 'h' suffix if it's on fiber chnl
This will be effective in all future megamgrs automatically.

6. Show cursor position alwyas in physical drive menu to indicate
the current physical drive. This helps in a situation where
coloring/highlighting is not that much prominent.
This is right now enabled for Linux version - it can be extended to
other OS also.

7. Show Warning message in the Linux path on selection of
FAIL-Drive/Online drive in phys drive menu.

Earlier these were offed in pwin.c file.

Co-ordinates of 'confirmation window(Y/N)' are also changed to
accommodate these changes.
In case of "NO" option selected by user it comes back to prev
menu to avoid screen corruption - Timir: 2/14/00

Only Linux Megamgr.

8. Spinning up device info was being shown with 'h' suffix on SCSI
chnl - corrected in this.

TEST REPORT:
Testing was limited to one 428-card with 2 x 35GB disks on it.

LIBRARY USAGE:
It uses dynamic/shared gnu library - that became issue of
compatibility on other Linux versions.

}

________________________________________________________________________________________
----------------------------------------------------------------------------------------

History of Linux Monitor

*****************
[ This Release ]
*****************

[Release ver 3.4: Sep-16-2003:]
{
Version 3.4: MegaServ and Version 3.1: MegaCt32
Clearcase Request Id: LSID100004285

Total of 5-files make this release.
install : installation script
deb_rmon : Debian linux specific raidmon : Shell script(new)
raidmon : raid monitor installation stuff : Shell script
MegaServ : Ver 3.4 Sep-16-2003 : Binary
MegaCt32 : Ver 3.1 Sep-16-2003 : Binary

MegaCt32 is copied as MegaCtrl during installation.

FILE DETAILS: ( As seen on Linux machine )
-rwxr-xr-x 1 root root 382124 Sep 16 17:20 MegaCt32
-rwxr-xr-x 1 root root 556260 Sep 16 17:20 MegaServ
-rwxr-xr-x 1 root root 825 Sep 16 17:20 deb_rmon
-rwxr-xr-x 1 root root 4552 Sep 16 17:20 install
-rwxr-xr-x 1 root root 1229 Sep 16 17:20 raidmon

These are released as lsi_v34.tgz( Linux Tar zipped format ).

LIST OF CHANGES:
Introduced delay in the monitor program after firing the commands, to resolve the driver performance
issue raised by NEC
}

**************************
[ Previous Releases ]
**************************

[Release ver 3.3: Aug-01-2003:]
{
Version 3.3: MegaServ and Version 3.1: MegaCt32
Clearcase Request Id: LSID100003287

Total of 5-files make this release.
install : installation script
deb_rmon : Debian linux specific raidmon : Shell script(new)
raidmon : raid monitor installation stuff : Shell script
MegaServ : Ver 3.3 Jul-31-2003 : Binary
MegaCt32 : Ver 3.1 Jul-31-2003 : Binary

MegaCt32 is copied as MegaCtrl during installation.

FILE DETAILS: ( As seen on Linux machine )
-rwxr-xr-x 1 root root 382124 Jul 31 17:20 MegaCt32
-rwxr-xr-x 1 root root 556228 Jul 31 17:20 MegaServ
-rwxr-xr-x 1 root root 825 Jul 31 17:20 deb_rmon
-rwxr-xr-x 1 root root 4552 Jul 31 17:20 install
-rwxr-xr-x 1 root root 1229 Jul 31 17:20 raidmon

These are released as lsi_v33.tgz( Linux Tar zipped format ).

LIST OF CHANGES:
1) Sense key check for SMART events is removed because some f/ws do not return proper value
(2) Default SMART POLLING STATE at start-up is, ON with value of 60 seconds interval. This is
for LSI only.
(3) Compilation flag CFLAG_REPORT_SMART_ONEDEV_ONCE is made generic for all OEMs.
}

[Release ver 3.2 : Jul-18-2003:]
{
Version 3.2: MegaServ and Version 3.0: MegaCt32
Clearcase Request Id : LSIID-10000-1716

Total of 5-files make this release.
install : installation script
deb_rmon : Debian linux specific raidmon : Shell script(new)
raidmon : raid monitor installation stuff : Shell script
MegaServ : Ver 3.2 Jul-18-2003 : Binary
MegaCt32 : Ver 3.0 Jul-18-2003 : Binary

MegaCt32 is copied as MegaCtrl during installation.

FILE DETAILS: ( As seen on Linux machine )
-rwxr-xr-x 1 root root 382124 Jul 18 17:20 MegaCt32
-rwxr-xr-x 1 root root 555716 Jul 18 17:20 MegaServ
-rwxr-xr-x 1 root root 825 Jul 18 17:20 deb_rmon
-rwxr-xr-x 1 root root 4552 Jul 18 17:20 install
-rwxr-xr-x 1 root root 1229 Jul 18 17:20 raidmon

These are released as lsi_v32.tgz( Linux Tar zipped format ).

LIST OF CHANGES:
Disabled “Battery Module/Pack missing” messages for LSI.
}

[Release ver 3.1 : Jun-19-2003:]
{
Version 3.1: MegaServ and Version 3.0: MegaCt32

There was an issue reported with the Linux Monitor. It used to get killed
after an indefinite period of time.

It was found out that it was happening due to the way "daemon" process
was created by this program.

In this release, changes have been made in the code to invoke the daemon
process in a different way.

Changes done both in MegaServ & MegaCt32(MegaCtrl).

RELEASED FILES
Total of 5-files make this release.
install : installation script
deb_rmon : Debian linux specific raidmon : Shell script(new)
raidmon : raid monitor installation stuff : Shell script
MegaServ : Ver 3.1 Jun-19-2003 : Binary
MegaCt32 : Ver 3.0 Jun-19-2003 : Binary

MegaCt32 is copied as MegaCtrl during installation.

File deatails: (As seen on Linux m/c)
MegaServ : 434,932 bytes
MegaCt32(MegaCtrl) : 328,692 bytes
install : 4,552 bytes
deb_rmon : 825 bytes
raidmon : 1,229 bytes

These are released as lsi_v3p1.gz( Linux Tar zipped format ).
}

[Release ver 3.0 : 04-10-03: ]
{
RELEASED FILES
Total of 5-files make this release.
install : installation script
deb_rmon : Debian linux specific raidmon : Shell script(new)
raidmon : raid monitor installation stuff : Shell script
MegaServ : Ver 3.0 Apr-10-2003 : Binary
MegaCt32 : Ver 2.9 Apr-10-2003 : Binary

MegaCt32 is copied as MegaCtrl during installation.

FILE DETAILS: ( As seen on Linux machine )
-rwxr-xr-x 1 root root 381804 Apr 10 10:27 MegaCt32
-rwxr-xr-x 1 root root 555940 Apr 10 10:27 MegaServ
-rwxr-xr-x 1 root root 825 Apr 01 11:07 deb_rmon
-rwxr-xr-x 1 root root 4552 Mar 13 15:05 install
-rwxr-xr-x 1 root root 1229 Mar 13 15:05 raidmon

These are released as lsi_v30.tgz( Linux Tar zipped format ).

LIST OF CHANGES:

1) Some of the messages with given id# are routed (along with logging in /var/log/megaserv.log)
to the file /var/log/messages also, using syslog library function.
2) Support of SATA controllers added and the Ch-xx id-yy mechanism is changed to Port-yy.
3) A small bug pertaining to memset(&bgndInit, 0, sizeof(bgndinit)) is changed to memset(bgndInit, 0, sizeof(bgndinit)) in the first argument.
}

[Release ver 2.9 : 11-27-02: ]
{
RELEASED FILES
Total of 5-files make this release.
install : installation script
deb_rmon : Debian linux specific raidmon : Shell script(new)
raidmon : raid monitor installation stuff : Shell script
MegaServ : Ver 2.9 Nov-27-2002 : Binary
MegaCt32 : Ver 2.9 Nov-27-2002 : Binary

MegaCt32 is copied as MegaCtrl during installation.

FILE DETAILS: ( As seen on Linux machine )
-rwxr-xr-x 1 root root 391304 Nov 27 02:51 MegaCt32
-rwxr-xr-x 1 root root 512688 Nov 27 02:51 MegaServ
-rwxr-xr-x 1 root root 825 Nov 26 11:19 deb_rmon
-rwxr-xr-x 1 root root 4552 Nov 26 09:56 install
-rwxr-xr-x 1 root root 1229 Nov 22 12:07 raidmon

These are released as lsi_v29.tgz( Linux Tar zipped format ).

LIST OF CHANGES:

Utility now reports the Rebuild and initialization progress

}

[Release ver 2.8 : 02-15-02: ]
{
RELEASED FILES
Total of 5-files make this release.
install : installation script
deb_rmon : Debian linux specific raidmon : Shell script(new)
raidmon : raid monitor installation stuff : Shell script
MegaServ : Ver 2.8 Feb-15-2002 : Binary
MegaCt32 : Ver 2.8 Feb-15-2002 : Binary
MegaCt32 is copied as MegaCtrl during installation.

FILE DETAILS: ( As seen on Linux machine )
-rwxr-xr-x 1 root root 354392 Feb 15 07:29 MegaCt32
-rwxr-xr-x 1 root root 452520 Feb 15 07:29 MegaServ
-rwxr-xr-x 1 root root 825 Feb 15 07:29 deb_rmon
-rwxr-xr-x 1 root root 3638 Feb 15 07:29 install
-rwxr-xr-x 1 root root 1229 Feb 15 07:29 raidmon

These are released as lsi_v28.tgz( Linux Tar zipped format ).

LIST OF CHANGES:
1. MegaServ now gives distinctive message for "Consistency checking" and "Background
initialization" ,if firmware supports the command 0xA4/0x13.

2. "-LogProgXXX" option is supported in ./MegaCt32 to allow user specify consistency
checking progress(%-age) reporting interval for ./MegaServ.
XXX=0 .. any +ve integer , implying number of seconds.
The default setting for log progress reporting interval is every 15-minutes.

3. MegaServ program now reports completion of consistency checking process on the
logical drives on fulfillment of any of the following conditions that means
‘change in consistency state’ such as
a) consistency checking progress reached 100%
b) consistency checking is aborted(either by this program or by some other
program).
This case cannot be handled differently as the utility does not have any information
otherwise and it tells user that running activity of consistency checking is OVER.
It should be considered to be the meaning of COMPLETION.

4. Allow user to disable the mailing feature if system mailing is not installed in
some Linux (such as Debian Linux) to avoid any screen corruption.

5 Default progress time is changed from 15 minutes to 900 seconds (as per NT monitor).

}

[GENERAL INFO : Release ver 2.8 : 02-15-02: ]
{
HOW TO INSTALL
INSTALLATION PROCEDURE
Install the new component as follows
a) copy all the files in a temporary directory
b) rename file megaserv as MegaServ and "megact32" as "MegaCt32"
c) Run "install" script as "./install"
It will copy the needed files to the respective directory.

Now you can run the MegaServ program thru
MegaCtrl -start

For other help, type "MegaCtrl -help"

OVERALL FEATURES OF LSI LINUX MONITOR V2.8
:The MegaServ is compliant to MegaRAID MIMD driver of Linux.

:Supports upto 12-adapters in total (8-logical drive + 40-logical
drive cards all inclusive).

:Allows running of check consistency on scheduled hour thru
specification of "consistency schedule" thru option of "MegaCtrl"

:Reports change in state of "logical drive"
In case of "number of logical drive" change detected, it skips the
comparison of logical drive state change during that cycle of polling.

:Reports change in state of "Physical drive"
In case of drive detected in "FAILED" state, it reports "reason of
such failure",if information is available from firmware.

:Polls SMART failure related events.
Uses new method of extended-sense-information,if available on
40-ld firmware side. Else uses old commands to get SCSI-DUMP data.

:Reports "Media Error + Other Error" counters of a physical
drive if any nonzero value found or the error counter value changes.
These error counters are reset on start of service and also on
reaching a threshold value of "20"( Total of MediaError+OtherErrors ).

:Logs different events in file "/var/log/megaserv.log"
with date & time stamp

:Sends mail to root for different events with date & time stamp

RESTRICTIONS
:MegaRAID Linux driver must be installed for successful running of this
utility.

:Service program polls different components one by one and then
sleeps for about 10-seconds(or more). If any event occurs more than
once during this 10-seconds period, then it will be able to report
only the last change during its actual polling of data.

:At scheduled hour, it runs check consistency on all redundant
optimal logical drives on all adapters. If by any chance the boot
drive is one of such drive, then during the running of check
consistency , the machine might be quite slow in response,depending
on i/o activities.

}

[LINUX : megamonitor - Ver 2.6 : May-02-2001 ]
{
MEGAMONITOR For Linux (MIMD) - Ver 2.6
**************************************

2nd May 2001

RELEASED COMPONENTS
*******************
1. Executables : - MegaCtrl, MegaServ
2. Installation Sripts : - raidmon, install

File Size Date
*********************************************************
1. MegaCtrl 28605 bytes 05/02/01
2. MegaServ 66868 bytes 05/02/01
3. raidmon 789 bytes 05/03/01
4. install 454 bytes 05/02/01

Release Version 2.4 - 15 April 2001
***********************************

1. ADDITIONS:
1.The Mailing of Events is made into optional,(i.e) user can Enable or Disable the Mailing facility.
2.The Scripts are enhanced with Creation of device node for MIMd driver.

2. DELETIONS:

3. CHANGES:
1. The Text file used is changed from /tmp/temp to a specific file related to monitor.
2. The Display of startup Messages are formatted in seperate lines.

4. BUGS FIXED:
1. The raidmon script is modified to be checked with chkconfig
2. The MegaServ is made to disassociate from terminal.

HOW TO INSTALL
**************

1. Run install as ./install from the directory in which deliverables are present.

Testing of the deliverables.
****************************

Limited testing of the deliverables were carried out on the following configuration.

MegaRAID Driver Version : 1.14g
Operating System : Redhat Linux 6.2

Known Limitations
*****************
1. The size of the log files is limited(system dependent).
2. The Linux monitor gets the state change for every 1 sec. In case, any process like initialization gets over before this one sec, then the monitor will not be able to log on the state change.
}

____________________________________________________________________________________________________________________________________________________________________________________________________
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Megaraid.tgz Readme

egaraid.tgz is the compressed tar file for the driver source code. This code
should be placed in /usr/src/linux-kernel-version/drivers/scsi directory for
compling the driver module.

Note that the code is not common for all kernels. It is generic code and must
be modified a bit for various kernels. The reference kernel for generic driver
is 2.4.21-4.EL (AS3.0)

There is an associated patch and a readme file in each supported kernel
subdirectory. Please refer to these two files to find out how to apply the
patch and compile on respective kernel.

_______________________________________________________________________________________
---------------------------------------------------------------------------------------

Source is provided for expert users only. LSI Logic provides only limited support on the recompilation of kernels.

Download Driver Pack

Change_History_Readme.txt Driver File Contents (Linux_2.00.9-dup.zip)

Recent Help Articles

More Popular Downloads

How To Update Drivers Manually

Recent Help Articles

More Popular Downloads