LSI (MPT Internal) RAID Engines

Top Previous Next

Benefits of Directly Querying LSI RAID Controllers

•

Use the software to assess RAID health remotely, and not be dependent on a BIOS-based program, or a utility that only runs on the host console. Since the output can easily be parsed and scripted, the administrator can implement a phone-home system based on specific parameters. Obviously this can't be done from a BIOS because the host isn't even running an O/S. Limitations in LSI-supplied windows-based tools prevent you from creating customized actions based on health.

•	The software can tell you serial numbers of disk drives, the controller, and firmware/driver revisions. SMARTMon-UX frees you from having to take a system down to gather patch/BIOS/driver information

•

If you are in a high-security area, use the -zdq command as part of a polling daemon that reports that all of the disks behind a RAID controller are online and have not been taken. We have customers who have "national security" implications that use the software to make sure that nobody has stolen a disk drive. Remember if you have RAID5, then somebody could take a disk drive, and the host would run normally on the degraded LUN. Our software detects disk drive removals behind LSI-based RAID controllers.

•	Do you have newer 6Gbit SAS disks, and/or SATA drives? Is everything synced up to highest supported speed? Look at the Link Max/min rates to find out.

The results below show /etc/smartmon-ux -zd /dev/es/ses0

(You must give it the device name for something that is attached to a LSI internal RAID controller. In this case, the controller is the LSISAS3800X card, which is a JBOD controller.)

Discovered LSILOGIC SYM3600-SAS S/N "0617053320" on /dev/es/ses0 [SES] (Enclosure Services)

Discovered (1) Controllers:

Port #0. /proc/mpt/ioc0 RAID SAS1068 A0 MPT 105 Firmware (1.16.00.01) IOC 0

x86 BIOS image's version: MPTBIOS-6.12.00.00 (2006.10.31)

Bus/Dev/Fun Board Name Board Assembly Board Tracer

130 3 0 SAS1068

SAS1068's phylinks are (Port 0,1,...,8): 3.0 G, 3.0 G, 3.0 G, 3.0 G, down, down, down, down

Firmware Settings

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

SAS WWID: 500605b0000488c0

Multi-pathing: Disabled

SATA Native Command Queuing: Enabled

SATA Write Caching: Enabled

SATA Maximum Queue Depth: 32

Device Missing Report Delay: 0 seconds

Device Missing I/O Delay: 0 seconds

Phy Parameters for Phynum: 0 1 2 3 4 5 6 7

Link Enabled: Yes Yes Yes Yes Yes Yes Yes Yes

Link Min Rate: 1.5 1.5 1.5 1.5 1.5 1.5 1.5 1.5

Link Max Rate: 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0

SSP Initiator Enabled: Yes Yes Yes Yes Yes Yes Yes Yes

SSP Target Enabled: No No No No No No No No

Port Configuration: Auto Auto Auto Auto Auto Auto Auto Auto

Target IDs per enclosure: 1

Persistent mapping: Enabled

Physical mapping type: None

Target ID 0 reserved for boot: No

Starting slot (direct attach): 0

Target IDs (physical mapping): 0

Interrupt Coalescing: Enabled, timeout is 16 us, depth is 16

Persistent Mappings

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

Persistent entry 0 is valid, Bus 0 Target 0 is PhysId 5000c5000040f53d

Persistent entry 1 is valid, Bus 0 Target 1 is PhysId 0523270354666c41

Persistent entry 2 is valid, Bus 0 Target 2 is PhysId 0523270354666f3e

Persistent entry 3 is valid, Bus 0 Target 3 is PhysId 0523270354666d4b

Persistent entry 4 is valid, Bus 0 Target 4 is PhysId 0523270354666c4a

Persistent entry 5 is valid, Bus 0 Target 5 is PhysId 5000c5000694c6ea

Persistent entry 6 is valid, Bus 0 Target 6 is PhysId 5000c5000694be86

