VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)

Error Messages
Kernel Warning Messages
Chapter 3
53
Kernel Warning Messages
A warning message from the kernel indicates that a non-critical operation has failed,
possibly because some resource is not available. Corrective action should be taken
immediately.
vxvm:vxio:WARNING: Cannot find device number for boot_path
• Description: The boot path retrieved from the system PROMs cannot be converted to
a valid device number.
• Action: Check your PROM settings for the correct boot string.
vxvm:vxio:WARNING: check_ilocks: overlapping ilocks: offset for length ,
offset for length
vxvm:vxio:WARNING: check_ilocks: stranded ilock on object_name start offset
len length
• Description: These internal errors do not occur unless there is a bug in VxVM.
• Action: Contact Customer Support.
vxvm:vxio:WARNING: detaching RAID-5 volume
• 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 disks have been lost due to a controller or power failure, use
the vxrecover utility to recover them once they have been re-attached to the system.
Check for other console error messages that may provide additional information
about the failure.
vxvm:vxio:WARNING: Device major , minor : Received spurious close
• Description: A close was received for an object that was not open. This can only
happen if the operating system is not correctly tracking opens and closes.
• Action: No action is necessary; the system will continue.
vxvm:vxio:WARNING: Double failure condition detected on RAID-5 volume
• Description: I/O errors have been received in more than one column of a RAID-5
volume. This could be caused by:
— a controller failure making more than a single drive unavailable
— the loss of a second drive while running in degraded mode
— two separate disk drives failing simultaneously (unlikely)
• Action: Correct the hardware failures if possible. Then recover the volume using the
vxrecover command.
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. If this is due to a media failure, other errors may have
been logged to the console.