TITLE : Common LED Error Codes and descriptions OS LEVEL : AIX DATE : 07/04/99 VERSION : 1.0 ---------------------------------------------------------------------------- ------------------- Display Value: c03 ------------------- Explanation: Wrong diskette inserted. System Action: Waiting for the user to insert the proper diskette. User Action: Insert the correct diskette. When the display value changes, find that value in this list. If this value is displayed while the correct diskette is inserted, there is a problem with the diskette. If you have a backup copy of the diskette, use that instead. If you are unable to resolve the problem, report it to your software service organization. ------------------- Display Value: c06 ------------------- Explanation: The rc.boot configuration shell script is unable to determine type of boot. System Action: This error halts the system. User Action: Try loading AIX Install/Maintenance again. If still unable to resolve the problem, report it to your software service organization. ------------------- Display Value: c07 ------------------- Explanation: Insert next diskette. System Action: Waiting for the user to insert diskette. User Action: Insert the next diskette When the display value changes, rind that value in this list. ------------------- Display Value: c09 ------------------- Explanation: Progress indicator: Writing to or reading from diskette. Action: Accessing diskette. User Action: No action necessary. ------------------- Display Value: c21 ------------------- Explanation: The ifconfig command was unable to configure the network or the client network host. System Action: The system halts. User Action: You will need to log on to the server or to another client with superclient privileges to perform the following activities: 1. Verify that the client is set up correctly by running the following command: lsdclient -L ClientHostName Verify that the server's Internet Protocol (IP) address, the client's host name, and the client's root directory path are correct. If any of this information is incorrect, correct it using the chdclient command. 2. Verify that the network is operating correctly by running the following command: ping -c 3 ClientHostName ClientHostName refers to the client host that detected the error. If running the ping command reveals that the client host is connected to the network, use this command on other clients on the system to thoroughly test the status of the network. If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: c22 ------------------- Explanation: The tftp command was unable to read client's ClientHostName.info file during a client network boot. System Action: The system halts. User Action: You will need to log on to the server or to another client with superdient privileges to perform the following activities: 1. Verify that the client's ClientHostName.info file exists and is not empty by listing the contents of the /tftpboot directory with the following command: ls -l /tftpboot |pg If the ClientHostName.info file does not exist, use the mkdclient command to create one. 2. Verify that the client is set up correctly by running the following command: lsdclient -L ClientHostName Verify that the server's IP address, the client's host name, and the client's root directory path are correct. If any of this information is incorrect, correct it using the chdclient command. 3. Verify that the tftpd daemon is running or is ready to run on the server. On an AlXserver, enter: lssrc -s inetd -l | grep tftpd If the command returns inactive in the last field, use SMIT to add the inetd subserver tftpd An example follows for starting the tftpd daemon using SMIT: smit tcpip Using the screen selections, select the Further Configuration option, the Server Netowrk Services option, the Other Available Services option, the Super Daemon (inetd) option, and then inetd Subsystem option Now you can use the submenu option to start, show characteristics of, or stop the tftpd daemon. 4. verify that the network is operating correctly by running the following command: ping -c 3 ClientHostName ClientHostName refers to the client host that detected the error. If running the ping command reveals that the client host is connected to the network, use this command on other clients on the system to thoroughly test the status of the network. If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: c23 ------------------- Explanation: The ucfgdevice command was unable to unconfigure the network device. System Action: If the machine is a remote /usr system, it boots with the minimal /usr file system. If the machine is diskless or dataless, it halts. User Action: If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: c24 ------------------- Explanation: Unable to read the client's ClientHostName.info file during client network boot. System Action: The system halts. User Action: You will need to log on to the server or to another client with superolient privileges to perform the following activities: 1. Verify that the client's ClientHostName.info file exists and is not empty by listing the contents of the /tftpboot directory with the following command: ls -l /tftpboot | pg If the ClientHostName.info file does not exist, use the mkdclient command to create one. 2. Verify the the client is set up correctly by running the following command: lsdclient -L ClientHostName Verify that the server's IP address, the client's host name, and the client's root directory path are correct. If any of this information is incorrect, correct it using the chdclient command. 3. Run the following command to verify that the tftpd daemon is running on the server: ps -e | grep tftpd If the system does not return any data, the daemon is not running and must be started using SMIT or the startsrc command. 4. Verify that the network is operating correctly by running the following command: ping -c 3 ClientHostName ClientHostName refers to the client host that detected the error. If running the ping command reveals that the client host is connected to the network, use this command on other clients on the system to thoroughly test the status of the network. If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: c25 ------------------- Explanation: Client did not mount remote miniroot during network install. System Action: The system halts. User Action: You will need to log on to the server or to another client with superdient privileges to perform the following activities: 1, Verify that the client's root file system, which is /export/root/ClientHostName on the server, is exported by the server. To do this, enter: /usr/bin/showmount -e ServerHostName If the client's file system is not in the list, use a text editor to add it to the /etc/exports file. After you save the changes, run the following command to update the client's root file system: /usr/sbin/exportfs 2. Run the following command to verify that the nfsd daemon is running on the server: ps -e | grep nfsd If the system does not return any data, the daemon is not running and must be started using the following command: /etc/rc.nfs If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: c26 ------------------- Explanation: Client did not mount the /usr file system during network boot. System Action: The system halts. User Action: You will need to log on to the server or to another client with superolient privileges to perform the following activities: 1. Verify that the client's /usr file system, which is /export/exec/SPOTName on the server, is exported by the server. To do this, enter: /usr/bin/showmount -e ServerHostName If the client's file system is not in the list, use a text editor to add it to the /etc/exports file. After you save the changes, run the following command to update the client's root file system: /usr/sbin/exportfs 2. Run the following command to verify that the nfsd daemon is running on the server: ps -e | grep nfsd If the system does not return any data, the daemon is not running and must be started using the following command: /etc/rc.nfs If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: c27 ------------------- Explanation: The machine is trying to boot from a device other than tok[O-3] or ent[O-3]. System Action: If the machine is a remote /usr system, it boots with the minimal /usr file system. If the machine is diskless or dataless, it halts. User Action: If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: c28 ------------------- Explanation: The machine is unable to set the attributes of the network device. System Action: If the machine is a remote /usr system, it boots with the minimal /usr file system. If the machine is diskless or dataless, it halts. User Action: If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: c29 ------------------- Explanation: The machine is unable to configure the network device. System Action: If the machine is a remote /usr system, it boots with the minimal /usr file system. If the machine is diskless or dataless, it halts. User Action: If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: 510 ------------------- Explanation: Progress indicator: starting device configuration. System Action: Configuration manager started. If an unrecoverable error occurs, the system halts. User Action: If the system halts, perform the hardware problem- determination procedures in Common Diagnostics and Service Guide. If there is a hardware failure, report it to your hardware service organization. If not, report the failure to your software service organization; then stop. You have completed these procedures. ------------------- Display Value: 511 ------------------- Explanation: Progress indicator: device configuration completed. System Action: Configuration manager ended. If an unrecoverable error occurs, the system will halt. User Action: If the system halts, perform the hardware problem determination procedures in Common Diagnostics and Service Guide. If there is a hardware failure, report it to your hardware service organization. If not, report the failure to your software service organization; then stop. You have completed these procedures. ------------------- Display Value: 512 ------------------- Explanation: Progress indicator: restoring device configuration files from media. System Action: Reading device configuration files from media. If an unrecoverable error occurs, the system halts. User Action: If the system halts, perform the hardware problem- determination procedures in Common Diagnostics and Service Guide. If there is a hardware failure, report it to your hardware service organization. If not, report the failure to your software service organization; then stop. You have completed these procedures. ------------------- Display Value: 516 ------------------- Explanation: Progress indicator: contacting server during network boot. System Action: Contacting server during network boot. If an unrecoverable error occurs, the system halts. User Action: If the system halts, perform the hardware problem- determination procedures in Common Diagnostics and Service Guide. If there is a hardware failure, report it to your hardware service organization. If not, report the failure to your software service organization; then stop. You have completed these procedures. ------------------- Display Value: 517 ------------------- Explanation: Progress indicator: the / (root) and /usr file systems are being mounted. System Action: The system is attempting to mount the / (root) and /usr file systems. These file systems are of type boot. User Action: If the mount does not successfully complete during a network boot, the system changes the three-digit display value to 5l8. If the system halts with a 517 displayed in the three-digit display, log on to the server or to another client with superolient privileges to perform the following activities: 1. Verify that the type field for the / (root) and /usr file systems is correct in the client's /etc/filesystems file. To do this, enter: pg /export/root/ClientHostName/etc/filesystems Make sure that the / (root) and /usr stanzas contain a line that reads type--boot. If the type field is incorrect, use a text editor to correct it. 2. Verify that the client's file systems are exported by the server. To do this, run the following command: /usr/bin/showmount -e ServerHostName If the client's / (root) or /usr file system is not in the list, use a text editor to add it to the /etc/exports file. After you have saved the changes, run the following command to update the client's root file system: 3. Verify the the client is set up correctly by running the following command: lsdclient -L ClientHostName Verify that the server's IP address, the client's host name, and the client's root directory path are correct. If any of this information is incorrect, correct it using the chdclient command. 4. Run the following command to verify that the tftpd daemon is running on the server: ps -e | grep tftpd If the system does not return any data, the daemon is not running and must be started using SMIT or the startsrc command. 5. Verify that the network is operating correctly by running the following command: ping -c 3 ClientHostName ClientHostName refers to the client host that detected the error. If running the ping command reveals that the client host is connected to the network, use this command on other clients on the system to thoroughly test the status of the network. If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: c25 ------------------- Explanation: Client did not mount remote miniroot during network install. System Action: The system halts. User Action: You will need to log on to the server or to another client with superdient privileges to perform the following activities: 1, Verify that the client's root file system, which is /export/root/ClientHostName on the server, is exported by the server. To do this, enter: /usr/bin/showmount -e ServerHostName If the client's file system is not in the list, use a text editor to add it to the /etc/exports file. After you save the changes, run the following command to update the client's root file system: /usr/sbin/exportfs 2. Run the following command to verify that the nfsd daemon is running on the server: ps -e | grep nfsd /usr/sbin/exportfs 3. Run the following command to verify that the nfsd daemon is running on the server: ps -e | grep nfsd If the system does not return any data, the daemon is not running and must be started using the following command: /etc/rc nfs If the above steps do not correct the problem, perform the hardware problem-determination procedures in Common Diagnostics and Service Guide. If there is a hardware failure, report it to your hardware service organization. If not, report the failure to your software service organization; then stop. You have completed these procedures. ------------------- Display Value: 518 ------------------- Explanation: Remote mount of the / (root) and /usr file systems during network boot did not complete Successfully. System Action: The system halts. User Action: You will need to log on to the server or to another client with superdient privileges to perform the following activities: 1. Verify that the type field for the / (root) and /usr file systems is correct in the client's /etc/filesystems file. To do this, enter: pg /export/root/Cl ientHostName/etc/f ilesystems Make sure that the / (root) and /usr stanzas contain a line that reads type=boot. If the type field is incorrect, use a text editor to correct it. 2. Verify that the client's file Systems are exported by the server. To do this, run the following command: /usr/bin/showmount -e ServerHostName If the client's / (root) or /usr file system is not in the list, use a text editor to add it to the /etc/exports file. After you have saved the changes, run the following command to update the client's root file system: /usr/sbin/exportfs 3. Run the following command to verify that the nfsd daemon is running on the server: ps -e | grep nfsd If the system does not return any data, the daemon is not running and must be started using the following command: /eto/rc.nfs If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: 551 ------------------- Explanation: Progress indicator: a vary-on operation of the root volume group is in progress. System Action: System is varying on root volume group. If this process is not successful, the system halts. User Action: If the system halts with this value displayed, perform the hardware problem-determination procedures in Common Diagnostics and Service Guide to determine if there is a problem with the device where the files reside. If these procedures do not find a problem with a device, report the problem to your software service organization; then stop. You have completed these procedures. ------------------- Display Value: 552 ------------------- Explanation: A vary-on operation of the root volume group failed. System Action: System unable to vary-on the root volume group. This error halts the system. User Action: Perform the hardware problem-determination procedures in Common Diagnostics and Service Guide to determine if there is a problem with the device where the files reside. If these procedures do not find a problem with a device, the problem is usually due to bad information on the boot logical volume. Otherwise, the log logical volume (/dev/hd8) has been corrupted. TO correct the problem with the boot logical volume, enter Install/Maintenance mode. (Refer to AIX Install/Maintenance" in AIX Version 3.2 Problem Solving Guide and Reference for information on loading the Install/Maintenance mode onto your system.) Then run the savebase command. When the savebase command completes, issue the sync; sync command. After this command completes, restart the system in Normal mode. If this does not correct the problem, re-enter Install/Maintenance mode and enter the /usr/sbin/logform /dev/hd8 command. When this command completes, restart the system in Normal mode. If you are not familiar with this mode or are unable to correct the problem, report the problem to your software service organization; then stop. You have completed these procedures. ------------------- Display Value: 553 ------------------- Explanation: The /etc/inittab file has been incorrectly modified or is corrupted. System Action: Phase 1 Boot is completed and the mit command is invoked. User Action: If the system halts, either the / (root) or /tmp file system was full when the system was restarted. This problem can usually be corrected by entering Install/Maintenance mode and correcting or replacing the /etc/inittab file. To determine if either file system is full, enter: df / /tmp You may need to erase some files to free space before correcting the /etc/inittab file. You can accomplish this by removing the /smit.log and /smit.script files if they have become large. Before removing these files, you may want to copy them to diskette or tape. o To copy the SMIT files to diskette, enter: ls /smit.log /smit.script I backup -iv o To copy the SMIT files to streaming tape, enter: ls /smit.log /smit.script I backup -ivf /dev/rmt0 o To copy the SMIT files to 9-track tape, enter: ls /smit.log /smit.script I backup -ivf /dev/rnt0 After you have copied the files, remove them from the disk by entering: rm /smit.log /smit.script Refer to "AIX Install/Maintenance" in AIX Version 3.2 Problem Solving Guide and Reference for information on loading the Install/Maintenance mode onto your system. If you are not familiar with this mode or are unable to correct the problem, report the problem to your software service organization; then stop. You have completed these procedures. ------------------- Display Value: 555 ------------------- Explanation: Unable to create NFS swap device during network boot. System Action: The system halts. User Action: This problem can occur if NFS is experiencing problems or if the client and server are set up incorrectly. You will need to log on to the server or another client with superdient privileges to perform the following activities: o Verify that the network is operating correctly by running the following command: ping -c 3 ClientHostName ClientHostName refers to the client host that detected the error. If running the ping command reveals that the client host is connected to the network, use this command on other clients on the system to thoroughly test the status of the network. o Verify that the client is set up correctly by running the following command: lsdclient -L ClientHostName Verify that the server's IP address, the client's host name, and the client's root directory path are correct. If any of this information is incorrect, correct it using the chdclient command. If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: 556 ------------------- Explanation: Unable to configure NFS swap device during network boot. System Action: The system halts. User Action: This problem can occur if NFS is experiencing problems or if the client and server are set up incorrectly. You will need to log on to the server or another client with superdient privileges to perform the following activities: o Verify that the network is operating correctly by running the following command: ping -c 3 ClientHostName ClientHostName refers to the client host that detected the error. If running the ping command reveals that the client host is connected to the network, use this command on other clients on the system to thoroughly test the status of the network. o Verify that the client is set up correctly by running the following command: lsdclient -L ClientHostName Verify that the server's IP address, the client, and the client's root directory path are correct. If any of this information is incorrect, correct it using the chdclient command. If you are unable to correct the problem, contact your software service organization for assistance. ------------------- Display Value: 581 ------------------- Explanation: The machine is hanging while trying to configure TCP/IP. System Action: The system freezes. User Action: This problem could be caused because the client is logging messages to the server database while configuring network interfaces using the /etc/rc.net shell script. The shell script uses stanzas to define, load, and configure the appropriate network interfaces for every configured network adapter. Part of each stanza specifies output should be logged. To get the client to reboot, remove the message logging associated with the /usr/lib/methods/cfgif method in the client /etc/rc.net file that resides on the server. The stanza should read as follows: /usr/lib/methods/cfgif $* ------------------- Display Value: 592 ------------------- Explanation: Progress indicator: High Function Terminal (HFT) device driver being configured. System Action: The configuration method for HFT is being run. If an unrecoverable error occurs, the system halts. User Action: If the system halts with this value, perform the hardware problem-determination procedures in Common Diagnostics and Service Guide. If these procedures indicate a problem, report the problem to your hardware service organization. Otherwise, report the problem to your software service organization; then stop. You have completed these procedures. Related Information Diskless Workstation Management Introduction. Diskless Workstation Troubleshooting. DWM Error Messages.