![[Return to Library]](BOOKSHELF.GIF)
![[Contents]](TOC.GIF)
![[Previous Chapter]](REW.GIF)
![[Next Section]](NEXT.GIF)
![[Next Chapter]](FF.GIF)
![[Index]](INDEX.GIF)
![[Help]](HELP.GIF)
The Logical Storage Manager is fault-tolerant and resolves most problems without system administrator intervention. If the volume daemon (vold) recognizes what actions are being taken, it can roll a transaction forward or back. When vold is unable to recognize and fix system problems, you need to handle the task of problem solving.
The following sections cover the majority of informational, failure, and error messages displayed by vold and the kernel driver. These sections include some errors that are infrequently encountered and difficult to troubleshoot. Clarifications are included to elaborate on the situation or problem that may have generated a particular message. Wherever possible, a recovery procedure (user action) is provided to locate and correct potential problems.
Should it be necessary to contact your customer support organization, these messages are numbered for ease of reference.
The following list contains the error messages associated with the volume daemon.
-r must be followed by 'reset'
Clarification: This message is caused by a usage error.
User Action: Correct the usage and try again.
-x argument : prefix too long
Clarification: The stub-mode device path prefix name supplied exceeded the maximum of 32 characters.
User Action: Select an alternate path for device files and retry the command.
-x string : invalid debug string
Clarification: An unknown argument string was given to the -x option to vold.
User Action: Select a valid string from the reference page for vold and try again.
Usage: vold [-dkf] [-r reset] [-m mode] [-x level]
For detailed help use: vold help
Clarification: vold was invoked with an invalid set of arguments.
User Action: Correct the usage and try again or type vold help for more help. This is the full usage message from entering vold help:
Usage: vold [-dkf] [-r reset] [-m mode] [-x level]
Recognized options:
-d set initial mode to disabled for transactions
-k kill the existing configuration daemon process
-f operate in foreground; default is background
-r reset reset kernel state; requires 'reset' option argument
-m mode set vold's operating mode
modes: disable, enable, bootload, bootstart
-x level set debugging level to <debug>, 0 turns off debugging
-R file set filename for client request rendezvous
-D file set filename for client diag request rendezvous
lsm:vold: Error: volume
volume_name
: Logging daemon killed by
\
signal
signal_number
[ core dumped ]
Clarification: Someone killed the logging daemon.
User Action: If required, restart the daemon with a call to voliod logio.
lsm:vold: Error: /dev/volevent:
error_message
lsm:vold: Error: cannot open /dev/volconfig:
error_message
lsm:vold: Error: Cannot kill existing daemon, pid=
process_id
Clarification: An attempt to kill an existing vold process with a SIGKILL signal has failed. This might be due to the process being in an unkillable kernel state perhaps because of a hung I/O or a missing I/O interrupt. There may be disk driver error messages in the /dev/osm buffer.
User Action: Try typing cat /dev/osm to see if any other messages have been output to the console device. If possible, use crash to determine the state of the process. If the process is asleep waiting for an I/O completion, then any disk driver error messages that have occurred might point to the solution. Failing this, a reboot is recommended.
lsm:vold: Error: /dev/voliod: VOL_LOGIOD_CHECK failed
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reinstall of the LSM package. If this fails, contact Customer Support.
lsm:vold: Error: /dev/voliod: VOL_LOGIOD_KILL failed
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Error: All transactions are disabled
Clarification: This message may appear with the message Disk group disabled by errors if the disk group to be disabled is the root disk group. The continued use of the system could be dangerous since any configuration changes required (including error handling cases) could cause the loss of ability to perform I/O to a volume. Because this includes the root volume, this situation could, if uncorrected, cause the system to hang.
User Action: This is a fatal error. All copies of the bootable root disk have failed. Recovery from this situation will require booting from floppy or from a disk unconnected with LSM. It may then be necessary to remove the LSM rootable disk configuration by using the volunroot command. See the LSM installation instructions for details. Once this has been achieved, the root disk group can be reinitialized to reestablish the database and log areas.
lsm:vold: Error: Cannot get all disk groups from the kernel
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reinstall of the LSM package. If this fails, contact Customer Support.
lsm:vold: Error: Cannot get all disks from the kernel
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by an LSM reconfiguration. If this fails, contact Customer Support.
lsm:vold: Error: Cannot get kernel transaction state
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting the vold daemon. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration LSM. If this fails, contact Customer Support.
lsm:vold: Error: Cannot get private storage from kernel
Clarification:
User Action:
lsm:vold: Error: Cannot get private storage from kernel
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration LSM. If this fails, contact Customer Support.
lsm:vold: Error: Cannot get private storage size from kernel
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration LSM. If this fails, contact Customer Support.
lsm:vold: Error: Cannot get record name from the kernel: error_message
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration LSM. If this fails, contact Customer Support.
lsm:vold: Error: Cannot not make directory directory_path
Clarification: When trying to create the specified directory, vold got a failure.
User Action: Try creating the directory manually and then issue the command voldctl enable.
lsm:vold: Error: Cannot recover operation in progress
Failed to get group
group_name
from the kernel
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Error: Cannot start usage_type volume, no valid complete plexes
Clarification: No usable plexes remain for either the root or swap volume. This error is fatal and will result in the message System startup failed also appearing and the system being shutdown.
User Action: This is generally an unrecoverable error and will likely require a reload of the system from backups.
lsm:vold: Error: Cannot start usage_type volume, no valid plexes
Clarification No usable plexes remain for either the root or swap volume. This error is fatal and will result in the message System startup failed also appearing and the system being shutdown.
User Action: This is generally an unrecoverable error and will likely require a reload of the system from backups.
lsm:vold: Error: Cannot start usage_type volume, volume state is invalid
Clarification: The volume is not in a state that can be recovered from. This might be because of corruption of the databases or because of an invalid use of the vold interfaces without the use of the utilities.
User Action: This is generally an unrecoverable error and will require reloading of the system from backups.
lsm:vold: Error: Cannot store private storage into the kernel
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Error: Differing version of vold installed
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Error: Disk
disk_name
, group
group_name
, device
device_name
:
\
not updated with new host ID
Error:
error_message
Clarification: If the host ID for a system is changed using the voldctl init command then all disks in all imported disk groups will need to have the host ID changed to the new ID. If the host ID for a disk cannot be changed, then this message will be displayed. Other problems might also exist for this disk.
User Action: The contents of the disk should be evacuated elsewhere and the disk should be reinitialized.
lsm:vold: Error: Disk group group_name , Disk disk_name : Cannot auto-import group: error_message
Clarification: The disk group group_name, could not be reimported after a system restart. The reason is given as part of the error message. Other error messages may appear which provide more information on what went wrong. Any volumes in the disk group will be unavailable until the error condition is fixed and the disk group is reimported.
User Action: Clear the error condition, if possible, and then import the disk group by hand with voldg import. After importing, you should restart all volumes with voldg -g groupname -sb.
lsm:vold: Error: Disk group
group_name
, Disk
disk_name
: Group name collides with
\
record in rootdg
Clarification: The disk group name group_name, for the disk group being imported from the named disk, collides with a configuration record in the rootdg disk group. Disk groups must have names that do not match any records in the root disk group.
User Action: If you want to import the disk group, you will have to rename the conflicting record in rootdg to some other name.
lsm:vold: Error: Disk group
group_name
: Cannot recover temp database
error_message
Clarification: The temp database stored in the root file system could not be opened or read. Other messages will detail the error. This may happen because of an I/O error or a problem in the file system.
User Action: The system should be rebooted and the operation retried.
lsm:vold: Error: Disk group group_name : Disabled by errors
Clarification: This message can appear if the last configuration database or last kernel log area for a disk group became disabled. This could have been due to an I/O error or some other condition. Other messages preceding this one are likely to highlight the root cause.
User Action: Any remaining active volumes should be backed up. The disk group will have to be reinitialized and the disks added again to the group to recover.
lsm:vold: Error: Disk group group_name : Errors in some configuration copies:
Clarification:
One or more on-disk database copies were found to contain errors. As
a result, the disk group could not be imported. This is probably
due to a disk I/O error, or to blocks of a configuration copy
being overwritten within invalid contents. Check for messages from
the disk driver.
Errors pertaining to specific configuration copies are listed on
successive lines. These lines can be in either of the following
forms:
File
filename
:
error_message
: Block
number
:
error_message
Disk
diskname
, copy
copy_number
:
error_message
: Block
number
:
error_message
Lines beginning with
File
indicate an error in the special configuration copy file used for storing
nonpersistent disk group information. Lines beginning with
Disk
indicate failure of a persistent configuration copy stored on a disk. The
copy number indicates which of the disk's configuration copies contains the
error.
User Action: If one or more disks for the disk group are currently inaccessible (such as due to a cabling error), make the disks accessible and try to import the disk group again with voldg import. Otherwise, the disk group is probably no longer usable and will have to be recreated. All volume configuration information for the disk group is lost.
lsm:vold: Error: Disk group
group_name
: Reimport of disk group failed:
error_message
Clarification: The reload of a disk group into the kernel failed. This could be because the log size for the kernel may not be set or because of some other error in the import procedure. Other messages should indicate the true cause of the failure.
User Action: The operation should be retried unless some other error message leads to a suggested course of action. If this fails, the system should be rebooted.
lsm:vold: Error: Disk group group_name : update failed: error_message
Clarification: This message occurs because a database update failed completely. No complete copy of the database could be written for the disk group. The disk group will be disabled and further access for configuration changes will be disallowed. If this error occurs for the root disk group, it will probably be necessary to reinstall the system.
User Action: Any volumes still active in the disk group should be backed up. The disk group will then have to be reinitialized and the disks added again to it.
lsm:vold: Error: Exec of /sbin/voliod failed
Clarification: An exec of /sbin/voliod failed.
User Action: Check the existence and permissions of the /sbin/voliod command. Try executing the command manually to ensure that it can be run.
lsm:vold: Error: Failed to store commit status list into kernel:
error_message
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Error: Fork of logio daemon failed
Clarification: The creation of a process that could then be used as a logging daemon failed.
User Action: Check for messages explaining the reason that a fork(2) call failed. Retry the operation.
lsm:vold: Error: GET_VOLINFO ioctl failed:
error_message
lsm:vold: Error: Version number of kernel does not match vold
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Error: Get of current rootdg failed
Clarification: An attempt to retrieve the rootdg from the kernel failed. This might be because of a kernel vold inconsistency or could also be because of a version difference between vold and the kernel.
User Action: Check that the correct version of vold and the kernel are installed. Other messages might suggest other problems in a prior attempt at loading a configuration and possible courses of action. If this fails, contact Customer Support.
lsm:vold: Error: No convergence between root disk group and disk list
Disks in one version of rootdg:
disk_name
type=
disk_type
info=
disk_info
Disks in alternate version of rootdg:
disk_name
type=
disk_type
info=
disk_info
Clarification: This message can appear when vold is not running in autoconfigure mode (see the vold(8) reference page) and when, after several retries, it cannot resolve the set of disks belonging to the root disk group. The algorithm for non-autoconfigure disks is to scan disks listed in the /etc/vol/volboot file and then examine the disks to find a database copy for the rootdg disk group. The database copy is then read to find the list of disk access records for disks contained in the group. These disks are then examined to ensure that they contain the same database copy. As such, this algorithm expects to gain convergence on the set of disks and the database copies contained on them. If a loop is entered and convergence cannot be reached, then this message will appear and the root disk group importation will fail.
User Action: Reorganizing the physical locations of the devices attached to the system may break the deadlock. If this fails, contact Customer Support.
lsm:vold: Error: Open of directory directory_path failed
Clarification: When vold was trying to create node files for the volumes, it was unable to open the directory in which the nodes were to be created.
User Action: Check for other errors that suggest why the directory might be missing or if the permissions might be incorrect. Fix the condition to allow vold to open or create the directory, then issue the command voldctl enable.
lsm:vold: Error: Read of directory directory_path failed
Clarification: The node directory could not be read when vold was trying to scan for volume nodes.
User Action: Check for other messages that might suggest why the directory is inaccessible. Try reading the directory manually if the directory is corrupted, then try removing and recreating it and then restarting vold.
lsm:vold: Error: Unexpected configuration tid for group group_name found in kernel
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Error: Unexpected error during
usage_type
volume reconfiguration:
error_message
Clarification: A record lock for the volume could not be acquired as part of the initial volume setup for either a root or swap volume. This is most likely to occur under low memory conditions.
User Action: Other messages may suggest an alternate course of action. Otherwise, this is generally an unrecoverable error and will require either the boot of an alternate root device or reloading of the system from backups.
lsm:vold: Error: Unexpected error fetching disk for
usage_type
volume:
error_message
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Error: Unexpected values stored in the kernel
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Error: VOL_RESET_KERNEL failed: a volume or plex device is open
or
lsm:vold: Error: VOL_RESET_KERNEL failed: error_message
Clarification: An attempt at resetting the kernel state with a vold -r reset command failed because all the LSM objects in the kernel were not closed. If any volumes are in use, then the reset cannot be performed. This may also happen if a reset was requested on a system with root volumes. Root volumes are, by definition, never closed and so a reset cannot be performed.
User Action: If a reset is really desired, then checking the state of the volumes and any mounted file systems should result in information about who might have them open. Unmounting all volumes and killing any processes accessing the volumes should allow the reset to occur.
lsm:vold: Error: mode : Unrecognized operating mode
Clarification: An unknown mode string was entered following a -m option.
User Action: Select a valid mode from the vold(8) reference page and try again.
lsm:vold: Error: cannot open /dev/voliod: error_message
Clarification: The open of the /dev/voliod file can only fail if the device node is missing or has an incorrect major or minor number.
User Action: Check the existence and values of the file and make sure that LSM was correctly installed.
lsm:vold: Error: cannot open argument : error_message
Clarification: The tracefile specified on the command line could not be opened in append mode. The error message supplied should explain the reason.
User Action: Select an alternate tracefile name that can be created or appended to.
lsm:vold: Error: cannot open volconfig_device : Device is already open
or
lsm:vold: Error: cannot open volconfig_device : error_message
Clarification The exclusive open device (/dev/volconfig) is already open. Only one vold process can be active on the system at one time. Subsequent attempts at starting vold or opening the device will result in this message.
User Action: Check for other running vold processes. The voldctl mode will report if vold is currently active.
lsm:vold: Error: enable failed: error_message
Clarification: This message may occur during an initial startup of vold. If changing to enabled mode when this error occurs, failures could be due to problems with the creation of the portal or with connection to the kernel. If changing from an enabled state to a disabled state, then problems could occur with removing the disk groups from the kernel because of such things as volumes in use.
User Action: Evaluate other error messages occurring with this one to determine the root cause of the problem. Make changes suggested by the other errors and then retry the command.
lsm:vold: Error: failed to create daemon: fork failed: error_message
Clarification: The call to fork(2) to generate a background vold process failed.
User Action: Check for messages explaining the reason that a fork(2) call failed. Retry the operation.
lsm:vold: Error: volume volume_name : Wait for logging daemon failed
Clarification: The wait called to wait for the existence of the daemon process did not execute correctly. This can only happen if the ioctl does not correctly match the command required, perhaps because of a mismatch between the voliod command and the kernel versions or perhaps because of an incorrect minor number for the /dev/voliod device.
User Action: Check the existence and permissions of the /dev/voliod device.
lsm:vold: FATAL Error: Disk group rootdg: Inconsistency -- Not loaded into kernel
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: FATAL Error: Group group_name : Cannot update kernel
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: FATAL Error: Interprocess communication failure: error_message
Clarification: The portal to client utilities has returned a failure. This is a fatal error since without a portal to clients, vold cannot do anything useful.
User Action: Check for other errors suggesting the reason for portal failure. Restart vold. If problems persist, reboot the system.
lsm:vold: FATAL Error: Invalid status stored in kernel
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Warning: Cannot create device path : error_message
Clarification: The mknod(2) call made by vold to create a device node failed. The reason for the error should be displayed.
User Action: Fix the reason indicated for node creation failure and then issue the command voldctl enable.
lsm:vold: Warning: Cannot exec /sbin/rm to remove directory_path : error_message
Clarification: An exec of /sbin/rm failed.
User Action: Ignore the error. It is not serious if the directory could not be removed.
lsm:vold: Warning: Cannot fork to remove directory directory_path : error_message
Clarification: The call to fork(1) to generate a process that could then exec rm(2) failed.
User Action: Ignore the error. It is not serious if the directory could not be removed.
lsm:vold: Warning: Disk device_name in kernel not a recognized type
Clarification: The disk type of a disk in the kernel does not match any known disk type. This can only occur if vold and the kernel are in an inconsistent state.
User Action: Try stopping and restarting vold. If this fails then reconfigure LSM. If this fails, contact Customer Support.
lsm:vold: Warning: Disk disk_name names group group_name , but group ID differs
Clarification: As part of a disk group import, a disk was discovered that had a mismatched disk group name and disk group ID. This disk will not have been imported. This can only happen if two disk groups of the same name exist that have different disk group ID values. In that case, one group will be imported along with all its disks and the other group will not. This message will appear for disks in the un-selected group.
User Action: If it turns out that the disk should be imported into the group, then this will have to be done by adding the disk to the group at a later stage. It will not happen automatically as part of the import. All configuration information for the disk will also be lost.
lsm:vold: Warning: Disk group group_name is disabled, disks not updated with \ new host ID
Clarification: If the host ID for a system is changed using the voldctl init command then all disks in all imported disk groups will need to have the host ID changed to the new ID. If a disk group is found in the imported but disabled state, then the host ID will not be changed.
User Action: The host ID will need to be cleared using the voldisk clearimport command for each disk, and then the disk group should be reimported.
lsm:vold: Warning: Disk group
group_name
: Disk group log may be too small
Log size should be at least
number
blocks
Clarification: The log areas for the disk group have become too small for the size of configuration currently in the group. This should usually never happen without first displaying a message about the database area size. This message only occurs during disk group import; it occurs if the disk was inaccessible while new database objects were added to the configuration, and the disk was then made accessible and the system restarted.
User Action: If this situation does occur, then the disks in the group will have to be explicitly reinitialized with larger log areas. See the reference page for voldisk(8). To reinitialize all the disks, they must be detached from the group with which they are associated and then reinitialized and readded. The group should then be deported and reimported for the changes to the log areas for the group to take effect.
lsm:vold: Warning: Disk group group_name : Errors in some configuration copies:
Clarification: One or more on-disk database copies were found to contain errors. As a result, the disk group could not be imported. This is most likely to be due to a disk I/O error, or to blocks of a configuration copy being overwritten within invalid contents. Check for messages from the disk driver. Providing that other copies of the database can be successfully read, the system will continue and the disk group import or initial vold enable operation should succeed. If the database copy can subsequently be written to, then this message will not recur.
Errors pertaining to specific configuration copies are listed on successive lines. These lines can be in either of the following forms:
File
filename
:
error_message
: Block
number
:
error_message
Disk
diskname
, copy
copy_number
:
error_message
: Block
number
:
error_message
Lines beginning with File indicate an error in the special configuration copy file used for storing nonpersistent disk group information. Lines beginning with Disk indicate failure of a persistent configuration copy stored on a disk. The copy number indicates which of the disk's configuration copies contains the error.
User Action: This message is likely to occur once due to an I/O failure and then not reoccur. If it does reoccur, then it may be necessary to remove the disk and reinitialize it to clear the condition. If all configuration copies for a disk group become unusable, then the disk group itself becomes unusable and must be recreated. If the rootdg disk group becomes unusable, LSM may need to be reconfigured. In this case, if root file system is on a volume, then the operating system itself may need to be reinstalled.
lsm:vold: Warning: Error in volboot file:
error_message
Entry: disk
disk_name disk_type disk_info
Clarification: This message occurs when an entry in the volboot file does not contain the correct information to define a valid disk access record.
User Action: Remove the entry using the voldctl rmdisk command and add it again using voldctl adddisk.
lsm:vold: Warning: Failed to update voldinfo area in kernel: error_message
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Warning: Field too long in volboot file:
Entry: disk
disk_name disk_type disk_info
Clarification: The volboot file is maintained by vold and voldctl and should never normally exhibit this problem. This problem might indicate some corruption of the volboot file or could also be the result of manual editing of the file.
User Action: The offending entry could try to be removed by use of the voldctl rmdisk command. If this fails, volboot may have to be reinitialized using a voldctl init command.
lsm:vold: Warning: Get of record record_name from kernel failed: error_message
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of LSM. If this fails, contact Customer Support.
lsm:vold: Warning: Plex plex_name for usage_type volume is stale or unusable
Clarification: This message is output to alert the user to the failure of one or more plexes of either the root or swap volume. The system may be able to continue depending on the existence of other usable plexes for the volume.
User Action: The failed plex should be repaired by either reattaching the plex to the volume once the system is booted, or by evacuating and replacing the disk on which the failed plex resides if it is thought that the disk is going bad.
lsm:vold: Warning: cannot remove group group_id from kernel: error_message
Clarification: Some inconsistency between vold and the kernel has caused an ioctl to fail. This could be caused by the use of older versions of vold or the kernel, or it could be due to a bug in LSM.
User Action: Try stopping and restarting vold. If this fails then a reboot of the system should be attempted, possibly followed by a reconfiguration of the LSM package. If this fails, contact Customer Support.
lsm:vold: Warning: response to client client number failed: error_message
Clarification: The portal to client utilities has returned a failure. This is a fatal error since without a portal to clients, vold cannot do anything useful. This could be caused by a STREAMS error or some other communications problem with the client.
User Action: Check for other errors suggesting the reason for portal failure. Restart vold. If problems persist, reboot the system.
![[Previous Section]](PREV.GIF)
The following are the kernel level error messages.
NOTICE: message on volume device hex_device_number ( volume_name ) in diskgroup group_name
Clarification: This is caused by a driver above the LSM level calling the LSM volprint() function. This usually happens when a driver detects some error condition in LSM and want to display the error.
User Action: No action necessary, unless specified in a supplied string.
NOTICE: io/vol.c(volerror): Correctable
type
error on volume
volume_name
,e
plex
plex_name
, block
block_number
Clarification: A correctable I/O error was detected and corrected. A correctable I/O error is one where a read error from an underlying device driver could be corrected by reading the data from an alternate mirror copy and then writing it back to the failed mirror.
User Action: If the I/O could have been completed by reading from an alternate mirror but the writeback to the failed mirror still failed, the mirror will be detached. This failure will cause the exception handling code to be entered, which will result in the volume's error recovery policy being followed. This usually results in either a mirror or the volume becoming detached. The user must intervene to reattach the mirror (volplex att), to bring back the failed mirror copy. If the volume was detached, then the data contained on it is unrecoverable and will have to be restored from backups.
NOTICE: io/vol.c(volerror): Uncorrectable type error on volume volume_name , \ plex plex_name , block block_number
Clarification: Following an I/O error from one mirror, an attempt to reread the data from an alternate mirror failed. This could be because no other mirrors exist or could be because the other mirrors also had I/O failures.
User Action: This failure will cause the exception handling code to be entered, which will result in the volume's error recovery policy being followed. This can have effects ranging from detaching a mirror to disabling the volume. The user must intervene to reattach the mirror (volplex att), to bring back the failed mirror copy. If the volume was detached, then the data contained on it is unrecoverable and will have to be restored from backups.
NOTICE: lsm: Can't close disk
disk_name
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
error_number/error_number
Clarification: This is unlikely to happen; closes cannot fail.
User Action: None.
NOTICE: lsm: Can't open device disk_name , device busy or inaccessible.
Clarification: The named disk cannot be accessed.
User Action: Turn on the drive.
WARNING: io/vol.c(volexcept): No volume error daemon - Cannot Log plex detach, \ detaching volume
Clarification: No voliod process was running and able to log a detach record for a mirror that is being detached due to an I/O error. This is a fatal error that causes future access to the volume to be rejected, because any system failure coming after additional I/O would not be able to detect the failure of the mirror and mirror inconsistencies might then occur.
User Action: Although it is too late to rescue this volume, at least one voliod process should be started as soon as possible (using voliod set 2). The failed volume will have to be stopped and restarted, then reloaded from backups. Mirrors will have become inconsistent and so any attempt at using the data on the volume could prove disastrous.
WARNING: volklog_dgfree: Can't clear group commit log record for group disk_group
Clarification: This can occur if a log flush to disk could not be performed because no valid log copies remained. This is likely to compromise the ability of the LSM to recover from any further I/O errors.
User Action: Disks should be added to the system such that new viable logging areas can be generated. Alternatively, failed disks should be removed and replaced with working devices.
WARNING: volklog_dgfree: Can't free kernel logging area for vol_reset_kernel of group disk_group
Clarification: A free of the logs for a disk group failed because either no valid log areas remained for flushing or some log records remained in the log before the clear operation was requested.
User Action: No user action can be taken here; this is a LSM internal error. Contact Customer Support.