 |
» |
|
|
|
The following sections cover the kernel level error messages. Kernel Notice Messages | |
The following are notice messages associated with the kernel. vxvm:vxio:NOTICE: Can't open disk disk in group disk_group.
If it is removable media (like a floppy), it may not be mounted
or ready. Otherwise, there may be problems with the drive.
Kernel error code number |
| Description The named disk cannot be accessed in the named disk
group. Action Ensure that the disk exists, is powered on, and is
visible to the system.
|
Can't close disk in group |
vxvm:vxio:NOTICE: Can't close disk disk in group disk_group. If it
is removable media (like a floppy), it may have been removed.
Otherwise, there may be problems with the drive. Kernel error
code public_region_error/private_region_error |
| Description This is unlikely to happen; closes cannot fail.
|
Read error on object of mirror in volume corrected |
vxvm:vxio:NOTICE: read error on object subdisk of mirror plex in
volume volume (start offset, length length) corrected. |
| Description A read error occurred, which caused a read of an alternate
mirror and a writeback to the failing region. This writeback was
successful and the data was corrected on disk. Action No action is required. The problem was corrected automatically.
The administrator may, however, note the failure as a reference
because if the same region fails again or frequently, the error
could indicate a more insidious failure and the disk should be reformatted
at the next reasonable opportunity.
|
String on volume device in disk group |
vxvm:vxio:NOTICE:
string on volume device_ # (device_name) in disk group group_name |
| Description An application requested message. The application running
on top of the Volume Manager has requested the output of this message. Action Refer to documentation for the appropriate application
for more information.
|
Kernel Warning Messages | |
The following are warning messages associated with the kernel. vxvm:vxio:WARNING: Device major, minor: Received spurious close |
| Description This message happens if a close was received for an
object that was previously not opened. This will only happen if
the operating system is not correctly tracking opens and closes. Action No action is necessary; the system will continue.
|
Failed to log the detach of the DRL volume |
vxvm:vxio:WARNING:
Failed to log the detach of the DRL volume volume |
| Description An attempt to write a kernel log entry indicating the
loss of a DRL volume failed. The attempted write to the log failed
either because the kernel log is full or because of a write error
to the drive. The volume will become detached. Action Messages about log failures are often fatal, unless
the problem is transient. However, the kernel log is sufficiently
redundant that such errors are unlikely to occur. If the problem is not transient (i.e. the drive cannot be
fixed and brought back online without data loss), the disk group
must be recreated from scratch and all of its volumes must be restored
from backup. Even if the problem is transient, the system must be
rebooted after correcting the problem. If error messages were seen from the disk driver, it is likely
that the last copy of the log failed due to a disk error. The failed
drive in the disk group should be replaced and the log will then
be re-initialized on the new drive. The failed volume can then be
forced into an active state and the data recovered.
|
vxvm:vxio:WARNING: DRL volume volume is detached |
| Description A Dirty Region Logging volume became detached because
a DRL log entry could not be written. This might be because of a
media failure, in which case other errors may have been logged to
the console. Action The volume containing the DRL log will continue. If
the system fails before the DRL can be repaired, a full recovery
of the volume's contents may be necessary and will be performed
automatically when the system is restarted. To recover the DRL capability,
a new DRL log should be added to the volume using the vxassist addlog command.
|
Read error on mirror of volume |
vxvm:vxio:WARNING:
read error on mirror plex of volume volume offset offset length length |
| Description An error was detected while reading a mirror. This
error may lead to further action shown by later error messages. Action If the volume is mirrored, no action is necessary at
this time since the alternate mirror's contents will be
written to the failing mirror; this is often sufficient to correct
media failures. If this error occurs often but never leads to a
plex detach, there may be a marginal region on the disk at the position
shown. It may eventually be necessary to remove data from this disk
(see the vxevac(1M) manual page) and then to reformat the drive.
In the unmirrored case, this message indicates that some data could
not be read. The file system or other application reading the data
may report an additional error, but in either event, data has been
lost. The volume can be partially salvaged and moved to another
location if desired.
|
Write error on mirror of volume offset length |
vxvm:vxio:WARNING: write error on mirror plex of volume volume
offset offset length length |
| Description An error was detected while writing a mirror. This
error will generally be followed by a detach message, unless the
volume is un-mirrored. Action The disk reporting the error is failing to correctly
store written data. If the volume is not mirrored, consider removing
the data and reformatting the disk. If the volume is mirrored, it
will become detached and you should consider replacing or reformatting
the disk. If this error occurs often but never leads to a plex detach,
there may be a marginal region on the disk at the position shown.
It may eventually be necessary to remove data from this disk (see
the vxevac(1M) manual page) and then to reformat the drive.
|
Object detached from volume |
vxvm:vxio:WARNING: object plex detached from volume volume |
| Description An uncorrectable error was detected by the mirroring
code and a mirror copy was detached. Action To restore redundancy, it may be necessary to add another
mirror. The disk on which the failure occurred should be evacuated
and reformatted, if possible. If the drive has failed completely,
it may need to be replaced.
|
Overlapping mirror detached from volume |
vxvm:vxio:WARNING: Overlapping mirror plex detached from volume
volume |
| Description An error has occurred on the last complete plex in
the mirrored volume. Any sparse mirrors that map the failing region
must be detached so that they cannot be accessed to satisfy that
failed region inconsistently. This message indicates that such an
overlapping mirror was found and is being detached. Action No Action is directly necessary. The message indicates
that the volume may have left some data inaccessible at the failing
region and that it is no longer redundantly stored.
|
vxvm:vxio:WARNING: Kernel log full: volume detached |
| Description A plex detach failed because the kernel log was full.
As a result, the mirrored volume will become detached. Action It is unlikely that this condition could ever occur.
The only corrective action for the detached volume is to reboot
the system.
|
vxvm:vxio:WARNING: Kernel log update failed: volume detached |
| Description A plex detach failed because the kernel log could not
be flushed to disk. As a result, the mirrored volume will become
detached. This could be caused by all the disks containing a kernel
log going bad. Action Correct the failed disks so that kernel logging can
once again function.
|
vxvm:vxio:WARNING: detaching RAID-5 raidvol |
| Description Either a double-failure condition in the RAID-5 volume
has been detected in the kernel or some other fatal error is preventing
further use of the array. Action If two or more drives were lost due to a controller
or power failure, then once the disks can be re-attached to the
system, they should be recovered using the vxrecover utility. Check the console for other errors that
may provide additional information as to the nature of the failure.
|
Object detached from RAID-5 volume |
vxvm:vxio:WARNING: object subdisk detached from
RAID-5 raidvol at column column offset offset |
| Description A subdisk was detached from a RAID-5 volume at the
specified column number and offset. This is caused by the failure
of a disk or an uncorrectable error occurring on that disk. Action Check the console for other error messages indicating
the cause of the failure. If the disk has failed, then it should
be replaced as soon as possible.
|
RAID-5 volume entering degraded mode operation |
vxvm:vxio:WARNING: RAID-5 raidvol entering degraded
mode operation |
| Description This message occurs when an uncorrectable error has
forced the detach of a subdisk. At this point, not all data disks
exist to provide the data upon request. Instead, parity regions
are required to regenerate the data for each stripe in the array.
Accesses will consequently take longer and will involve reading
from all drives in the stripe. Action Check the console for other error messages indicating
the cause of the failure. If the disk has failed, it should be replaced
as soon as possible.
|
Double failure condition detected on RAID-5 volume |
vxvm:vxio:WARNING: Double failure condition detected on
RAID-5 raidvol |
| Description Double-failures occur if I/O errors are received at
the same altitude in the array from more than one column of the
array. This could be caused by a controller failure causing more
than a single drive to become unavailable; by the loss of a second
drive after having run in a degraded state for significant periods
of time; or by two separate disk drives failing simultaneously (which
is unlikely to happen). Action If the condition is correctable and the drives recoverable,
the conditions should be corrected. The volume can then be recovered using
the vxrecover(1M) command.
|
Failure in RAID-5 logging operation |
vxvm:vxio:WARNING: Failure in RAID-5 logging operation
vxvm:vxio:WARNING: log object object_name detached from
RAID-5 volume |
| Description These two messages will appear together when a RAID-5
log has failed and has been detached. Action To restore RAID-5 logging to the RAID-5 volume, simply
create a new log region and attach it to the volume.
|
vxvm:vxio:WARNING: check_ilocks:
stranded ilock on object_name start offset len length |
| Description This is an internal Volume Manager problem. This warning
should not occur unless there is a bug in the Volume Manager. Action Contact Customer Support for more information.
|
vxvm:vxio:WARNING: check_ilocks: overlapping ilocks:
offset for length, offset for length |
| Description This is an internal Volume Manager problem. This warning
should not occur unless there is a bug in the Volume Manager. Action Contact Customer Support for more information.
|
Illegal vminor encountered |
vxvm:vxio:WARNING: Illegal vminor encountered |
| Description If a volume device other than the root volume device
is opened before a configuration has been loaded, this message could
result. Action No action should be necessary; an attempt to access
a volume device was made before the volume daemon (vxconfigd) loaded the volume configuration. Under normal
startup conditions, this message should not occur. If the operation
is necessary, start the Volume Manager and re-attempt the operation.
|
vxvm:vxio:WARNING: object_type object_name block offset:
Uncorrectable read error |
| Description A read or write operation from the specified object
failed. An error will be returned to the application. Action This error represents lost data. The data may need
to be restored and failed media may need to be repaired. Depending
on the type of object failing and on the type of recovery suggested
for that type, an appropriate recovery operation may be necessary.
|
Uncorrectable read/write error |
vxvm:vxio:WARNING: object_type object_name block offset:
Uncorrectable read error on object_type object_name block offset
vxvm:vxio:WARNING: object_type object_name block offset:
Uncorrectable write error on object_type object_name block offset |
| Description A read or write operation from the specified object
failed. An error will be returned to the application. Although similar
to the previous message, this message is able to supply more specific
information about the failing object. Action This error represents lost data. The data may need
to be restored and failed media may need to be repaired. Depending
on the type of object failing and on the type of recovery suggested
for that type, an appropriate recovery operation may be necessary.
|
Root volumes are not supported on your PROM version |
vxvm:vxio:WARNING: Root volumes are not supported on your PROM
version. |
| Description The Volume Manager requires the ability to access the
PROMs for your SPARC hardware. If the PROMs are not a recent OpenBoot PROM
type, then root volumes will not be usable. Action If you have set up a root volume, then undo the configuration
(by running vxunroot or removing the rootdev line from /etc/system) as soon as possible and contact your hardware
vendor for an upgrade to your PROM level.
|
Cannot find device number |
vxvm:vxio:WARNING: Cannot find device number for boot_path |
| Description The supplied boot path was retrieved from the PROMs
for your system. It cannot be converted to a valid device number. Action Check your PROM settings for the correct boot string.
|
mod_install returned errno |
vxvm:vxio:WARNING: mod_install returned errno |
| Description A call made to the operating system mod_install() function to load the vxio driver failed. Action Check your console for additional messages that may
explain why the load failed. Also check the console messages log
file for any additional messages that were logged but not displayed
on the console.
|
subdisk failed in plex in volume |
vxvm:vxio:WARNING:
subdisk subdisk failed in plex plex in volume volume |
| Description The kernel has detected a subdisk failure, which may
mean that the underlying disk is failing. Action Check for obvious problems with the disk (such as a
disconnected cable). If hot-relocation is enabled and the disk is
failing, the subdisk failure may be taken care of automatically.
|
Kernel Panic Messages | |
The following are panic messages associated with the kernel. Object association depth overflow |
vxvm:vxio:PANIC: Object association depth overflow |
| Description This is an internal Volume Manager problem. This warning
should not occur unless there is a bug in the Volume Manager. Action Contact Customer Support for more information.
|
|
Printable version