Persistent entry 7 is valid, Bus 0 Target 7 is PhysId 5000c5000694bb7a

Persistent entry 8 is valid, Bus 0 Target 8 is PhysId 5000c5000694beae

Persistent entry 9 is valid, Bus 0 Target 9 is PhysId 5000c5000694c0de

Persistent entry 10 is valid, Bus 0 Target 10 is PhysId 5000c5000694bffe

Persistent entry 11 is valid, Bus 0 Target 11 is PhysId 500a0b82e0850019

Persistent entry 12 is valid, Bus 0 Target 12 is PhysId 5000c5000694c6e9

Persistent entry 13 is valid, Bus 0 Target 13 is PhysId 5000c5000694be85

Persistent entry 14 is valid, Bus 0 Target 14 is PhysId 5000c5000694bb79

Persistent entry 15 is valid, Bus 0 Target 15 is PhysId 5000c5000694bead

Persistent entry 16 is valid, Bus 0 Target 16 is PhysId 5000c5000694c0dd

Persistent entry 17 is valid, Bus 0 Target 17 is PhysId 5000c5000694bffd

Persistent entry 18 is valid, Bus 0 Target 18 is PhysId 500a0b82e0894019

SAS1068's links are 3.0 G, 3.0 G, 3.0 G, 3.0 G, down, down, down, down

B___T___L Vendor Product Rev SASAddress PhyNum

0 12 0 SEAGATE ST3146855SS MS01 5000c5000694c6e9 0

0 13 0 SEAGATE ST3146855SS MS01 5000c5000694be85 1

0 14 0 SEAGATE ST3146855SS MS01 5000c5000694bb79 2

0 15 0 SEAGATE ST3146855SS MS01 5000c5000694bead 3

0 16 0 SEAGATE ST3146855SS MS01 5000c5000694c0dd 5

0 17 0 SEAGATE ST3146855SS MS01 5000c5000694bffd 11

0 18 0 LSILOGIC SYM3600-SAS 0166 500a0b82e0894019 24

RAID is not supported on this port

Program Ended.

The results below show /etc/smartmon-ux -zdL /dev/es/ses0

This particular controller doesn't support an event log, but the dump will still provide information about the firmware and chipset.

Discovered LSILOGIC SYM3600-SAS S/N "0617053320" on /dev/es/ses0 [SES] (Enclosure Services)

Discovered (1) Controllers:

mpt0 RAID SAS1068 A0 MPT 105 Firmware 01100001 IOC 0

This controller does not support event logging

The event log is empty for the above controller, or the feature is not supported by the firmware

Program Ended.

Reporting disk drives only (the -zdq command)

The results below do an efficient scan to just report physical disks seen by the operating system, as well as disk drives that are hidden behind logical disks created by RAID firmware, using the command smartmon-ux -zdq This dump was run on a LINUX host that uses a LSI controller configured in RAID-1 mode. Note that some of the disks report a physical device (/dev/hdb, /dev/sda, /dev/sdb, /dev/sdc). Those disks are directly seen by the operating system. The HP disk at "Bus 0 Target 5" is only seen by the RAID controller and invisible to the operating system. (Note for security reasons, the serial numbers were manually changed in this document).

[root@w13 /scratch/common]# ./smartmon-ux -zdq

Discovered TSSTcorpCDW/DVD TS-L462D S/N "" on /dev/hdb (SMART unsupported)

Discovered ATA ST3500630NS S/N "9QG43RVS" on /dev/sda (Not Enabling SMART)(476940 MB)

Discovered HP DF072BAFDT S/N "BJL4P86004TB0862" at Bus 0 Target 5 (Not Enabling SMART) (70007 MB)

