|
|
Warning messages (error messages that begin with WARNING:)
alert you to virtual disk failures that require immediate attention.
These messages are recorded in /usr/adm/messages and are
displayed on the console.
The virtual disk configuration is not supported. The driver
failed the virtual disk because only eight levels of
nesting are allowed by the disk array driver. The desired
configuration exceeds that level.
There are three possibilities:
The array or mirror is no longer functional. The driver was unable to access two disk pieces in the virtual disk or the driver was unable to access one disk piece in the virtual disk while the parity data was out of date. You must:
The system does not have enough memory to initialize the virtual disk driver or perform a driver operation. If this error message persists and there is no ``memory leak'' (a process that progressively uses up memory without releasing it), add additional physical memory to the system or reduce the virtual disk or other system resources. See ``Virtual disks''.
The system does not have enough memory to allocate the necessary buffers for I/O. If this error message persists, consider adding additional physical memory to the system or reducing system resources.
The driver failed to access disk piece m when reading or writing the timestamp. Piece m will be taken out of service, but the array or mirror will still be functional.
Restore parity on the out-of-service piece. If the restore fails, the out-of-service drive should be repaired/replaced as soon as possible and the parity restored.
The virtual disk in not functional. The driver failed to open or access a disk piece when initializing a new configuration. The disk drive is either disabled or the disk piece is not defined properly. Repair or replace the failed drive or ensure the disk piece is available, then force the virtual disk online. If the virtual disk is an array or mirror, restore the parity.
There was a system crash while the reconfigure operation was in progress. The array is offline. You should:
The array or mirror is no longer functional. The driver was unable to access two disk pieces in the virtual disk. You should force the array or mirror online.
If the configuration fails, you should:
The timestamp on disk piece m of the array or mirror has become desynchronized. You should:
Timestamps for the disk pieces, which make up the array or mirror, are out of synchronization. One or more of the disk pieces, which make up the array or mirror, were accessed individually prior to reboot or an enable. You should:
The driver was unable to access a disk piece and attempted
to replace the failed disk (the disk piece will be taken
out of service) with the spare disk piece. While updating
the data on the spare piece, an I/O error
occurred. The spare piece will not replace the
out-of-service piece in the virtual disk. The array or
mirror is still functional, but you should replace the
out-of-service data drive and spare drive as soon as
possible.
The virtual disk was fully operational prior to a system
crash. Data on the parity piece may not be accurate. The
system will automatically restore parity during boot, so
no intervention is necessary in this case.
The virtual disk had one piece out of service prior to a system crash. Data on the virtual disk may not be accurate. Repair or replace the out-of-service drive and restore the virtual disk data from backups as described in ``Restoring a scheduled filesystem backup''.
The daemon was not spawned during reboot. RAID virtual disks may not be operational. Reboot the system and use ps -aef to make sure the vddaemon is running. If the problem occurs again, the system may be corrupted. Deconfigure the virtual disks and reinstall the Virtual Disk Manager package.
At least one vddaemon must be running. On multiprocessor systems, one is started per CPU for extra performance. If only one is running, then virtual disk performance may be reduced.
The driver was unable to configure disk piece m of the virtual disk. Piece m will be taken out of service. The array or mirror is functional, but you should repair or replace the disk drive as soon as possible and restore the parity of the failed drive. See ``Repairing a failed drive'' for more information.
The driver failed to access disk piece m of the virtual disk. This disk piece will be taken out of service. The array or mirror is functional, but you should repair or replace the out-of-service disk drive as soon as possible and restore the parity for the failed drive.
The maximum number of outstanding jobs for the specified
virtual device has been reached.
Restore the parity again.
See
``Virtual disks''.
A reconfiguration on vdisk n was in progress and was interrupted. The driver attempted to restart the reconfiguration from the interrupted point, but could not. The virtual disk will be offline. You should:
A write to dktab piece m of vdisk0 failed. Configuration information is not valid on that backup piece. You can either:
Reconfiguration of the indicated virtual disk cannot be
restarted if it is interrupted before completion. Verify
that enough spool pieces are configured in
vdisk0 for as many simultaneous fail-safe
reconfigurations as will be executed. See
``Adding a configuration backup''
for information on modifying the virtual disk database.
The piece number x of vdisk0 is too small to back up the current configuration of configured virtual disks. Increase the length of that piece or reconfigure vdisk0 to include a larger disk piece. See ``Adding a configuration backup'' for information on modifying the virtual disk database.