[ Previous |
Next |
Contents |
Glossary |
Home |
Search ]
AIX Version 4.3 Messages Guide and Reference
Error Messages for Component ID 0514
0514-018 The values specified for the
following attributes are not valid
Possible Causes
- From the command line, you specified an
attribute that is out of the range of legal values.
- The Object Data Management (ODM) database
is damaged.
Procedures for Recovery
- Check the attributes in your command
to be sure they are in legal range.
- Run the lsattr
-R command to display the range of legal attribute values for that
specific device, then run your command with the correct attributes.
- Check to see if your ODM database is
damaged, then try replacing the PdAt file.
- Copy the PdAt file from another
system that has the same release level as your system, either through the
network by running the ftp
command or through a diskette by using the backup
and restore
commands.
- Restore the file making sure that it preserves
the permission code, the ownership, and the location of your previous file.
- Reenter your command.
0514-022 The specified connection is
not valid
Possible Causes
Procedures for Recovery
- Using SMIT, supply a valid connection location.
- Return to the SMIT screen where the error
occurred.
- Locate the screen containing the PORT number
field. You may need to select Cancel to page back through the screens.
- Position the cursor in the PORT number
field of this screen and select List. A list of valid connection
locations is displayed.
- Select the desired connection location
from the list.
- Select Do to insert the proper
value into the PORT number field.
- Locate a valid connection location, then
use it with the mkdev command.
- Enter the lsconn
-p command to list the valid connection locations.
- Select a connection location from the
list.
- Reenter the mkdev
command using the new connection location.
0514-031 A device is already configured
at the specified location
Possible Causes
- You attempted to add a device at a location
that is already occupied by a different device.
Procedures for Recovery
- Determine which device occupies the
location, and either remove it or find a new location for the new device.
- Select the System Management Interface
Tool (SMIT) Devices-> List Devices-> List All Defined Devicesmenu option. SMIT displays the name, status, location, and description
of all defined devices. The device status is one of the following:
Available |
The device is defined and configured. |
Defined |
The device is currently defined but not configured. The location is
still reserved for the device and no other device can be added at that
location. See "Devices
Overview for System Management" in AIX Version 4.3 System Management Guide: Operating System and Devices for more
information. |
Undefined |
The system does not recognize the device. |
- Choose the location where you want to
add the device.
OR
- Choose a location where you want to add
the device. See "Location
Codes" in AIX Version 4.3 System Management Guide: Communications and Networks for more information.
- Use the lsdev
command to determine which device currently occupies the specified location,
as follows:
lsdev -C | grep aa-bb-cc-dd
where aa-bb-cc-dd is the location code (found in step 1). The
location code can range from 2 to 12 characters in length.
The name of the device is displayed, along
with its present status.
- With the information from steps 1 and
2, either delete the existing device from the specified location and add
the new device, or add the new device at a different location.
0514-040 Error initializing a device into
the kernel
Possible Causes
- You were unable to configure a specific
device. While trying to initialize your device driver, you were unable
to load it as part of the kernel extension. The specific device driver
file in the /etc/drivers file is damaged or contains software errors.
- Your Object Data Management (ODM) database
file is damaged, and you are unable to configure your device.
Procedures for Recovery
- Check for possible software errors
if you are modifying your configuration method or device driver.
- Try replacing the device driver file
if you suspect that the device driver is damaged.
- Copy the device driver file from another
system that has the same release level as your system, either through the
network by running the ftp
command, or through a diskette by using the backup
and restore
commands. When you restore the file, make sure that it preserves the permission
code, ownership, and location of your previous file.
- Enter your command again.
- If you suspect that the ODM database
is damaged, try replacing the PdAt file.
- Copy the PdAt file from another
system that has the same release level as your current system, either through
the network by running the ftp command, or through a diskette by
using the backup and restore commands. When you restore the
file, make sure that it preserves the permission code, ownership, and location
of your previous file.
- Enter your command again.
0514-047 Cannot access a device
Possible Causes
- You specified the wrong connection address
to make a device available.
- The device that you are trying to add
is not attached to your system or has hardware problems.
Procedures for Recovery
- Check your device to make sure that
you entered the correct connection address.
If your device is connected to a SCSI card,
the number is on the back of the device. This number is a single-digit
number. In order to convert it to a connection number, add a 0 (zero) digit
to this number; that is, if the number is 1 (one), the connection number
is 10, and if the number is 2, the connection number is 20.
- Check to make sure that no other device
attached to the SCSI card has the same connection number as your device.
Use the lsdev
command to check the connection numbers of the device attached to the SCSI
card. If there is one number that matches your connection number, change
the number on the back of your device to a unique number.
If you are using SMIT, return to the SMIT
screen where the error occurred and enter the appropriate connection number.
Otherwise, reenter the mkdev
command with the appropriate connection address.
- If your device is connected to a serial
port, check to see if it is plugged in to the correct serial port, then
rerun your command.
If you suspect there is a hardware problem:
- Check your cables to make sure that they
are attached correctly.
- Check to see if your device is turned
on.
- Run diagnostics by using the diag
command.
0514-050 Cannot perform the requested
function because the specified device was not detected
Possible Causes
- The device you are trying to add is not
attached to your system or has hardware problems.
Procedures for Recovery
0514-062 Cannot perform the requested
function because the specified device is busy
Possible Causes
You specified a device that is being used
by one or more processes.
Procedures for Recovery
- Check to make sure you selected the
correct device.
If that is not the problem:
- Remove the process that is allocating
your device.
- Run the ps
-ef command to list which process is using the device you specified.
- Remove the process by using the kill
command.
If that does not resolve the problem:
- Reboot your system and reenter your
command if your system is still busy.
- Use the sync
command to update your i-node table.
- Run the shutdown
-Fr command. Wait for the login prompt.
- After you log in, reenter your command.
If your device is still busy:
- Run your command in single user mode.
- Shut down your system and turn the key
mode switch to Service.
- Reboot your system using the boot media.
- Select the Maintenance option from
the Installation and Maintenance menu, then select Access a Root
Volume Group.
- After identifying the correct volume group,
select Access this Volume Group and start a shell.
0514-063 The specified device driver name
is too long
Possible Causes
- The name of the device driver you want
to configure is too long. The device name must be less than 20 characters
in length in order to be added to the CuDvDr Object Data Management (ODM)
database file.
- Your libcfg.a library file is damaged.
Procedures for Recovery
- Change the name of your device driver
to a name with less than 20 characters.
- Replace the libcfg.a library file.
- Copy the libcfg.a file located
on your /lib directory from another system that has the same release
level as your current system, either through the network by running the
ftp command, or through a diskette by using the backup
and restore
commands. If you use the ftp
command, use the bin subcommand.
- When you restore the file, make sure that
it preserves the permission code, the ownership, and the location of your
previous file.
- Reenter your command.
0514-516 Device configuration database
lock service timed out
Possible Causes
- You ran a command that tried to access
a Configuration Object Data Management (CODM) file that is presently in
use or was closed incorrectly.
Procedures for Recovery
0514-521 Cannot find information in the
predefined device configuration database for the customized device: DeviceName
Possible Causes
- Your predefined device configuration database
PdDv file, located in the /usr/lib/objrepos file, is damaged.
Procedures for Recovery
- Replace the PdDv file.
Copy the PdDv file from another
system that has the same release level as your current system, either through
the network by running the ftp
command, or through a diskette, by using the backup
and restore
commands. When you restore the file, make sure that it preserves the permission
code, the ownership, and the location of your previous file.
- Reenter your command.
[ Previous |
Next |
Contents |
Glossary |
Home |
Search ]