Discovered ATA WDC WD2500AAJS-2 S/N "WD-WMART1663509" on /dev/sdb (Not Enabling SMART)(238475 MB

Discovered LSILOGIC Logical Volume S/N "" on /dev/sdc (SMART unsupported)(69618 MB)

Here is the -zd dump from the same system, that reveals more about the configuration and how the disks are used.

[root@w13 /scratch/common]# ./smartmon-ux -zd

Discovered TSSTcorpCDW/DVD TS-L462D S/N "" on /dev/hdb (SMART unsupported)

Discovered ATA ST3500630NS S/N "9QG43RVS" on /dev/sda (Not Enabling SMART)(476940 MB)

Discovered (1) Controllers:

Port #0. /proc/mpt/ioc0 RAID SAS1068 B1 MPT 105 Firmware (1.18.00) IOC 0

x86 BIOS image's version: MPTBIOS-6.12.00.00 (2006.10.31)

Bus/Dev/Fun Board Name Board Assembly Board Tracer

130 3 0 SAS1068

SAS1068's phylinks are (Port 0,1,...,8): 1.5 G, down, 3.0 G, down, down, 3.0 G, down, down

Firmware Settings

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

SAS WWID: 500d068000003505

Multi-pathing: Disabled

SATA Native Command Queuing: Enabled

SATA Write Caching: Enabled

SATA Maximum Queue Depth: 32

Device Missing Report Delay: 0 seconds

Device Missing I/O Delay: 0 seconds

Phy Parameters for Phynum: 0 1 2 3 4 5 6 7

Link Enabled: Yes Yes Yes Yes Yes Yes Yes Yes

Link Min Rate: 1.5 1.5 1.5 1.5 1.5 1.5 1.5 1.5

Link Max Rate: 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0

SSP Initiator Enabled: Yes Yes Yes Yes Yes Yes Yes Yes

SSP Target Enabled: No No No No No No No No

Port Configuration: Auto Auto Auto Auto Auto Auto Auto Auto

Target IDs per enclosure: 1

Persistent mapping: Disabled

Physical mapping type: Direct Attach

Target ID 0 reserved for boot: No

Starting slot (direct attach): 0

Target IDs (physical mapping): 0

Interrupt Coalescing: Enabled, timeout is 16 us, depth is 4

Persistent Mappings

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

No persistent entries found

SAS1068's phylinks are (Port 0,1,...,8): 1.5 G, down, 3.0 G, down, down, 3.0 G, down, down

Discovered ST3500630NS S/N "9QG43RVS" on RAID (Not Enabling SMART) (476940 MB)

Discovered WDC WD2500AAJS-22VTA0 S/N "WD-WMART1663590" on RAID (Not Enabling SMART) (238475 MB)

Discovered LSILOGIC Logical Volume S/N "" on RAID (Not Enabling SMART) (69618 MB)

1 volume is active, 2 physical disks are

Volume 0 is Bus 0 Target 4, Type IM (Integrated Mirroring)

Volume Name:

Volume WWID: 0a0cade5ed79d4ab

Volume State: degraded, enabled

Volume Settings: write caching disabled, auto configure

Volume draws from Hot Spare Pools: 0

Volume Size 69618 MB, Stripe Size 0 KB, 2 Members

Volume Device:

Member 1 is PhysDisk 0 at (Bus 0 Target 5)

Discovered HP DF072BAFDT S/N "BJL4P86004TB0862" at Bus 0 Target 5 (70007 MB) state=online PhysDisk=0

Discovered HP DF072BABUD S/N "J2YD2PCA" at Bus 0 Target 8 (70007 MB) state=missing, out of sync PhysDisk=1

Volume 0 State: degraded, enabled

Volume 1 State: optimal, disabled

(Additional output follows, but was truncated as it isn't relevant to the -zd command)

There are several points of interest in this dump.

•	Note that the HP Disk S/N J2YD2PCA shows state=missing. That is because this disk is no longer plugged into the system, and really is missing. The RAID controller remembers the serial number, and smartmon-ux reports it, so you can see what was manually removed).

•	Some ports are running at 1.5 Gbit/sec, others are running at 3 Gbit/sec

•	The logical device is degraded (one disk is missing from the RAID-1 mirror)