| 2500-001 | Cannot open or access file file_name. |
Explanation: The file does not exist or does not have the appropriate permissions.
User Response: Verify that the file exists with the appropriate permissions.
| 2500-002 | Error opening HSD HSD_name. |
Explanation: The data striping device (HSD) cannot be opened or it does not exist.
User Response: Use lshsd to verify that the file exists.
| 2500-003 | The ioctl_string ioctl() call failed. |
Explanation: The ioctl call failed for the specified ioctl.
User Response: See the errno to determine the reason for failure.
| 2500-004 | The call to odm_initialize() failed odmerrno_value |
Explanation: The ioctl call to start the odm failed. The odmerrno variable has been set to indicate the error.
User Response: Use the odmerrno value to determine the error.
| 2500-005 | The call to genmajor() failed conferrno_value. |
Explanation: The call to genmajor() to retrieve the data striping device (HSD) major number failed. The conferrno variable has been set to indicate the error.
User Response: Use the conferrno and the errno values to determine the reason for failure.
| 2500-006 | Error Unloading the HSD Kernel Extension. |
Explanation: The loadext() call failed.
User Response: Check the errno to determine the reason for failure.
| 2500-007 | The HSD device driver is not loaded. |
Explanation: The HSD driver should already be loaded at this point.
User Response: Configure the HSD.
| 2500-008 | The hsd_command_name command passed to the HSD Device Driver failed. |
Explanation: The HSD driver encountered an error condition while executing the specified command.
User Response: See the errno to determine the reason for failure.
| 2500-009 | With the -a option, additional parameters are not allowed. |
Explanation: The user specified the -a option. This means all HSDs. Additional parameters are not allowed on the command line.
User Response: Reissue the command with no additional parameters.
| 2500-010 | File file_name not found. |
Explanation: The specified file does not exist.
User Response: The HSD needs to be placed in the SDR. This file will then be created automatically the next time cfghsd is called.
| 2500-011 | Definition of HSD hsd_name not found in the file hsd_table_pathname. |
Explanation: The specified HSD could not be found in the HSD_Table file.
User Response: Check that the data in the HSD is correct. Modify the SDR as necessary.
| 2500-012 | Cannot allocate memory for item. |
Explanation: The malloc call to allocate temporary storage for the item failed.
User Response: This is system problem.
| 2500-013 | HSD_name hsdvsd_name cannot be the same as VSD name. |
Explanation: If the HSD and the IBM Virtual Shared Disk both tried to create the same special files in /dev, the HSD /dev files would overlay the IBM Virtual Shared Disk /dev files, rendering both unusable.
User Response: Make up a new HSD name. The recommended naming convention is hsd.logical_name. Retry the operation.
| 2500-014 | You have specified a HSD name, HSD_name, that does not exist. |
Explanation: The method invoked the command for a HSD_name that does not have an entry in the SDR.
User Response: No action required. You do not have a HSD with this name.
| 2500-017 | method_command failed on HSD_name |
Explanation: The method invoked the command for HSD_name, and the command failed for that HSD.
User Response: See the previous error message displayed from the command for details. This message identifies the HSD_name that the previous error message didn't.
| 2500-021 | The repository cannot be accessed. Return code was return code. |
Explanation: The routine could not access the System Data Repository. The routine halted.
User Response: Refer to the chapter on diagnosing system monitor problems in PSSP: Diagnosis Guide for more information on diagnosing system monitor problems.
| 2500-022 | You have specified an invalid number of arguments. |
Explanation: An invalid command format was issued. The routine halted.
User Response: Reenter the command with the correct format.
| 2500-023 | You have specified an invalid flag. |
Explanation: A flag passed to the routine was invalid.
User Response: Reenter the command with the correct flag.
| 2500-024 | Issuing the command SDR_command gave a return code of return_code. |
Explanation: The routine passed a command to the System Data Repository which gave a nonzero return code.
User Response: Refer to the chapter on diagnosing system monitor problems in PSSP: Diagnosis Guide .
| 2500-025 | Virtual Shared Disk vsd_name is not found or configured. |
Explanation: The IBM Virtual Shared Disk vsd_name is not defined or configured.
User Response: Check to see if the IBM Virtual Shared Disk is defined and configured.
| 2500-026 | Failed to configure Hashed Shared Disk hsd_name. |
Explanation: The program failed to configure a HSD.
User Response: Check to see if all underlying IBM Virtual Shared Disks are defined and configured.
| 2500-031 | Error unlinking device_name. |
Explanation: The HSD special file already exists with a different device number from the specified device number.
User Response: Use rm to remove device_name from /dev.
| 2500-032 | Error loading the HSD kernel extension. |
Explanation: The loadext() call failed.
User Response: See the errno to determine the reason for failure.
| 2500-033 | Error Configuring the HSD Device. |
Explanation: The sysconfig() call failed.
User Response: See the errno to determine the reason for failure.
| 2500-034 | Device already exists. |
Explanation: The sysconfig() call failed and errno is EALREADY. The device is already configured.
User Response: Do not attempt to configure a device that is already configured.
| 2500-035 | name is too long. Length must be less than or equal to 31 characters |
Explanation: The name passed is unacceptable. The length of the name must be less than or equal to 31 characters.
User Response: Correct the name's length and reenter the command.
| 2500-036 | Special Device File file_name already exists, and does not have the proper HSD major number of major_number. |
Explanation: The file the HSD is trying to create already exists for a non-HSD.
User Response: Change the name of the HSD that conflicts with the existing device or remove the existing device file and try the operation again.
| 2500-037 | Can't create Special Device File file_name. |
Explanation: The HSD special device file create operation (mknod) failed. The reason for the mknod failure is also printed.
User Response: Refer to the mknod failure message to correct the problem.
| 2500-050 | Invalid Parallelism Value, parallelism value. |
Explanation: An invalid parallelism value was passed in. Valid values are:
User Response: Retry the command with a valid parallelism value
| 2500-060 | Invalid HSD command command. |
Explanation: The command passed to dohsd2 was invalid.
User Response: Use the valid command ucfg.
| 2500-070 | The -s and -l flags are not compatible. |
Explanation: The -s and the -l flags cannot be used together.
User Response: Reissue the command with only one of these flags.
| 2500-071 | Cannot allocate memory for HSD info. The count of HSDs is hsd_count. |
Explanation: The malloc call to allocate temporary storage for the HSD information failed.
User Response: Try again specifying the HSD you are interested in.
| 2500-082 | The stripe_size must be a number greater than or equal to 4096 and less than or equal to 128K. |
Explanation: A unacceptable value was entered for the stripe size.
User Response: Reenter the command with the correct value.
| 2500-083 | HSD_name HSD_name is already in use. |
Explanation: The name specified already defines a HSD in the SDR.
User Response: Use the undefhsd command to delete the entry in the SDR and reenter the undefhsd command. Or pick another HSD name.
| 2500-084 | VSD_name VSD_name is already used in other HSD. |
Explanation: The VSD_name specified has been defined in another HSD.
User Response: Select another IBM Virtual Shared Disk which is not used by any HSD.
| 2500-085 | The HSD_name, HSD_name cannot be the same as an VSD_name. |
Explanation: The HSD and the IBM Virtual Shared Disk both create special device files in /dev using the HSD and the IBM Virtual Shared Disk names respectively. Therefore, these names cannot be the same.
User Response: Make up a new name for the HSD. The suggested naming convention is hsd.logical_name.
| 2500-086 | name too long. Length must be less than or equal to 31 characters. |
Explanation: The name passed was unacceptable. The length of the name must be less than or equal to 31 characters.
User Response: Correct the name's length and reenter the command.
| 2500-087 | The option must be either protect_lvcb or not_protect_lvcb. |
Explanation: You must select one option; protect_lvcb or not_protect_lvcb.
User Response: Select protect_lvcb if you wish to protect the logical volume control block. If you do not wish to protect it, select not_protect_lvcb.
| 2500-089 | Entry already in the SDR. |
Explanation: The information specified for this command has already been placed in the SDR.
User Response: You do not need to reenter the information; it is already in the SDR.
| 2500-090 | You have specified an VSD name, VSD_name that does not exist. |
Explanation: The name specified does not have an entry in the SDR.
User Response: Use the vsdatalst to get a list of defined IBM Virtual Shared Disks.
| 2500-091 | stripe_size stripe_size is not multiple of 4K. |
Explanation: The value of the stripe size must be a multiple of 4K.
User Response: Rerun the command using a stripe size that is a multiple of 4K.
| 2500-092 | stripe_size must be between 4K and 1GB. |
Explanation: The value of the stripe size must be between 4K and 1GB.
User Response: Rerun the command using a stripe size between 4K and 1GB.
| 2500-093 | Failed to generate hsd minor number minor_number for hsd hsd_name. |
Explanation: If a new minor number is generated for a given HSD, and the return code from the SDR is not zero, an error occurs.
User Response: Check to see if the minor_number is a valid integer. If the minor_number is a valid integer, the problem is in the SDR.
Use /usr/lpp/ssp/bin/SDRGetObjects -q hsd_minor_number to verify the minor number in the SDR. If the minor_number is not a valid integer, the problem is in defhsd. Use hsdatlst to verify the minor number in defined HSDs.
| 2500-094 | Bad system class hsd_minor_number in SDR. |
Explanation: If a new minor number is generated for a given HSD, and the system class hsd_minor_number is empty after HSDs were defined, an error occurs.
User Response: Check the SDR database. Use /usr/lpp/ssp/bin/SDRGetObjects -q hsd_minor_number to verify the minor number in the SDR.
| 2500-095 | All the VSDs in the HSD must be of the same size. |
Explanation: All the IBM Virtual Shared Disks within an HSD must be the same size. All the IBM Virtual Shared Disks specified do not have the same size.
User Response: Check the SDR database. You may use the /usr/lpp/ssp/bin/SDRGetObjects -q VSD_Table VSD_name size_in_MB command to verify IBM Virtual Shared Disk sizes in the SDR.
| 2500-100 | The HSD character special device file character_device_name is not found. Have you run cfghsd hsd_name? |
Explanation: The /dev/r<hsdname> device file does not exist.
User Response: Run cfghsd to configure the device.
| 2500-101 | The file /unix was not found at device_ driver_pathname. |
Explanation: The /unix file was not found.
User Response: Use find to locate the boot image.
| 2500-102 | Step 1: FAILURE! The write of hsdd to hsd_name failed. |
Explanation: The write of the /unix to the specified HSD failed.
User Response: Check that the HSD exists and has been properly installed and configured.
| 2500-103 | Error: records in = records_in records out = records_out. |
Explanation: The dd command failed.
User Response: Check that the HSD has been properly installed and configured.
| 2500-104 | Error: remainder in = remainder_in remainder out = remainder_out. |
Explanation: The dd command failed.
User Response: Check that the HSD has been properly installed and configured.
| 2500-105 | Step 2: FAILURE! Bad rc (return_code) from dd of HSD to temporary file. |
Explanation: The read back of the HSD driver from the HSD failed.
User Response: Check the man page for the dd to determine the error.
| 2500-106 | Step 3: FAILURE! Bad rc (return_code) from dd of THSDD to temporary file. |
Explanation: The read of the /unix failed.
User Response: Check the man page for the dd to determine the error.
| 2500-107 | Step 4: FAILURE! Bad rc (return_code) from diff of temporary files. |
Explanation: The diff between what was read back from the HSD and the HSD driver failed.
User Response: Check the man page for diff to determine the error.
| 2500-108 | hsd_name is not an active hsd. Have you run cfghsd? |
Explanation: The parameter to hsdvts must be a HSD in the active state.
User Response: Make sure you have defined your HSD; run cfgvsd and startvsd; and run lshsd -l to see that your HSD is in the active state.
| 2500-116 | Check HSD_table_name table in the SDR, cannot find the table. |
Explanation: Some fields in the table are incorrect.
User Response: Run SMIT to set HSD information.
| 2500-117 | Check HSD_table_name table in the SDR, it is an empty table. |
Explanation: Some fields in the HSD table are incorrect.
User Response: Run SMIT to set HSD information.
| 2500-118 | Check HSD_table_name table in the SDR, undefined field is found. |
Explanation: Some fields in the HSD table are incorrect.
User Response: Run SMIT to set HSD information.
| 2500-119 | Failed to create new hsd files, default will be current /usr/lpp/csd/hsdfiles |
Explanation: At least one of the new HSD tables is incorrect.
User Response: Run SMIT to set HSD information.
| 2500-120 | Lock file (file_name) held too long; I am taking it. You may want to investigate. |
Explanation: hsdreadSDR uses a lock file which is a directory. hsdreadSDR waits about 7 seconds for the lock, then generates this message and continues running. If you see this message after the first cfghsd following a reboot, it probably means that the system crashed in the middle of a previous cfghsd, leaving behind a lock file. If this is the case, you can ignore the message.
If the message is generated in circumstances other than the first cfghsd following a reboot, it may be that another process is running a cfghsd and that process is hung. Insure that /usr/lpp/hsd/hsdfiles is a writable directory on a writable file system.
User Response: If this is not the first cfghsd after a reboot, check to see if another process is running cfghsd and if that process is hung.
| 2500-121 | Unable to find and create hsd_flat_file_directory_name. |
Explanation: The file was not found and the mkdir command to create it failed.
User Response: Investigate the mkdir failure and fix the problem. If the parent directory is not writable on this node, go to a node where you can write to the directory and make this file a symbolic link to a file system that is writable from the original node.
| 2500-123 | HSD hsd_name is configured on node host and cannot be undefined. |
Explanation: A HSD cannot be undefined if it is configured on any node.
User Response: Use the ucfghsd command for the hsd_name on the host to unconfigure the HSD, then enter the undefhsd again.
| 2500-124 | Deletion of hsd hsd_name from the HSD_Table in the SDR failed with a return code of return_code. hsd_name and minor number minor_number are not undefined. |
Explanation: The SDRDeleteObjects command failed when trying to undefine the HSD by deleting it from the SDR HSD_Table class. The minor_number was not deleted from the SDR HSD_Minor_Number class.
User Response: To determine how to fix the problem, see the preceding message from the SDRDeleteObjects, and then enter the undefhsd command again.
| 2500-125 | Some IBM Hashed Shared Disk Devices already exist before operation. Please use lshsd command to check the states. |
Explanation: In order to run the cfghsd operation on the HSD this HSD must not be configured.
User Response: Use the lshsd command to check to see if the HSD has been configured.
| 2500-126 | IBM Hashed Shared Disk Device is not configured. |
Explanation: In order to run the ucfghsd operation on the HSD it must be configured first.
User Response: Use the cfghsd command to configure the HSD, and try the failing command again.
| 2500-127 | IBM Hashed Shared Disk Device device name is not defined. |
Explanation: The IBM Hashed Shared Disk has not been defined.
User Response: Reissue the command with a valid IBM Hashed Shared Disk name.
| 2500-501 | uiomove failed. |
Explanation: The uiomove system call failed.
User Response: Record the above information and contact the IBM Support Center.
| 2500-502 | out of memory. |
Explanation: Allocation of pinned memory in the kernel has failed.
User Response: Record the above information and contact the IBM Support Center.
| 2500-503 | devswadd failed. |
Explanation: An attempt to add vsdd functions to the device switch table failed.
User Response: Record the above information and contact the IBM Support Center.
| 2500-504 | pincode failed. |
Explanation: An attempt to put hsdd driver code into pinned memory failed.
User Response: Record the above information and contact the IBM Support Center.
| 2500-505 | devswdel failed. |
Explanation: An attempt to delete vsdd entries from the device switch table failed.
User Response: Record the above information and contact the IBM Support Center.
| 2500-506 | xmalloc error. |
Explanation: An attempt to allocate pinned memory in the kernel failed.
User Response: Record the above information and contact the IBM Support Center.
| 2500-507 | device (device major number, device minor number) already configured. |
Explanation: This device has already been configured.
User Response: None.
| 2500-508 | device (device major number, device minor number) not configured. |
Explanation: An attempt was made to unconfigure a device that was not configured.
User Response: None.
| 2500-509 | device (device major number, device minor number) not configured. |
Explanation: An attempt was made to unconfigure a device that was not configured.
User Response: None.
| 2500-510 | failed due to lock mismatch. |
Explanation: A locking problem was encountered.
User Response: Record the above information and contact the IBM Support Center.
| 2500-511 | failed due to number of opens mismatch. |
Explanation: There is an error in the open counter for this hsd.
User Response: Record the above information and contact the IBM Support Center.
| 2500-512 | failed to remove entry points. |
Explanation: The devswdel() system call failed while trying to unconfigure the Hashed Shared Disk device driver.
User Response: Record the above information and contact the IBM Support Center.
| 2500-513 | unpincode failed. |
Explanation: The unpincode() system call failed while trying to unconfiure the Hashed Shared Disk device driver.
User Response: Record the above information and contact the IBM Support Center.
| 2500-514 | check hsd_inited device (device major number, device minor number) NOT configured. |
Explanation: The Hashed Shared Disk device driver is not initialized.
User Response: Record the above information and contact the IBM Support Center.
| 2500-515 | check find_hsd device (device major number, device minor number) NOT configured. |
Explanation: This device has not been configured.
User Response: Configure the hsd and retry the operation.
| 2500-516 | check hsd_stat device (device major number, device minor number) is not configured. |
Explanation: This device has not been configured.
User Response: Configure the hsd and retry the operation.
| 2500-517 | check hsd_inited device (device major number, device minor number) NOT configured/opened. |
Explanation: The Hashed Shared Disk device driver is not initialized.
User Response: Record the above information and contact the IBM Support Center.
| 2500-518 | check find_hsd device (device major number, device minor number) NOT configured/opened. |
Explanation: This device has not been configured.
User Response: Record the above information and contact the IBM Support Center.
| 2500-519 | get hsd_gen_info failed. |
Explanation: A failure occurred copying data to user space.
User Response: Record the above information and contact the IBM Support Center.
| 2500-520 | vlevel copyin failed. |
Explanation: A failure occurred copying data to the kernel.
User Response: Record the above information and contact the IBM Support Center.
| 2500-521 | parallelism copyin failed. |
Explanation: A failure occurred copying data to the kernel.
User Response: Record the above information and contact the IBM Support Center.
| 2500-522 | parallelism value invalid. |
Explanation: The value specified for the hsd parallelism is invalid.
User Response: Specify a value between 1 and 9.
| 2500-523 | GIOCGET device (device major number, device minor number) NOT configured. |
Explanation: This device has not been configured.
User Response: Configure the device and retry the operation.
| 2500-524 | GIOCGET copyout failed. |
Explanation: A failure occurred copying data to user space.
User Response: Record the above information and contact the IBM Support Center.
| 2500-525 | GIOCGETL copyin failed. |
Explanation: A failure occurred copying data to the kernel.
User Response: Record the above information and contact the IBM Support Center.
| 2500-526 | GIOCGETL copyout failed. |
Explanation: A failure occurred copying data to user space.
User Response: Record the above information and contact the IBM Support Center.
| 2500-527 | GIOCGETL copyout vsd_data_len failed. |
Explanation: A failure occurred copying data to user space.
User Response: Record the above information and contact the IBM Support Center.
| 2500-528 | GIOCGETL copyout hsd_info_list failed. |
Explanation: A failure occurred copying HSD_INFO_LIST to user space.
User Response: Record the above information and contact the IBM Support Center.
| 2500-529 | GIOCGET device (device major number, device minor number) NOT configured. |
Explanation: This device has not been configured.
User Response: Configure the device and retry the operation.
| 2500-530 | bad ioctl request 0x the passed in ioctl op code. |
Explanation: An invalid ioctl request was issued.
User Response: Retry the operation with a valid request.
| 2500-531 | device (device major number, device minor number) NOT configured. |
Explanation: This device has not been configured.
User Response: Configure the device and retry the operation.
| 2500-532 | uphysio failed on hsd with minor number hsd device minor number. |
Explanation: The uphysio() system call failed.
User Response: Record the above information and contact the IBM Support Center.
| 2500-533 | device (device major number, device minor number) NOT configured. |
Explanation: This device has not been configured.
User Response: Configure the device and retry the operation.
| 2500-534 | uphysio failed on hsd with minor number hsd device minor number. |
Explanation: The uphysio() system call failed.
User Response: Record the above information and contact the IBM Support Center.
| 2500-535 | cant open device (device major number, device minor number). |
Explanation: An open of the device failed.
User Response: Check the state of the device.
| 2500-536 | cannot close device with minor number (hsd device minor number). |
Explanation: A close of the device failed.
User Response: Check the state of the device.