VTrak E-Class Product Manual
Physical Drive Problems
Physical Drive Offline
Check the drive for:
•
PFA Condition – Caused by a bad block or sector.
See "Clearing Stale and PFA Conditions" on page 112.
•
Stale Configuration – Caused by obsolete array information on the physical
drive. Identify the disk array to which the physical drive belongs. Then delete
the disk array. See "Deleting a Disk Array" on page 118.
If the error condition remains on the physical drive, clear the error condition.
See "Clearing Stale and PFA Conditions" on page 112.
Physical Drive Not Usable
This condition occurs when you have:
•
Two controllers in your VTrak subsystem and a SATA drive without an
AAMUX adapter. See "AAMUX Adapter" on page 12.
•
A missing or defective SAS cable between the VTrak subsystem and a
JBOD enclosure.
Physical Drive Failed
When physical drive status shows failed, the physical drive cannot be repaired.
You must replace the failed drive.
Physical Drive Fails during Migration
VTrak has two methods for migrating a disk array:
•
DDF – The default setting. Slower but reliable
•
NVRAM – An optional setting that requires special access. Faster but risks
data loss
Normally, RAID level migration is done under the default Disk Data Format (DDF)
setting. If a physical drive or the controller fails during migration, the disk array
goes critical, and you can rebuild it. Migration under DDF can take up to several
hours depending on the number and size of the physical drives and data input/
output activity.
You can set the VTrak to migrate disk arrays under Non-Volatile Random Access
Memory (NVRAM), a much faster process because it writes data to the memory
in the controller. However, if a physical drive or the controller fails during
migration, the logical drives will go offline and you will lose data. See "Incomplete
Array" on page 279.
280