KAPL12035-E
|
The version of the kernel supported by the installed HDLM does not match the currently running kernel version.
|
- Details
The version of the kernel to which installed HDLM has adjusted and the kernel that is running now is not corresponding. There is a possibility of installing the package of the kernel after installing HDLM.
- Action
Install HDLM that adjusts to the kernel that is running now.
|
|
KAPL12036-E
|
The HDLM file is invalid. File name = aa...aa
|
- Details
A file necessary for processing HDLM cannot be found. Alternatively, the content of a file is invalid.
aa...aa: Name of file where error was detected.
- Action
Reinstall an HDLM.
|
KAPL12303-E
|
A file or directory does not exist. File name = aa...aa
|
- Details
aa...aa: The name of the non-existent file
- Action
- For dracut command:
If the file name displayed in the message is the HDLM file name shown below, HDLM may not be installed correctly. In this situation, re-install HDLM.
/etc/dracut.conf.d/hdlm-dracut.conf
- If the file name displayed in the message is another file name
The OS (kernel) or the HBA driver may not be installed correctly. Confirm sure the
existence of the files.
|
KAPL12321-E
|
An invalid root partition is specified in the file. File name = aa...aa
|
- Details
aa...aa: The name of the file containing the invalid root partition entry
- Action
Change the root partition specified in the /etc/fstab file to a SCSI
or HDLM device, or specify settings so that HDLM manages the device that is
listed next to the root partition specified in the
/etc/fstab file.
|
KAPL12323-I
|
The insertion of the module was started. Module name = aa...aa
|
- Details
The insertion of the module was started.
aa...aa: The name of the module being inserted
- Action
None.
|
KAPL12324-E
|
The module could not be inserted. Module name = aa...aa
|
- Details
The module could not be inserted.
aa...aa: The name of the module whose insertion has failed
- Action
Confirm that the system environments are not changed after creating the initial ramdisk image file.
Check whether there is a mistake in the initial ramdisk image file specified in the config file of the boot loader.
|
KAPL12325-I
|
The command started. Command name = aa...aa
|
- Details
aa...aa: The started command
- Action
None.
|
KAPL12326-E
|
The command could not execute. Command name = aa...aa
|
- Details
aa...aa: The failed command
- Action
- For dracut command:
Perform the following confirmation corresponding to the output command, and then retry. Re-execute the dracut command after performing the next check according to the outputted command.
And if the error message is outputted before this message, remove the cause of the error with reference to the contents of the message.
- cp:
Confirm that there is enough unused capacity and that the user has write permission in the root directory (/).
- dlmcfgmgr:
Confirm that the version of the OS has not changed since you made the initial ramdisk image file.
Take action according to the contents output in the log of the dlmcfgmgr utility.
Confirm that the user has write permission in the root directory (/).
- dlnkmgr:
Confirm that HDLM has been configured.
Take action according to the contents output in the log of the dlmcfgmgr utility.
Confirm that the user has write permission in the root directory (/).
- mkdir:
Confirm that there is enough unused capacity and that the user has write permission in the following directory:
- mount:
Confirm that there is unused capacity in the loop device.
- umount:
A temporary file remains, so do the following:
Unmount
/etc/opt/DynamicLinkManager/tmp/initrdmnt.$$ ($$ is a process ID).
Remove the /etc/opt/DynamicLinkManager/tmp/initrdmnt.$$ ($$ is a process ID) file.
Execute the DLMgetras utility for collecting HDLM error information, and then contact
your HDLM vendor or the maintenance company if there is a maintenance
contract for HDLM. For details on the DLMgetras utility, see DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12327-E
|
An invalid entry is registered in the file. File name = aa...aa
|
- Details
aa...aa: The name of the file containing the invalid entry
- Action
- For dracut command:
Take the following actions depending on the file name output, and then reexecute the dracut command.
- In the case of /etc/lvm/lvm.conf file
Edit the following lines as described in BOOT_SETTING_UP_XEN=GUID-07C2F5FE-7561-46DC-B423-A2C9B671F65B=5=EN=.html or BOOT_PERFORMING_A_RE-INSTALLATION_OF_HDLM=GUID-05AE3AE2-401F-4E18-A655-C9D5A0884CB8=4=EN=.html:
- filter or global_filter
- write_cache_state
- types
- md_component_detection
|
KAPL12339-E
|
The HDLM device required to start the host could not be found.
|
- Action
This message is always preceded by some other specific error message.
|
KAPL12340-E
|
A backup of the configuration definition file was used to configure the HDLM devices. Confirm that the HDLM devices are properly configured, and then make them management targets before using them again.
|
- Details
This message is output when the following conditions are met:
When the configuration definition file becomes corrupted, because, for example, a user directly edited the file.
When the configuration definition file becomes corrupted, because, for example, the system stopped while a program was creating the configuration definition file.
- Action
Make sure that the all the HDLM device and LDEV associations are correct. If all the associations are correct, make any HDLM devices management targets that are not management targets before using them again.
If one or more associations are not correct, execute the DLMgetras utility for
collecting error information, and then contact your HDLM vendor or your
maintenance company, if you have an HDLM maintenance contract.
|
KAPL12342-I
|
Execution of bootup script completed.
|
- Action
None.
|
KAPL12350-E
|
The HDLM device corresponding to root device could not be found. Root device name = aa...aa
|
- Details
aa...aa: Root device name
- Action
Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12351-I
|
The collection of files for HDLM started.
|
- Details
The collection of files for HDLM started.
- Action
None.
|
KAPL12352-I
|
The collection of files for HDLM completed.
|
- Details
The collection of files for HDLM completed.
- Action
None.
|
KAPL12355-I
|
The utility for creating an HDLM boot-up service started.
|
- Details
The utility for creating an HDLM boot-up service started.
- Action
None.
|
KAPL12356-I
|
The utility for creating an HDLM boot-up service ended.
|
- Details
The utility for creating an HDLM boot-up service ended.
- Action
None.
|
KAPL12357-I
|
A required entry could not be found in the system file.
|
- Details
A required entry could not be found in the system file.
- Action
None.
|
KAPL12358-E
|
The utility for creating an HDLM boot-up service ended abnormally. Code = aa...aa, Errno = bb...bb. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
|
- Details
aa...aa: Internal code (decimal number)
bb...bb: Error number (decimal number)
- Action
Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see "DLMgetras utility for collecting HDLM error information" on page DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12359-I
|
The entered timeout value is invalid. The utility for creating an HDLM boot-up service will execute with the default value. Parameter = aa...aa
|
- Details
aa...aa: Parameter with invalid value specified (string)
- Action
None.
|
KAPL12360-I
|
The utility for creating an HDLM boot-up service is executing. Elapsed time = aa...aa
|
- Details
aa...aa: Elapsed time/Specified time (seconds)
- Action
None.
|
KAPL12361-E
|
The specified parameter of the utility for changing HDLM device names is invalid. Parameter = aa...aa
|
- Details
aa...aa: Specified parameter
- Action
Specify the correct parameters and then re-execute the utility for changing HDLM device names (dlmchname).
|
KAPL12362-W
|
Usage: aa...aa [-f | -o]
|
- Details
aa...aa: dlmchname
- Action
Specify the correct parameters and then re-execute the utility for changing HDLM device names (dlmchname).
|
KAPL12363-E
|
Memory could not be allocated. Size = aa...aa
|
- Details
aa...aa: Target memory size (decimal number)
- Action
If the actual memory size is insufficient, increase the actual memory size. If any running applications are not needed, stop those applications.
If the actual memory size is sufficient, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
For details on the DLMgetras utility, see DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12364-E
|
An internal error occurred in the file operation. File name = aa...aa, Code = bb...bb, Errno = cc...cc. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
|
- Details
aa...aa: File name
bb...bb: Internal code (decimal number)
cc...cc: Error number (errno) (decimal number)
- Action
Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
For details on the DLMgetras utility, see DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12365-E
|
Multiple instances of the utility for changing HDLM device names and the utility for managing the HDLM configuration cannot be executed concurrently. Wait until the utility for changing HDLM device names or the utility for managing the HDLM configuration ends, and then re-execute the utility for changing HDLM device names.
|
- Action
Do either 1 or 2, as appropriate:
1. Wait until the utility for changing HDLM device names (dlmchname) ends, and then re-execute it.
2. Wait until the utility for managing the HDLM configuration (dlmcfgmgr) ends, and then re-execute the utility for changing HDLM device names (dlmchname).
|
KAPL12366-E
|
The file format is invalid. File name = aa...aa. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
|
- Details
aa...aa: /etc/opt/DynamicLinkManager/.dlmfdrv.conf
- Action
Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
For details on the DLMgetras utility, see DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12367-E
|
You lack permissions required to execute the utility for changing HDLM device names. Execute the utility as a user who has root permissions.
|
- Action
Re-execute the utility for changing HDLM device names (dlmchname) as a user who has root permissions.
|
KAPL12368-E
|
An error occurred during creation of an HDLM temporary file. File name = aa...aa, Code = bb...bb, Errno = cc...cc
|
- Details
aa...aa: File name
/etc/opt/DynamicLinkManager/.dlmfdrv.conf
/etc/opt/DynamicLinkManager/.dlmfdrv.unconf
/etc/opt/DynamicLinkManager/dlmchname.conf
bb...bb: Internal code (decimal number)
cc...cc: Error number (errno) (decimal number)
- Action
Verify that the root directory (/) has enough unused capacity.
If it has enough unused capacity, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
For details on the DLMgetras utility, see DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12369-E
|
The file could not be created. File name = aa...aa, Code = bb...bb, Errno = cc...cc
|
- Details
aa...aa: File name
/etc/opt/DynamicLinkManager/.dlmfdrv.conf
/etc/opt/DynamicLinkManager/.dlmfdrv.unconf
/etc/opt/DynamicLinkManager/dlmchname.conf
bb...bb: Internal code (decimal number)
cc...cc: Error number (errno) (decimal number)
- Action
Verify that the root directory (/) has enough unused capacity.
If it has enough unused capacity, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
For details on the DLMgetras utility, see DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12370-E
|
An internal error occurred in the utility for changing HDLM device names. Code = aa...aa, Errno = bb...bb. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
|
- Details
aa...aa: Internal code (decimal number)
bb...bb: Error number (errno) (decimal number)
- Action
Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
For details on the DLMgetras utility, see DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12371-E
|
A file could not be opened. File name = aa...aa, Code = bb...bb, Errno = cc...cc. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
|
- Details
aa...aa: File name
/etc/opt/DynamicLinkManager/.dlmfdrv.conf
/etc/opt/DynamicLinkManager/.dlmfdrv.unconf
/etc/opt/DynamicLinkManager/dlmchname.conf
bb...bb: Internal code (decimal number)
cc...cc: Error number (errno) (decimal number)
- Action
Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
For details on the DLMgetras utility, see DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12372-W
|
The entered value is invalid.
|
- Action
After the KAPL12374-I message is output, enter the correct y/n value.
|
KAPL12373-E
|
The entered value is invalid. The utility for changing HDLM device names will now stop. Re-execute the utility.
|
- Action
Re-execute the utility for changing HDLM device names (dlmchname).
|
KAPL12374-I
|
This operation will change the HDLM device configuration. Do you want to continue? [y/n]:
|
- Action
Enter y to continue. Enter n to cancel.
|
KAPL12375-W
|
Processing of the utility for changing HDLM device names was interrupted. Re-execute the utility.
|
- Action
Re-execute the utility for changing HDLM device names (dlmchname).
|
KAPL12376-E
|
The value entered for the storage system serial number and LU number is incorrect in the device name change definition file. Incorrect value = aa...aa
|
- Details
aa...aa: Incorrect storage system serial number and LU number
- Action
If the value entered for the storage system serial number and LU number is incorrect, the incorrect value is displayed. Correct the number, and then re-execute the utility for changing HDLM device names (dlmchname).
|
KAPL12377-I
|
The utility for changing HDLM device names started: aa...aa
|
- Details
aa...aa: date and time (for example, Fri Aug 23 19 : 12 : 50 2004)
- Action
None.
|
KAPL12378-I
|
Restart the machine for configuration changes to take effect.
|
- Action
Change the name of the HDLM device in applications that use HDLM, and then restart the machine for the configuration changes to take effect.
|
KAPL12379-I
|
The utility for changing HDLM device names finished normally.
|
- Action
None.
|
KAPL12380-E
|
The file does not exist. File name = aa...aa
|
- Details
aa...aa: File name
/etc/opt/DynamicLinkManager/.dlmfdrv.conf
/etc/opt/DynamicLinkManager/dlmchname.conf
- Action
If the configuration definition file (.dlmfdrv.conf) file does not exist, execute the dlmstart utility and configure the HDLM devices. For details on the dlmstart utility, see DLMSTART_UTILITY_FOR_STARTING_HDLM=GUID-2E6FA911-E868-4B28-9B6F-5A1A23906AF4=2=EN=.html.
If the device name change definition file (dlmchname.conf) does not exist, execute the utility for changing HDLM device names (dlmchname) with the -o option and create the device name change definition file (dlmchname.conf). For details on the dlmchname utility, see DLMCHNAME_HDLM_DEVICE_NAME_REPLACEMENT_UTILITY=GUID-2167435C-559B-4E91-B215-288F9AC58030=2=EN=.html.
|
KAPL12381-E
|
A required system file could not be found. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
|
- Action
Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see "DLMgetras utility for collecting HDLM error information" on page DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12382-E
|
A required entry could not be found in the system file. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
|
- Action
Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM. For details on the DLMgetras utility, see "DLMgetras utility for collecting HDLM error information" on page DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12386-E
|
An internal error occurred in the utility for changing HDLM device names. File name = aa...aa, Code = bb...bb, Errno = cc...cc. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
|
- Details
aa...aa: File name
bb...bb: Internal code (decimal number)
cc...cc: Error number (errno) (decimal number)
- Action
Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
For details on the DLMgetras utility, see DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12387-E
|
An internal error occurred in the utility for changing HDLM device names. Execute the DLMgetras utility to collect error information, and then contact your vendor or maintenance company.
|
- Action
After restarting the system, perform either of the following operations:
Make sure that the HDLM device is not being used, and then re-execute the command.
Execute the command with the -f option specified, and then restart the system.
If the HDLM device name cannot be changed by performing either of the above operations, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.
For details on the DLMgetras utility, see DLMGETRAS_UTILITY_FOR_COLLECTING_HDLM_ERROR_INFORMATION=GUID-23937FA5-2612-443B-A4FB-FCC9CA3E70AC=3=EN=.html.
|
KAPL12388-E
|
The utility for changing HDLM device names ended abnormally.
|
- Action
Check the error message that was output just before this message, and then perform the action indicated in that error message.
|
KAPL12389-E
|
Required entries were not found in the device name change definition file.
|
- Action
-
No items subject to a name change were found in the
device name change definition file (dlmchname.conf).
For details on the utility for changing HDLM device names (dlmchname), see DLMCHNAME_HDLM_DEVICE_NAME_REPLACEMENT_UTILITY=GUID-2167435C-559B-4E91-B215-288F9AC58030=2=EN=.html
|
KAPL12390-I
|
The user terminated the operation.
|
- Action
None.
|
KAPL12391-E
|
The specified HDLM device name in the device name change definition file is already in use. HDLM device name = aa...aa
|
- Details
aa...aa: The specified HDLM device name
- Action
Review the entries in the device name change definition file (dlmchname.conf) and re-execute the utility for changing HDLM device names (dlmchname). For details on this utility, see DLMCHNAME_HDLM_DEVICE_NAME_REPLACEMENT_UTILITY=GUID-2167435C-559B-4E91-B215-288F9AC58030=2=EN=.html.
|
KAPL12392-E
|
Duplicated entries were found in the dlmchname.conf file. Duplicated entry = aa...aa
|
- Details
aa...aa: Duplicated entry
- Action
Review the entries in the device name change definition file (dlmchname.conf) and re-execute the utility for changing HDLM device names (dlmchname). For details on this utility, see DLMCHNAME_HDLM_DEVICE_NAME_REPLACEMENT_UTILITY=GUID-2167435C-559B-4E91-B215-288F9AC58030=2=EN=.html.
|
KAPL12393-E
|
The file format of the device name definition file is invalid. Incorrect line = aa...aa
Duplicated entries were found in the dlmchname.conf file. Duplicated entry = aa...aa
|
- Details
aa...aa: The incorrect line in the device name definition file (dlmchname.conf)
- Action
Review the entries in the device name change definition file (dlmchname.conf) and re-execute the utility for changing HDLM device names (dlmchname). For details on this utility, see DLMCHNAME_HDLM_DEVICE_NAME_REPLACEMENT_UTILITY=GUID-2167435C-559B-4E91-B215-288F9AC58030=2=EN=.html.
|
KAPL12394-E
|
An HDLM device specified in the device name change definition file is invalid. HDLM device name = aa...aa
|
- Details
aa...aa: The specified HDLM device name
- Action
Review the specified HDLM device name format and re-execute the utility for changing HDLM device names (dlmchname). For details on HDLM device names, see LOGICAL_DEVICE_FILES_FOR_HDLM_DEVICES=GUID-1FB8E878-1356-4536-B854-9F544BC9B9C6=2=EN=.html. For details on the dlmchname utility, see DLMCHNAME_HDLM_DEVICE_NAME_REPLACEMENT_UTILITY=GUID-2167435C-559B-4E91-B215-288F9AC58030=2=EN=.html.
|
KAPL12395-E
|
The utility for changing HDLM device names cannot be executed because the HDLM driver has not been loaded.
|
- Action
Execute the dlmstart utility and configure the HDLM devices and re-execute the utility for changing HDLM device names (dlmchname). For details on the dlmchname utility, see DLMCHNAME_HDLM_DEVICE_NAME_REPLACEMENT_UTILITY=GUID-2167435C-559B-4E91-B215-288F9AC58030=2=EN=.html.
|
KAPL12451-E
|
Logical volumes might not be set up in a multi-path configuration because the LVM cache file is enabled. Disable the LVM cache file.
|
- Action
Perform the following steps:
Check whether write_cache_state=0 is specified in the /etc/lvm/lvm.conf file. If write_cache_state=0 is not specified, specify it.
Execute /sbin/vgscan.
Check whether the following files exist. If either or both of the files exist, delete them.
/etc/lvm/.cache
/etc/lvm/cache/.cache
Create the initial RAM disk image file again. For details on the procedure, see the following:
- If an HDLM device is being used as a boot disk:
See step 9 in SETTINGS_FOR_A_MULTIPATH_BOOT_DISK_ENVIRONMENT=GUID-D1139199-D2D6-4E66-80E8-F96431212132=5=EN=.html.
- If an HDLM device is not being used as a boot disk:
Create the initial RAM disk image file for HDLM.
For details on the procedure, see Step 4. Re-create the initial RAM disk image file
in NOTES_ON_USING_LVM2=GUID-91F95B7F-B4F1-4A73-A110-536AD5C219CC=5=EN=.html.
Restart the server.
# shutdown -r now
Check whether the LVM cache file is present by using the following commands. If the
file is present, move to step 7. If it is not present, the recovery
procedure is complete.
# ls /etc/lvm/.cache
# ls /etc/lvm/cache/.cache
Perform the check described in CONFIRMING_THAT_THE_LOGICAL_VOLUME_IS_IN_A_MULTI-PATH_CONFIGURATION=GUID-154677B3-273B-40F8-A0AF-4351382F45F9=2=EN=.html.
If a multi-path configuration is being used, clear the LVM cache by executing the following command. This ends the procedure.
If a multi-path configuration is not being used, clear the LVM cache by executing
the following command, and then go to step 8. You can also restart
the server instead of performing steps 8 and 9.
# rm /etc/lvm/.cache
# rm /etc/lvm/cache/.cache
Deactivate the volume group containing the logical volume that is not operating in a multi-path configuration.
# vgchange -an volume-group-name
Reactivate the volume group.
# vgchange -ay volume-group-name
|
KAPL12551-E
|
The utility for setting HDLM driver option can be executed with the name dlmsetopt only.
|
- Action
Change the utility name back to dlmsetopt, and then execute it.
|
|
KAPL12552-E
|
Multiple instances of the utility for setting HDLM driver option
(dlmsetopt) cannot execute concurrently.
|
- Action
-
Wait until the executing utility finishes, and then
re-execute dlmsetopt.
If two or more utilities are not executing simultaneously,
delete the following files, and then re-execute the utility:
/etc/opt/DynamicLinkManager/.dlm_modules.conf.lock
|
|
KAPL12553-W
|
For Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, or
Red Hat Enterprise Linux 9: Usage:
/opt/DynamicLinkManager/bin/dlmsetopt {-r retrycount | -inqt InquiryTimeout | -inqr
InquiryRetry | -epr ErrorPathRetry | -epd ErrorPathDelay | -prsup ReserveStatus |
-h}
For OSs other than the above:Usage:
/opt/DynamicLinkManager/bin/dlmsetopt {-r retrycount | -inqt InquiryTimeout | -inqr
InquiryRetry | -epr ErrorPathRetry | -epd ErrorPathDelay | -h}
|
- Action
-
Refer to DLMSETOPT_UTILITY_FOR_SETTING_HDLM_DRIVER_OPTIONS=GUID-2D0A9E93-105D-4255-AECD-CC67B3B20DD6=2=EN=.html, and then
specifying the correct argument. Then, re-execute the
dlmsetopt utility.
|
KAPL12554-I
|
The utility for setting HDLM driver option has started.
|
- Action
None.
|
KAPL12555-I
|
The utility for setting HDLM driver option completed normally.
|
- Action
None.
|
KAPL12556-I
|
An attempt to execute the utility for setting HDLM driver option has failed.
|
- Action
Check the action recommended in the error message output before this message, and take action accordingly.
|
KAPL12557-I
|
The user stopped the utility for setting HDLM driver option.
|
- Details
Even if the message KAPL12555-I is output before this message, the contents set by the execution of the dlmsetopt utility will have no effect and the settings will return to the state before the execution.
- Action
If necessary, re-execute the dlmsetopt utility.
|
KAPL12558-I
|
Please restart the computer so that the option settings take effect.
|
- Action
Restart the computer.
|
KAPL12559-E
|
An invalid value was specified in the parameter. Option = aa...aa, Parameter = bb...bb
|
- Details
aa...aa: Option
bb...bb: Specified parameter(Maximum 10 characters. If there are more than 10 characters, only 10 characters will be output followed by ...)
- Action
Refer to DLMSETOPT_UTILITY_FOR_SETTING_HDLM_DRIVER_OPTIONS=GUID-2D0A9E93-105D-4255-AECD-CC67B3B20DD6=2=EN=.html, and then specifying the correct argument. Then, re-execute the dlmsetopt utility.
|
KAPL12560-E
|
An option is not specified.
|
- Action
Refer to DLMSETOPT_UTILITY_FOR_SETTING_HDLM_DRIVER_OPTIONS=GUID-2D0A9E93-105D-4255-AECD-CC67B3B20DD6=2=EN=.html, specify the correct argument, and then re-execute the dlmsetopt utility.
|
KAPL12561-E
|
An invalid option was specified. Option = aa...aa
|
- Details
aa...aa: Option
- Action
Refer to DLMSETOPT_UTILITY_FOR_SETTING_HDLM_DRIVER_OPTIONS=GUID-2D0A9E93-105D-4255-AECD-CC67B3B20DD6=2=EN=.html, specify the correct argument, and then re-execute the dlmsetopt utility.
|
KAPL12562-E
|
A necessary file or directory was not found. File or directory name = aa...aa
|
- Details
aa...aa: Referenced directory or file name
- Action
Make sure that the directory or file indicated in the message has not been renamed. If the directory or file has been renamed, change the name back to its original name, and then re-execute the utility for setting HDLM driver option (dlmsetopt).
|
KAPL12563-E
|
An attempt to create a directory has failed. Directory = aa...aa
|
- Details
aa...aa: Directory that an attempt was made to create
- Action
Make sure there is enough free disk capacity, and then re-execute the utility for setting HDLM driver option (dlmsetopt).
Delete any unnecessary files in the file system, and then re-execute the dlmsetopt utility.
|
KAPL12564-E
|
An attempt to back up a file has failed. File name = aa...aa
|
- Details
aa...aa: Backup file name
- Action
Make sure there is enough free disk capacity, and then re-execute the utility for setting HDLM driver option (dlmsetopt).
|
KAPL12565-E
|
Could not modify file. File name = aa...aa
|
- Details
aa...aa: Name of file to be updated
- Action
Make sure there is enough free disk capacity, and then re-execute the utility for setting HDLM driver option (dlmsetopt). If this message still appears, stop any unnecessary processes, and then re-execute the dlmsetopt utility.
|
KAPL12566-E
|
The utility for setting HDLM driver option was executed and ended abnormally last time.
|
- Action
Compare the contents of the /etc/modprobe.conf file and the /etc/opt/DynamicLinkManager/DLMSETOPT/modprobe.conf file. According to the result, perform the following procedures:
The /etc/opt/DynamicLinkManager/DLMSETOPT/modprobe.conf file was
copied for backup by HDLM before the utility for setting HDLM driver option
(dlmsetopt) is to be executed.
When the file contents match:
Delete the /etc/opt/DynamicLinkManager/DLMSETOPT/modprobe.conf file. Then, re-execute the dlmsetopt utility to make sure that an error does not occur.
When the file contents do not match:
Overwrite the /etc/modprobe.conf file with the /etc/opt/DynamicLinkManager/DLMSETOPT/modprobe.conf file, and then re-configure the content that was configured in the /etc/modprobe.conf file according to the user's environment. Then, delete the /etc/opt/DynamicLinkManager/DLMSETOPT/modprobe.conf file. Finally, re-execute the dlmsetopt utility to make sure that an error does not occur.
|
KAPL12567-E
|
The version of the kernel supported by the installed HDLM does not match the currently running kernel version.
|
- Details
The version of the kernel to which installed HDLM has adjusted and the kernel that is running now is not corresponding. There is a possibility of installing the package of the kernel after installing HDLM.
- Action
Install HDLM that adjusts to the kernel that is running now.
|
KAPL12568-E
|
The HDLM file is invalid. File name = aa...aa
|
- Details
A file necessary for processing HDLM cannot be found. Alternatively, the content of a file is invalid.
aa...aa: Name of file where error was detected.
- Action
Reinstall an HDLM.
|
KAPL12801-E
|
The version of the kernel supported by the installed HDLM does not match the currently running kernel version.
|
- Details
The version of the kernel to which installed HDLM has adjusted and the kernel that is running now is not corresponding. There is a possibility of installing the package of the kernel after installing HDLM.
- Action
Install HDLM that adjusts to the kernel that is running now.
|
KAPL12802-E
|
The HDLM file is invalid. File name = aa...aa
|
- Details
A file necessary for processing HDLM cannot be found. Alternatively, the content of a file is invalid.
aa...aa: Name of file where error was detected.
- Action
Reinstall an HDLM.
|
KAPL12803-E
|
The device management file could not be created. Restart the host before using HDLM.
|
- Details
The device management file could not be created. Restart the host before using HDLM.
- Action
After HDLM was installed by using the -update option, the host was not restarted. Restart the host before using HDLM.
|
|
KAPL12804-E
|
UUID information on the device was not able to be acquired. Device = aa...aa
|
- Details
-
UUID information on the device was not able to be
acquired.
aa...aa: The target device
- Action
-
Verify that the output device has UUID information. If UUID
information does not exist, set a UUID for the device.
|
|
KAPL12805-E
|
Modification of a symbolic link has failed. Symbolic link = aa...aa, Details = bb...bb
|
- Details
-
Modification of a symbolic link has failed.
aa...aa: Symbolic link that
could not be updated
bb...bb: Message output from
the OS
- Action
-
Check the message displayed in the detailed information, and
respond according to the action described in the message.
|
KAPL12851-E
|
The version of the kernel supported by the installed HDLM does not match the currently running kernel version.
|
- Details
The version of the kernel to which installed HDLM has adjusted and the kernel that is running now is not corresponding. There is a possibility of installing the package of the kernel after installing HDLM.
- Action
Install HDLM that adjusts to the kernel that is running now.
|
KAPL12852-E
|
The HDLM file is invalid. File name = aa...aa
|
- Details
A file necessary for processing HDLM cannot be found. Alternatively, the content of a file is invalid.
aa...aa: Name of file where error was detected.
- Action
Reinstall an HDLM.
|
KAPL12901-E
|
The version of the kernel supported by the installed HDLM does not match the currently running kernel version.
|
- Details
The version of the kernel to which installed HDLM has adjusted and the kernel that is running now is not corresponding. There is a possibility of installing the package of the kernel after installing HDLM.
- Action
Install HDLM that adjusts to the kernel that is running now.
|
KAPL12902-E
|
The HDLM file is invalid. File name = aa...aa
|
- Details
A file necessary for processing HDLM cannot be found. Alternatively, the content of a file is invalid.
aa...aa: Name of file where error was detected.
- Action
Reinstall an HDLM.
|
KAPL12903-I
|
The utility for creating an HDLM boot disk environment (dlmbootstart) will now start.
|
- Details
The utility for creating an HDLM boot disk environment (dlmbootstart) will now start.
- Action
None.
|
KAPL12904-I
|
Editing of the boot loader configuration file will now start.
|
- Details
The boot loader configuration file will now be edited.
- Action
None.
|
KAPL12905-I
|
The processing to configure the fstab file will now start.
|
- Details
The fstab file will now be configured.
- Action
None.
|
KAPL12906-I
|
Editing of the /etc/lvm/lvm.conf file will now start.
|
- Details
The /etc/lvm/lvm.conf file will now be edited.
- Action
None.
|
KAPL12907-I
|
The processing to configure the initial RAM disk image file will now start.
|
- Details
The initial RAM disk image file will now be configured.
- Action
None.
|
KAPL12908-I
|
The utility for creating an HDLM boot disk environment (dlmbootstart) finished.
|
- Details
The utility for creating an HDLM boot disk environment (dlmbootstart) finished.
- Action
None.
|
KAPL12909-I
|
Editing of the boot loader configuration file finished.
|
- Details
The boot loader configuration file was edited.
- Action
None.
|
KAPL12910-I
|
The processing to configure the fstab file finished.
|
- Details
The fstab file was configured.
- Action
None.
|
KAPL12911-I
|
Editing of the /etc/lvm/lvm.conf file finished.
|
- Details
The /etc/lvm/lvm.conf file was configured.
- Action
None.
|
KAPL12912-I
|
The processing to configure the initial RAM disk image file finished.
|
- Details
The initial RAM disk image file was configured.
- Action
None.
|
KAPL12913-E
|
An attempt to execute the utility for creating an HDLM boot disk environment (dlmbootstart) failed. Take the actions described in the message that was output just before this message, and then re-execute the dlmbootstart utility.
|
- Details
An attempt to execute the utility for creating an HDLM boot disk environment (dlmbootstart) failed.
- Action
Check the actions to take described in the message that was output just before this message.
|
KAPL12914-E
|
Editing of the boot loader configuration file failed. Take the actions described in the message that was output just before this message, and then re-execute the dlmbootstart utility.
|
- Details
Editing of the boot loader configuration file failed.
- Action
Check the actions to take described in the message that was output just before this message.
|
KAPL12915-E
|
The processing to configure the fstab file failed. Take the actions described in the message that was output just before this message, and then re-execute the dlmbootstart utility.
|
- Details
The processing to configure the fstab file failed.
- Action
Check the actions to take described in the message that was output just before this message.
|
KAPL12916-E
|
Editing of the /etc/lvm/lvm.conf file failed. Take the actions described in the message that was output just before this message, and then re-execute the dlmbootstart utility.
|
- Details
Editing of the /etc/lvm/lvm.conf file failed.
- Action
Check the actions to take described in the message that was output just before this message.
|
KAPL12917-E
|
The processing to configure the initial RAM disk image file failed. Take the actions described in the message that was output just before this message, and then re-execute the dlmbootstart utility.
|
- Details
The processing to configure the initial RAM disk image file failed.
- Action
Check the actions to take described in the message that was output just before this message.
|
KAPL12918-I
|
The utility for creating an HDLM boot disk environment (dlmbootstart) was terminated.
|
- Details
The utility for crating an HDLM boot disk environment (dlmbootstart) was terminated.
- Action
None.
|
KAPL12919-I
|
Editing of the boot loader configuration file was terminated.
|
- Details
Editing of the boot loader configuration file was terminated.
- Action
None.
|
KAPL12920-I
|
The processing to configure the fstab file was terminated.
|
- Details
The processing to configure the fstab file was terminated.
- Action
None.
|
KAPL12921-I
|
Editing of the /etc/lvm/lvm.conf file was terminated.
|
- Details
Editing of the /etc/lvm/lvm.conf file was terminated.
- Action
None.
|
KAPL12922-I
|
The processing to configure the initial RAM disk image file was terminated.
|
- Details
The initial RAM disk image file setting was terminated.
- Action
None.
|
KAPL12923-E
|
The utility for creating an HDLM boot disk environment (dlmbootstart) was executed with an invalid parameter. Parameter = aa...aa
Specify the correct parameter, and then try again.
|
- Details
aa...aa: The specified parameter (character string)
- Action
Specify the correct parameters, and then re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
KAPL12924-E
|
The processing to edit the boot loader configuration file was executed with an invalid parameter.
Parameter = aa...aa
Specify the correct parameter, and then execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
- Details
aa...aa: The specified parameter (character string)
- Action
Check the parameters of the target utility, and then execute the utility again.
|
KAPL12925-E
|
The processing to configure the fstab file was executed with an invalid parameter.
Parameter = aa...aa
Specify the correct parameter, and then execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
- Details
aa...aa: The specified parameter (character string)
- Action
Check the parameters of the target utility, and then execute the utility again.
|
KAPL12926-E
|
The processing to edit the /etc/lvm/lvm.conf file was executed with an invalid parameter.
Parameter = aa...aa
Specify the correct parameter, and then execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
- Details
aa...aa: The specified parameter (character string)
- Action
Check the parameters of the target utility, and then execute the utility again.
|
KAPL12927-E
|
The processing to create the initial RAM disk image file was executed with an invalid parameter.
Parameter = aa...aa
Specify the correct parameter, and then execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
- Details
aa...aa: The specified parameter (character string)
- Action
Check the parameters of the target utility, and then execute the utility again.
|
KAPL12928-W
|
Usage:
/opt/DynamicLinkManager/bin/dlmbootstart { -set hdlm [ -shutdown | -reboot ] | -set restore | -h }
|
- Action
Check for parameters, and then re-execute the dlmbootstart utility. Refer to dlmbootstart utility for creating an HDLM boot disk environment on page DLMBOOTSTART_UTILITY_FOR_CREATING_AN_HDLM_BOOT_DISK_ENVIRONMENT=GUID-1DDD7B91-963B-4A94-ADD0-05E9C351C6A9=2=EN=.html.
|
KAPL12933-E
|
The utility for creating an HDLM boot disk environment (dlmbootstart) is already being executed. Wait for the dlmbootstart utility to finish, and then execute the utility again.
|
- Details
An attempt to execute the utility for creating an HDLM boot disk environment (dlmbootstart) failed because two or more instances of the utility were executed simultaneously.
- Action
Wait for the utility for creating an HDLM boot disk environment (dlmbootstart) to finish, and then execute the utility again.
For details on the dlmbootstart utility, see page DLMBOOTSTART_UTILITY_FOR_CREATING_AN_HDLM_BOOT_DISK_ENVIRONMENT=GUID-1DDD7B91-963B-4A94-ADD0-05E9C351C6A9=2=EN=.html.
Delete the following files, and then execute the dlmbootstart utility:
/opt/DynamicLinkManager/bin/.dlmbootstart.lock
/opt/DynamicLinkManager/bin/.dlmbootsetup.lock
/opt/DynamicLinkManager/bin/.dlmlvmsetup.lock
|
KAPL12934-E
|
Editing of the boot loader configuration file is in progress. Wait for the dlmbootstart utility to finish, and then execute the utility again.
|
- Details
The boot loader configuration file is being edited.
- Action
Wait for the utility for creating an HDLM boot disk environment (dlmbootstart) to finish, and then execute the utility again.
For details on the dlmbootstart utility, see page DLMBOOTSTART_UTILITY_FOR_CREATING_AN_HDLM_BOOT_DISK_ENVIRONMENT=GUID-1DDD7B91-963B-4A94-ADD0-05E9C351C6A9=2=EN=.html.
|
KAPL12935-E
|
The processing to configure the fstab file is in progress. Wait for the dlmbootstart utility to finish, and then execute the utility again.
|
- Details
The fstab file is being set.
- Action
Wait for the utility for creating an HDLM boot disk environment to finish, and then execute the utility again.
Refer to dlmbootstart utility for creating an HDLM boot disk environment on page DLMBOOTSTART_UTILITY_FOR_CREATING_AN_HDLM_BOOT_DISK_ENVIRONMENT=GUID-1DDD7B91-963B-4A94-ADD0-05E9C351C6A9=2=EN=.html.
|
KAPL12936-E
|
Editing of the /etc/lvm/lvm.conf file is in progress. Wait for the dlmbootstart utility to finish, and then execute the utility again.
|
- Details
The /etc/lvm/lvm.conf file is being edited.
- Action
Wait for the utility for creating an HDLM boot disk environment to finish, and then execute the utility again.
Refer to dlmbootstart utility for creating an HDLM boot disk environment on page DLMBOOTSTART_UTILITY_FOR_CREATING_AN_HDLM_BOOT_DISK_ENVIRONMENT=GUID-1DDD7B91-963B-4A94-ADD0-05E9C351C6A9=2=EN=.html.
|
KAPL12937-E
|
The processing to configure the initial RAM disk image file is in progress. Wait for the dlmbootstart utility to finish, and then execute the utility again.
|
- Details
The initial RAM disk image file is being set.
- Action
Wait for the utility for creating an HDLM boot disk environment to finish, and then execute the utility again.
Refer to dlmbootstart utility for creating an HDLM boot disk environment on page DLMBOOTSTART_UTILITY_FOR_CREATING_AN_HDLM_BOOT_DISK_ENVIRONMENT=GUID-1DDD7B91-963B-4A94-ADD0-05E9C351C6A9=2=EN=.html.
|
KAPL12938-E
|
An error occurred in the internal processing of the utility for creating an HDLM boot disk environment (dlmbootstart). Details = aa...aa, bb...bb
Execute the DLMgetras utility, and then contact your HDLM vendor or the maintenance company if there is a maintenance contact for HDLM.
|
- Details
aa...aa: Return value (decimal number)
bb...bb: Maintenance information (number of lines where the error occurred) (decimal number)
- Action
Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM.
|
KAPL12939-E
|
An error occurred in the internal processing of editing the boot loader configuration file. Details = aa...aa, bb...bb
Execute the DLMgetras utility, and then contact your HDLM vendor or the maintenance company if there is a maintenance contact for HDLM.
|
- Details
aa...aa: Return value (decimal number)
bb...bb: Maintenance information (number of lines where the error occurred) (decimal number)
- Action
Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM.
|
KAPL12940-E
|
An error occurred in the internal processing of configuring the fstab file. Error Code = aa..aa[bb..bb] cc..cc
Execute the DLMgetras utility, and then contact your HDLM vendor or the maintenance company if there is a maintenance contact for HDLM.
|
- Details
aa...aa: Name of the function where the error occurred
bb...bb: Line number where the error occurred (decimal number)
cc...cc: Detailed information (character string)
- Action
The way to resolve the problem depends on errno in the detailed information.
12(ENOMEM)
Make sure there is sufficient memory.
2(ENOENT)
13(EACCES)
Re-install HDLM.
28(ENOSPC)
Make sure there is enough free disk capacity.
If errno is not displayed in the detailed information, or an errno different from the above is displayed, contact your HDLM vendor or the maintenance company if you have a maintenance contact for HDLM.
|
KAPL12941-E
|
An error occurred in the internal processing of editing the /etc/lvm/lvm.conf file Details = aa...aa, bb...bb
Execute the DLMgetras utility, and then contact your HDLM vendor or the maintenance company if there is a maintenance contact for HDLM.
|
- Details
aa...aa: Return value (decimal number)
bb...bb: Maintenance information (number of lines where the error occurred) (decimal number)
- Action
Contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM.
|
KAPL12942-E
|
An error occurred in the internal processing of creating the initial RAM disk image file.
Error Code = aa..aa[bb..bb] cc..cc
Execute the DLMgetras utility, and then contact your HDLM vendor or the maintenance company if there is a maintenance contact for HDLM.
|
- Details
aa...aa: Name of the function where the error occurred
bb...bb: Line number where the error occurred (decimal number)
cc...cc: Detailed information (character string)
- Action
The way to solve the problem depends on the detailed information of errno.
12(ENOMEM)
Make sure that there is sufficient memory.
2(ENOENT)
13(EACCES)
Re-install HDLM.
28(ENOSPC)
Make sure there is enough free disk capacity.
If errno is not displayed in the detailed information, or error that is not applicable for the above is displayed,
contact your HDLM vendor or the maintenance company if there is a maintenance contact of HDLM.
|
KAPL12943-E
|
A specified file or directory, required for processing of the utility for creating an HDLM boot disk environment (dlmbootstart), does not exist. File or directory name = aa...aa
Check whether the specified file or directory exists by comparing with the OS in its initial state or in the state just after HDLM is installed.
|
- Details
aa...aa: Name of the non-existent file or directory (character string)
- Action
Check whether the specified file or directory exists by comparing with the OS in its initial state or in the state just after HDLM is installed. Then, execute the dlmbootstart utility.
For details on the dlmbootstart utility, see page DLMBOOTSTART_UTILITY_FOR_CREATING_AN_HDLM_BOOT_DISK_ENVIRONMENT=GUID-1DDD7B91-963B-4A94-ADD0-05E9C351C6A9=2=EN=.html.
|
KAPL12944-I
|
The restoration processing of the utility for creating an HDLM boot disk environment (dlmbootstart) will now start.
|
- Details
The restoration processing of the utility for creating an HDLM boot disk environment (dlmbootstart) will now start.
- Action
None.
|
KAPL12945-E
|
The log information could not be output to a log file during execution of the utility for creating an HDLM boot disk environment (dlmbootstart). Make sure that the disk has enough unused capacity and that the user has write permission for this directory.
|
- Details
The log information could not be output to the error log file /var/opt/DynamicLinkManager/log/dlmbootstart*.log.
- Action
Make sure that the disk has enough unused capacity and that the user has write permission for the log file directory.
|
KAPL12946-I
|
After one minute, the system will stop or restart.
|
- Details
After one minute, the system will stop or restart.
- Action
None.
|
KAPL12947-I
|
The processing to edit the boot loader configuration file was skipped.
|
- Details
The processing to edit the boot loader configuration file was skipped.
- Action
None.
|
KAPL12948-E
|
A specified file or directory, required for the processing to edit the boot loader configuration file, does not exist. File or directory name = aa...aa
Check whether the specified file or directory exists by comparing with the OS in its initial state or in the state just after HDLM is installed.
|
- Details
aa...aa: Name of the non-existent file or directory (character string)
- Action
Check whether the specified file or directory exists by comparing with the OS in its initial state or in the state just after HDLM is installed. Then, execute the dlmbootstart utility.
For details on the dlmbootstart utility, see page DLMBOOTSTART_UTILITY_FOR_CREATING_AN_HDLM_BOOT_DISK_ENVIRONMENT=GUID-1DDD7B91-963B-4A94-ADD0-05E9C351C6A9=2=EN=.html.
|
KAPL12949-I
|
This OS is not supported.
|
- Details
This OS is not supported.
- Action
None.
|
KAPL12950-E
|
The log information could not be output to a log file during editing of the boot loader configuration file. Make sure that the disk has enough unused capacity and that the user has write permission for this directory.
|
- Details
The log information could not be output to the error log file /var/opt/DynamicLinkManager/log/dlmbootstart*.log.
- Action
Make sure that the disk has enough unused capacity and that the user has write permission for the log file directory.
|
KAPL12951-E
|
Both of the following RPM packages exist: grub and grub2. Leave the package that was installed in the OS in its initial state, and remove the other package.
|
- Details
Both of the following RPM packages exist: grub and grub2.
- Action
Make sure the environment is one where only one of the grub or grub2 RPM packages is installed. Then, re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
KAPL12952-E
|
Neither of the following RPM packages exist: grub and grub2. Re-install the package that was installed in the OS in its initial state.
|
- Details
Neither of the following RPM packages exists: grub and grub2.
- Action
Make sure the environment is one where only one of the grub or grub2 RPM packages is installed. Then, re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
KAPL12953-I
|
The restoration processing of the utility for creating an HDLM boot disk environment (dlmbootstart) finished.
|
- Details
The restoration processing of the utility for creating an HDLM boot disk environment (dlmbootstart) finished.
- Action
None.
|
KAPL12954-I
|
The processing to edit the /etc/lvm/lvm.conf file was skipped.
|
- Details
The editing processing of /etc/lvm/lvm.conf file was skipped.
- Action
None.
|
KAPL12955-E
|
A specified file or directory does not exist in the processing to edit the file lvm.conf. File or directory name = aa...aa
Check whether the specified file or directory exists by comparing whether it exists in the OS in its initial state or in the state just after HDLM is installed.
|
- Details
aa...aa: Name of the non-existent file or directory
- Action
Check whether the specified file or directory exists by comparing with the OS in its initial state or in the state just after HDLM is installed. Then, execute the dlmbootstart utility. For details on the dlmbootstart utility, see page DLMBOOTSTART_UTILITY_FOR_CREATING_AN_HDLM_BOOT_DISK_ENVIRONMENT=GUID-1DDD7B91-963B-4A94-ADD0-05E9C351C6A9=2=EN=.html.
|
KAPL12956-W
|
The grub.conf file or the menu.lst file contains multiple copy-source entries. Change the default value to the entry for the currently running OS, and then re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
- Details
The grub.conf file or the menu.lst file contains multiple copy-source entries.
- Action
Change the default value to the entry for the currently running OS, and then re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
KAPL12957-E
|
The log information could not be output to a log file during editing of the /etc/lvm/lvm.conf file. Make sure that the disk has enough unused capacity and that the user has write permission for this directory.
|
- Details
The log information could not be output to the error log file /var/opt/DynamicLinkManager/log/dlmbootstart*.log.
- Action
Make sure that the disk has enough unused capacity and that the user has write permission for the log file directory.
|
KAPL12958-W
|
The grub.conf file or the menu.lst file does not contain a copy-source entry. Compare the grub.conf file or the menu.lst file in the OS in its initial state, and make sure there is an entry of the currently running OS.
|
- Details
The grub.conf file or the menu.lst file does not contain a copy-source entry.
- Action
Compare the grub.conf file or the menu.lst file in the OS in its initial state, and check whether there is an entry for the currently running OS.
|
KAPL12959-E
|
The lvm.conf file contains multiple definitions of the following item. Item name = aa...aa
Make sure the item is defined only once, and then re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
- Details
aa...aa: Name of item defined multiple times (character string)
- Action
Make sure the item is defined only once, and then re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
For details on the dlmbootstart utility, see page DLMBOOTSTART_UTILITY_FOR_CREATING_AN_HDLM_BOOT_DISK_ENVIRONMENT=GUID-1DDD7B91-963B-4A94-ADD0-05E9C351C6A9=2=EN=.html.
|
KAPL12960-E
|
The lvm.conf file does not contain the following item. Item name = aa...aa
Make sure this item exists in the lvm.conf file, and then re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
- Details
aa...aa: Name of the non-existent item (character string)
- Action
Make sure this item exists in the lvm.conf file, and then re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
KAPL12961-E
|
The environment is not a SAN environment.Make sure the environment is one where the system boots from a system disk in a storage area network. Alternatively, make sure the system disk (/) is not excluded from the HDLM management target by executing the HDLM-configuration definition utility (dlmcfgmgr) with the -o parameter specified.
|
- Details
The environment is not a SAN environment.
- Action
Make sure the environment is one where the system boots from a system disk in a storage area network. Alternatively, make sure the system disk (/) is not excluded from the HDLM management target by executing the HDLM-configuration definition utility (dlmcfgmgr) with the -o parameter specified.
|
KAPL12962-W
|
The utility for creating an HDLM boot disk environment (dlmbootstart) ended abnormally last time. The initial RAM disk image file or the hdlm.conf file might be invalid.
|
- Details
The system determined that the utility for creating an HDLM boot disk environment (dlmbootstart) did not end normally because a temporary file for the processing to configure the initial RAM disk image file remains from the last time.
- Action
Enter y in response to the KAPL12963-I message to continue the processing.
|
KAPL12963-I
|
The temporary file that remains from when the utility ended abnormally last time will be deleted, and processing to configure the initial RAM disk image file will continue based on the current system information. Do you want to continue? [y/n]:
|
- Action
You can select whether to continue the processing to configure the initial RAM disk image file or to terminate the processing.
If you enter y, the temporary file (for the processing to configure the initial RAM disk image file) that remains from when the utility ended abnormally last time will be deleted, and the processing will continue.
After this, if any of the following problems occur, execute the utility for collecting HDLM error information (DLMgetras) to acquire the error information and the files in the /tmp/dlminitramsetup_crash directory, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM.
The HDLM device is not being used as a boot disk in this environment.
An error message appears, and the OS stops.
An error message appears when the OS starts.
If you enter n, processing to configure the initial RAM disk image file will stop.
|
KAPL12964-I
|
The creation of the initial RAM disk image file for HDLM will now start.
|
- Action
None.
|
KAPL12965-I
|
The creation of the initial RAM disk image file for HDLM finished.
|
- Action
None.
|
KAPL12966-E
|
The creation of the initial RAM disk image file for HDLM failed.
|
- Action
Check the following.
Check whether there is sufficient unused disk capacity.
If the unused capacity is insufficient, allocate the required amount of capacity.
Check the read and write permissions for the following directories:
Check whether there is sufficient unused memory capacity.
If the unused capacity is insufficient, allocate the required amount of capacity.
|
KAPL12967-I
|
The restoration of the initial RAM disk image file will now start.
|
- Action
None.
|
KAPL12968-I
|
The restoration of the initial RAM disk image file finished.
|
- Action
None.
|
KAPL12969-E
|
The restoration of the initial RAM disk image file failed.
|
- Action
Check the following.
Check whether there is sufficient unused disk capacity.
If the unused capacity is insufficient, allocate the required amount of capacity.
Check the read and write permissions for the following directories:
Check whether there is sufficient unused memory capacity.
If the unused capacity is insufficient, allocate the required amount of capacity.
|
KAPL12970-I
|
The initial RAM disk image file was not restored because a backup of the file does not exist.
|
- Action
None.
|
KAPL12971-I
|
The creation of the fstab file for HDLM will now start.
|
- Action
None.
|
KAPL12972-I
|
The creation of the fstab file for HDLM finished.
|
- Action
None.
|
KAPL12973-E
|
The creation of the fstab file for HDLM failed.
|
- Action
Check the following.
Check whether there is sufficient unused disk capacity.
If the unused capacity is insufficient, allocate the required amount of capacity.
Check the read and write permissions for the following directories:
Check whether there is sufficient unused memory capacity.
If the unused capacity is insufficient, allocate the required amount of capacity.
|
KAPL12974-I
|
The fstab file was not updated because the file is already configured for HDLM, or because there are no devices managed by HDLM.
|
- Action
None.
|
KAPL12975-I
|
The restoration of the fstab file will now start.
|
- Action
None.
|
KAPL12976-I
|
The restoration of the fstab file finished.
|
- Action
None.
|
KAPL12977-E
|
The restoration of the fstab file failed.
|
- Action
Check the following.
Check whether there is sufficient unused disk capacity.
If the unused capacity is insufficient, allocate the required amount of capacity.
Check the read and write permissions for the following directories:
Check whether there is sufficient unused memory capacity.
If the unused capacity is insufficient, allocate the required amount of capacity.
|
KAPL12978-I
|
The fstab file was not restored because a backup of the file does not exist.
|
- Action
None.
|
KAPL12979-W
|
The utility for creating an HDLM boot disk environment (dlmbootstart) ended abnormally last time. The fstab file might be invalid.
|
- Details
The system determined that the utility for creating an HDLM boot disk environment (dlmbootstart) did not end normally because a temporary file for the processing to configure the fstab file remains from the last time.
- Action
Enter y in response to the KAPL12980-I message to continue the processing.
|
KAPL12980-I
|
The temporary file that remains from when the utility ended abnormally last time will be deleted, and processing to configure the fstab file will continue based on the current system information. Do you want to continue? [y/n]:
|
- Action
You can select whether to continue the processing to configure the fstab file or to terminate the processing.
If you enter y, the temporary file (for the processing to configure the fstab file) that remains from when the utility ended abnormally last time will be deleted, and the processing will continue.
After this, if any of the following problems occur, execute the utility for collecting HDLM error information (DLMgetras) to acquire the error information and the files in the /tmp/dlminitramsetup_crash directory, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM.
The HDLM device is not being used as a boot disk in this environment.
An error message appears, and the OS stops.
An error message appears when the OS starts.
If you enter n, processing to configure the fstab file will stop.
|
KAPL12981-E
|
HDLM device not configured. Execute the utility for HDLM start (dlmstart), configure an HDLM device, and then re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
- Details
HDLM device not configured.
- Action
Execute the utility for HDLM start (dlmstart), configure an HDLM device, and then re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
KAPL12982-E
|
The SCSI device is being used as a swap device. Disable the swap, and then re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|
- Details
The SCSI device is being used as a swap device.
- Action
Disable the swap for the SCSI device that is an HDLM-management target by using the swapoff command, and then re-execute the utility for creating an HDLM boot disk environment (dlmbootstart).
|