User manual

ManualsBrandsSeagate ManualsAutomobile AccessoriesST3655N

211

212

213

214

215

216

217

218

219

220

Using S.M.A.R.T. Disk Monitor 213

opcode=0xB1

E=0208 I=FFFFD7C4 T=00:29:44 P=0 : Drive not ready, no retries

ata task file written out : cd dh ch cl sn sc ft

: B0 A0 C2 4F 01 01 D1

ata task file read back : st dh ch cl sn sc er

: D0 A0 C2 4F 01 01 00

E=0208 I=008E8E9C T=00:29:44 : Drive not ready

E=0208 I=008E8E9C T=00:29:44 U=0 : Return error status to host

Error, Unit 0: Drive not ready

(EC:0x208, SK=0x04, ASC=0x08, ASCQ=0x00, SEV=01, Type=0x70)

opcode=0xB1

Saving PRINTLOG, time=2300170 ...

** End of Diagnostic Dump **

Program Ended.

Reporting AMCC Internal Event Log (-z3L)

This reports the contents of the controller's internal event log. The format is fixed and it is suitable for parsing. Here is

an example of what you would expect to see on a power up. Event log entries are numbered sequentially from zero,

and a power cycle clears the log.

[root@frank smartmon]# ./smartmon-ux -z3L /dev/sg2

Discovered 3ware Logical Disk 00 S/N " " on /dev/sg2 (SMART unsupported)(190724 MB)

Physical Device Dump: (DeviceMake-Model [Firmware] S/N=SerialNumber Blocks DiskNumber.ControllerPort [DeviceState]

WDC WD2000JD-00FYB0 [02.05D02] S/N=WD-WMAEH2469728 190782 MB at ID.Port 0.0 [OK]

Maxtor 6Y080M0 [YAR51BW0] S/N=Y3JRAGXE 78167 MB at ID.Port 1.3 [OK]

Logical Device Dump:

SINGLEDISK 190724 MB at SCSIID 0 [OK]

SINGLEDISK 76283 MB at SCSIID 1 [OK]

Controller Event Log Dump

Event# 0: Code=0000h @ Wed Dec 31 18:00:00 1969 (0x04:0x0000): AEN queue empty

Reporting AMCC Internal Event Log (-z3m)

This reports the health of the subsystem as part of a background monitoring daemon. You would add it as a runtime

parameter when you run the program as either a windows service or UNIX/LINUX daemon. You should combine it

with the -F flag to set a polling interval. (If you do not set the polling flag, then the health will be queried every 10

minutes).

1.52.5 LSI (MPT Internal) RAID Engines

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

214