Disk Drive Errors and Failure Recovery

Disk Drive Revive Failure Recovery

If a disk revive operation receives a checksum error or nonfatal error, the SCF START DISK

command retries the disk revive operation at the current address until either the operation is

successful or the operation suspends or stops. If the disk revive operation suspends or stops,

refer to the SCF Reference Manual for the Storage Subsystem.

A disk revive operation might display errors when you use the SCF START DISK command.

The following table lists causes of SCF START DISK command failures along with

appropriate recovery actions.

Cause Recovery Action

The disk volume label is unreadable. Report this problem to your service provider.

The configured disk subtype is incompatible

with the subtype specified on the disk

volume label.

Verify that the disk drive is properly

configured. This problem can be caused by

an attempt to use a newly installed disk drive

that either is not supported by the storage

subsystem or has not yet been configured.

Use the SCF ALTER DISK command to

properly configure the disk drive.

The disk drive failed during an SCF

CONTROL DISK, REBUILDDFS operation.

Rerun the CONTROL DISK, REBUILDDFS

command. If the disk drive fails a second

time, contact your service provider.

One disk drive in a mirrored disk volume has

an older disk volume label timestamp than

the other disk drive.

Use the SCF START DISK command on the

older disk drive to revive it.

The disk volume label or directory label

format is bad or invalid.

Contact your service provider, who might be

able to correct the invalid data or directory

using the TANDUMP utility.

Not enough memory is available. Try stopping processes that are running in

the same processor as the primary disk

process until enough memory is available to

start the disk.