3Ware 7000-2 - Escalade RAID Controller, User Manual

Page: 25 / 196

Introduction
www.3ware.com 25
Configure and manage your disk arrays
The 3ware Disk Array Configuration Utility is a BIOS level tool
for creating, deleting, maintaining disk arrays and rebuilding mir-
rored arrays. From the
3DM Disk Array Configuration Utility ,
you can also specify hot spares from available drives to be dynami-
cally substituted for a failed drive in a mirrored array. Refer to the
3ware Disk Array Configuration Utility chapter.
SMART Monitoring (Self-Monitoring, Analysis and Reporting
Technology) adds monitoring and troubleshooting functionality by
automatically checking a disk drive's health and reporting potential
problems. It allows you to take proactive steps to prevent impend-
ing disk crashes. SMART data is checked on all disk drives (array
members, JBOD and Hot Spares). Three SMART commands are
issued: SMART RETURN STATUS (B0h with a Feature register
value of DAh), SMART READ LOG (B0h with the content of the
Features register equal to D5h), and SMART READ DATA (B0h
with the content of the Features register equal to D0h).
• SMART RETURN STATUS - This command is issued 24 hours
after the Escalade controller is powered up. This 24 hour wait
period is timed internally in the 3ware firmware, and is not
affected by changes to the system clock. Every 24 hours, the
SMART RETURN STATUS is issued to attached disk drives. If
none of the disk drives have detected a “threshold exceeded”
condition, then nothing is logged to the 3DM Alarms page. If
any of the disk drives have detected a “threshold exceeded” con-
dition, then an AEN is logged to the 3DM Alarms page. This is
repeated every 24 hours that the Escalade controller is powered
up.
• SMART READ LOG and SMART READ DATA - These com-
mands are issued independent of the SMART RETURN STA-
TUS command. These commands are only issued when the
'Download Error Log' button on the 3DM Alarms page is
pressed (See page 155). The SMART data is returned at the bot-
tom of the Error Log, starting after “#SMARTErrorLogStart.”