User manual

SANtools® S.M.A.R.T. Disk Monitor (SMARTMon-UX)210
SANTOOLS® is registered in US Patent and Trademark Office No 3,107,854 All rights reserved.
Alert [#7 Type 2101h at 18:55:02 03/29/2005] SCSI drive failed on logical drive 0(channel=1, id=82/52h,
lun=0).
Warning [#8 Type 113Fh at 19:01:45 03/29/2005] Channel 1 (ID 89/59h) reported that a redundant path failure
was detected. Now using redundant logical channel 1.
Warning [#9 Type 1101h at 19:01:45 03/29/2005] Channel 1 (ID 89/59h) reported a select timeout, sector=0h.
Warning [#10 Type 113Fh at 19:12:49 03/29/2005] Channel 1 (ID 86/56h) reported that a redundant path failure
was detected. Now using redundant logical channel 1.
Warning [#11 Type 1101h at 19:12:49 03/29/2005] Channel 1 (ID 86/56h) reported a select timeout, sector=0h.
Alert [#12 Type 2101h at 19:12:50 03/29/2005] SCSI drive failed on logical drive 0(channel=1, id=86/56h,
lun=0).
Warning [#13 Type 113Fh at 19:13:26 03/29/2005] Channel 1 (ID 90/5ah) reported that a redundant path failure
was detected. Now using redundant logical channel 1.
Warning [#14 Type 1101h at 19:13:26 03/29/2005] Channel 1 (ID 90/5ah) reported a select timeout, sector=0h.
Alert [#15 Type 2101h at 19:13:27 03/29/2005] SCSI drive failed on logical drive 0(channel=1, id=90/5ah,
lun=0).
Information [#16 Type 2183h at 19:13:42 03/29/2005] Rebuild continued on logical drive 0.
Information [#17 Type 2184h at 19:23:58 03/29/2005] Rebuild paused due to state change on logical drive 0.
Detailed RAID Controller and Peripheral Report:
The -zix command is designed for storage diagnostic engineers, and should not be used unless the LUNs on the
RAID engine are offline and no longer satisfying I/O requests from application software.
The information that is returned is controller and device-specific configuration hex dumps.
Partial RAID Controller Event Log:
The -ziA flag is like the -ziL flag, but it lets you control the starting number and total count of event log entries.
You would ordinarily use this command as part of a script.
[root@BOSS smartmon]# ./smartmon-ux -ziA 4 2 /dev/sde
SMARTMon-ux [Release 1.28, Build 01-APR-2005] - Copyright 2001-2005 SANtools, Inc. http://www.SANtools.com
Discovered IFT ER2000R1 S/N "3221234" on /dev/sde (SMART unsupported)(492 MB)
Warning [#4 Type 113Fh at 18:52:58 03/29/2005] Channel 0 reported that a redundant loop failure has been
detected. Now using the surviving logical channel 2.
Warning [#5 Type 113Fh at 18:54:57 03/29/2005] Channel 1 (ID 82/52h) reported that a redundant path failure
was detected. Now using redundant logical channel 1.
Additional Information
· Unless you (or your RAID provider) has configured the engine otherwise, you can query this RAID engine by
sending the -I+ command to any LUN.
· RAID subsystem manufacturers and VARs/OEMs mask the make & model of RAID engine they are using by
changing the make and model fields. You may have an Infortrend-based subsystem and not know it.
· By design, our software does NOT allow you to change any configurable parameters except for mode pages. You
cannot use our software as a "configurator".
Continuous Infortrend Polling
The -zm command can be used to continuously poll an Infortrend RAID engine. You would generally combine this flag
with the -F flag which allows you to specify a polling interval. Otherwise, it will use the default polling interval of 10
minutes.
1.52.4 3WARE AMCC RAID Engines
Support for the 3-WARE / AMCC family RAID engines is limited to the 7xxxx, 8xxx, and 9xxx family. This includes the
controllers that work with both SATA and ATA (PATA) disk drives.
The full inquiry command -I+ reports controller-specific information such as firmware revisions and make/model
information. The text highlighted in blue is specific o 3-WARE controllers. There is a chance that you have a
3ware-based controller, but the identification strings have been changed because the controller is relabeled by an
OEM. If our software does not properly report that you have a 3-WARE engine because of this, please let us know,
and we will make the necessary modifications and supply you with an update. The 3ware API does not provide an
elegant way to determine if the controller is a 3-WARE controller, so we rely on interpreting SCSI strings rather than
sending what may be invalid commands which might confuse a non-3ware device.
209
54