User manual
Table Of Contents
- SuperTrak User Manual
- Contents
- Chapter 1: Introduction
- Chapter 2: Installation
- Unpacking the SuperTrak Card
- Installing the SuperTrak Card
- Choosing the Physical Drives
- Creating a Logical Drive
- Installing the CLI
- Installing WebPAM PRO
- Logging into WebPAM PRO
- Setting up WebPAM PRO
- Chapter 3: Installing Drivers
- Chapter 4: SuperBuild™ Utility
- Chapter 5: Management with WebPAM PRO
- Logging into WebPAM PRO
- Accessing the Interface
- Managing Users
- Working with Subsystem/Host Management
- Managing Software Services
- Managing the Host
- Managing the Subsystem
- Viewing Subsystem Information
- Clearing Statistical Data
- Setting an Alias for the Subsystem
- Updating the Firmware
- Checking Subsystem Health
- Viewing the Runtime Event Log
- Saving the Runtime Event Log
- Clearing the Runtime Event Log
- Viewing the NVRAM Event Log
- Saving the NVRAM Event Log
- Clearing the NVRAM Event Log
- Viewing Current Background Activities
- Making Background Activity Settings
- Running Background Activities
- Running Media Patrol
- Running PDM
- Viewing Scheduled Activities
- Scheduling an Activity
- Deleting a Scheduled Activity
- Viewing System Configuration
- Managing the Controller
- Managing Enclosures
- Managing Physical Drives
- Viewing a List of Physical Drives
- Locating a Physical Drive
- Making Global Physical Drive Settings
- Viewing Physical Drive Information
- Viewing Physical Drive Statistics
- Making Physical Drive Settings
- Clearing Stale and PFA Conditions
- Viewing the SMART Log
- Viewing Advanced SMART Log Information
- Saving Advanced SMART Log Information
- Making SMART Log Settings
- Managing Disk Arrays
- Viewing Disk Arrays
- Locating a Disk Array
- Creating a Disk Array
- Creating a Disk Array - Automatic Configuration
- Creating a Disk Array - Express Configuration
- Creating a Disk Array - Advanced Configuration
- Deleting a Disk Array
- Viewing Disk Array Information
- Making Disk Array Settings
- Creating a Logical Drive
- Deleting a Logical Drive
- Migrating a Disk Array
- Rebuilding a Disk Array
- Running Media Patrol on a Disk Array
- Running PDM on a Disk Array
- Transitioning a Disk Array
- Preparing a Disk Array for Transport
- Managing Logical Drives
- Managing Spare Drives
- Working with the Logical Drive Summary
- Chapter 6: Management with the CLI
- Opening the CLI on Windows
- Opening the CLI on Linux, FreeBSD, and VMware
- Table of Supported Commands
- Notes and Conventions
- List of Supported Commands
- Chapter 7: Technology Background
- Chapter 8: Troubleshooting
- Chapter 9: Support
- Appendix A: Partition and Format
- Appendix B: Upgrades
- Appendix C: Battery Backup Unit
- Appendix D: LED Backplane Connections
- Index

Chapter 7: Technology Background
255
Media Patrol
Media Patrol is a routine maintenance procedure that checks the magnetic media
on each physical drive. Media Patrol checks all physical drives assigned to disk
arrays and on spare drives. Media Patrol does not check unconfigured drives.
Unlike Synchronization and Redundancy Check, Media Patrol is concerned with
the condition of the media itself, not the data recorded on the media. If Media
Patrol encounters a critical error, it triggers PDM if PDM is enabled.
You can run Media Patrol:
• From the subsystem. See page 138.
• Directly on a disk array. See page 169.
Predictive Data Migration (PDM)
Predictive Data Migration (PDM) is the migration of data from the suspect
physical drive to a spare drive, similar to Rebuilding a Logical Drive. But unlike
Rebuilding, PDM constantly monitors your physical drives and automatically
copies your data to the spare drive before the suspect drive fails and your Logical
Drive goes Critical. See “Running PDM” on page 138 and “Running PDM on a
Disk Array” on page 169.
After the data is copied from the suspect drive, the controller marks the suspect
drive with a Stale configuration and a PFA error.
You can clear the Stale configuration and PFA error and put the physical drive
back into service. See “Clearing Stale and PFA Conditions” on page 152 or
page 269. In some cases, however, you might remove the physical drive for
repair or replacement.
PDM Triggers
The following actions trigger PDM:
• A physical drive with unhealthy status (see below)
• Media Patrol finds a disk critical error*
• You initiate PDM manually
*PDM also counts the number of media errors reported by Media Patrol.
A physical drive becomes unhealthy when:
• A SMART error is reported
• The bad sector remapping table fills to the specified level
Because data would be lost if written to a bad sector, when a bad sector is
detected, the physical drive creates a map around it. These maps are saved in