- 论坛徽章:
- 0
|
|
0c0 The dump completed successfully \r\n0c1 The dump failed due to an I/O error. \r\n0c2 A user-requested dump has started. You requested a dump using the SYSDUMPSTART command, a dump key sequence, or the Reset button. \r\n \r\n0c3 The dump is inhibit \r\n0c4 The dump did not complete. A partial dump was written to the dump device. There is not enough space on the dump deviceto contain the entire dump. To prevent this problem from occuring again, you must increase the size of your dumpmedia. \r\n \r\n \r\n0c5 The dump failed to start. An unecpected error occured while the system was attempting to write to the dump media. \r\n0c6 A dump to the secondary dump device was requested. Make the secondary dump device ready, then press CTRL-ALT-NUMPAD2. \r\n0c7 Reserved. \r\n0c8 The dump function is disabled. No primary dump device is configured. \r\n0c9 A dump is in progress. \r\n0cc Unknown dump failure \r\n \r\n \r\n ---------- Diagnostics Load Progress Indicators ----------- \r\n \r\nc00 AIX Install/Maintenance loaded successfully. \r\nc01 Insert the first diagnostic diskette. \r\nc02 Diskettes inserted out of sequence. \r\nc03 The wrong diskette is in the drive. \r\nc04 The loading stopped with an irrecoverable error. \r\nc05 A diskette error occurred. \r\nc08 RAM filesystem started incorrectly. \r\nc07 Insert the next diagnostic diskette. \r\nc09 The diskette drive is reading or writing a diskette. \r\nc20 An unexpected halt occured, and the system is configured to enter the kernel debug program instead of entering asystem dump. \r\n \r\nc21 The \'ifconfig\' command was unable to configure the network for the client network host. \r\nc22 The \'tftp\' command was unable to read client\'s ClientHostName.info file during a client network boot. \r\nc24 Unable to read client\'s ClientHostName.info file during a client network boot. \r\nc25 Client did not mount remote miniroot during network install. \r\nc26 Client did not mount the /usr filesystem during the network boot. \r\nc29 System was unable to configure the network device. \r\nc31 Select the console display for the diagnostics. To select \"No console display\", set the key mode switch to normal thento Service. The diagnostic program will then load and run the diagnostics automatically. \r\n \r\nc32 A direct-attached display (HFT) was selected. \r\nc33 a TTY terminal attached to serial ports S1 or S2 was selected. \r\nc34 A file was selected. The console messages store in a file \r\nc40 Configuration files are been restored. \r\nc41 Could not determine the boot type or device. \r\nc42 Extracting data files from diskette. \r\nc43 Diagboot cannot be accessed. \r\nc44 Initialyzing installation database with target disk information. \r\nc45 Cannot configure the console. \r\nc46 Normal installation processing. \r\nc47 Could not create a physical volume identifier (PVID) on disk. \r\nc48 Prompting you for input. \r\nc49 Could not create or form the JFS log. \r\nc50 Creating rootvg volume group on target disk \r\nc51 No paging space were found. \r\nc52 Changing from RAM environment to disk environment. \r\nc53 Not enough space in the /tmp directory to do a preservation installation. \r\nc54 Installing either BOS or additionnal packages. \r\nc55 Could not remove the specified logical volume in a preservation installation. \r\nc56 Running user-defined customization. \r\nc57 Failure to restore BOS. \r\nc58 Display message to turn the key. \r\nc59 Could not copy either device special files, device ODM, or volume group information from RAM to disk. \r\nc61 Failed to create the boot image. \r\nc70 Problem Mounting diagnostics CDROM disc. \r\nc99 Diagnostics have completed. This code is only used when there is no console. \r\n \r\n \r\n --------Debugger Progress Indicators ---------- \r\n \r\nc20 Kernel debug program activated. An unexpected system halt has occured, and you have configured the system \r\n to enter the kernel debug program instead of performing a dump. \r\n \r\n \r\n ---------Built-In Self Test (Bist) Indicators--------- \r\n \r\n100 BIST completed successfully. Control was passed to IPL ROS. \r\n101 BIST started following RESET \r\n102 BIST started following Power-on Reset \r\n103 BIST could not determine the system model number. \r\n104 Equipment conflict. BIST could not find the CBA. \r\n105 BIST could not read the OCS EPROM. \r\n106 BIST detected a module error. \r\n111 OCS stopped. BIST detected a module error. \r\n112 A checkstop occured during BIST. \r\n113 BIST checkstop count is greater than 1. \r\n120 BIST starting a CRC check on the 8752 EPROM. \r\n121 BIST detected a bad CRC in the first 32K of the OCS EPROM. \r\n122 BIST started a CRC check on the first 32K of the OCS EPROM. \r\n123 BIST detected a bad CRC on the OCS area of NVRAM. \r\n124 BIST started a CRC check on the OCS area of NVRAM. \r\n125 BIST detected a bad CRC on the time-of-day area of NVRAM. \r\n126 BIST started a CRC check on the time-of-day area of the NVRAM. \r\n127 BIST detected a bad CRC on the 8752 EPROM. \r\n130 BIST presence test started. \r\n140 BIST failed: procedure error \r\n142 BIST failed: procedure error \r\n143 Invalid memory configuration. \r\n144 BIST failed; procedure error. \r\n151 BIST started AIPGM test code. \r\n152 BIST started DCLST test code. \r\n153 BIST started ACLST test code. \r\n154 BIST started AST test code. \r\n160 Bad EPOW Signal/Power status signal \r\n161 BIST being conducted on BUMP I/O \r\n162 BIST being conducted on JTAG \r\n163 BIST being conducted on Direct I/O \r\n164 BIST being conducted on CPU \r\n165 BIST being conducted on DCB and Memory \r\n166 BIST being conducted on interrupts \r\n170 BIST being conducted on \'Multi-Processor \r\n180 BIST logout failed. \r\n182 BIST COP bus not responding \r\n185 A checkstop condition occured during the BIST \r\n186 System logic-generated checkstop (Model 250 only) \r\n187 Graphics-generated checkstop (Model 250) \r\n195 BIST logout completed. \r\n888 BIST did not start \r\n \r\n \r\n ------- Power-On Self Test ------- \r\n \r\n200 IPL attempted with keylock in the SECURE position. \r\n201 IPL ROM test failed or checkstop occured (irrecoverable) \r\n202 IPL ROM test failed or checkstop occured (irrecoverable) \r\n203 Unexpected data storage interrupt. \r\n204 Unexpected instruction storage interrupt. \r\n205 Unexpected external interrupt. \r\n206 Unexpected alignment interrupt. \r\n207 Unexpected program interrupt. \r\n208 Unexpected floating point unavailable interrupt. \r\n209 Unexpected SVC interrupt. \r\n20c L2 cache POST error. (The display shows a solid 20c for 5 seconds \r\n210 Unexpected SVC interrupt. \r\n211 IPL ROM CRC comparison error (irrecoverable). \r\n212 RAM POST memory configuration error or no memory found (irrecoverable). \r\n213 RAM POST failure (irrecoverable). \r\n214 Power status register failed (irrecoverable). \r\n215 A low voltage condition is present (irrecoverable). \r\n216 IPL ROM code being uncompressed into memory. \r\n217 End of bootlist encountered. \r\n218 RAM POST is looking for 1M bytes of good memory. \r\n219 RAM POST bit map is being generated. \r\n21c L2 cache is not detected. (The display shows a solid 21c for 5 sec) \r\n220 IPL control block is being initialized. \r\n221 NVRAM CRC comparison error during AIX. \r\n IPL(Key Mode Switch in Normal mode). \r\n Reset NVRAM by reaccomplishing IPL in Service mode. For systems with an internal, direct-bus-attached(DBA)disk,IPL \r\n ROM attempted to perform an IPL from that disk before halting with this three-digit display values. \r\n222 Attempting a Normal mode IPL from Standard I/O planar attached devices specified in NVRAM IPL Devices List. \r\n223 Attempting a Normal mode IPL from SCSI attached devices specified in NVRAM IPL Devices List. \r\n Note: May be caused by incorrect jumper setting for external SCSI devices or by incorrect SCSI terminator. \r\n REFER FFC B88 \r\n224 Attempting a Normal mode restart from 9333 subsystem device specified in NVRAM device list. \r\n225 Attempting a Normal mode IPL from IBM 7012 DBA disk attached devices specified in NVRAM IPL Devices List. \r\n226 Attempting a Normal mode restart from Ethernet specified in NVRAM device list. \r\n227 Attempting a Normal mode restart from Token Ring specified in NVRAM device list. \r\n228 Attempting a Normal mode IPL from NVRAM expansion code. \r\n229 Attempting a Normal mode IPL from NVRAM IPL Devices List; cannot IPL from any of the listed devices, or there are \r\n no valid entry in the Devices List. \r\n22c Attempting a normal mode IPL from FDDI specified in NVRAM IPL device list. \r\n230 Attempting a Normal mode restart from adapter feature ROM specified in IPL ROM devices list. \r\n231 Attempting a Normal mode restart from Ethernet specified in IPL ROM devices list. \r\n232 Attempting a Normal mode IPL from Standard I/O planar attached devices specified in Rom Default Device List. \r\n233 Attempting a Normal mode IPL from SCSI attached devices specified in IPL ROM Default Device List. \r\n234 Attempting a Normal mode restart from 9333 subsystem device specified in IPL ROM device list. \r\n235 Attempting a Normal mode IPL from IBM 7012 DBA disk attached devices specified in IPL ROM Default Device List. \r\n236 Attempting a Normal mode restart from Ethernet specified in IPL ROM default devices list. \r\n237 Attempting a Normal mode restart from Token Ring specified in IPL ROM default device list. \r\n238 Attempting a Normal mode restart from Token Ring specified by the operator. \r\n239 System failed to restart from the device chosen by the operator. \r\n23c Attempting a normal mode IPL from FDDI specified in IPL ROM device list. \r\n240 Attempting a Service mode restart from adapter feature ROM. \r\n241 Attempting a Normal mode IPL from devices specified in the NVRAM IPL Devices List. \r\n242 Attempting a Service mode IPL from Standard I/O planar attached devices specified in NVRAM IPL Devices List. \r\n243 Attempting a Service mode IPL from SCSI attached devices specified in NVRAM IPL Devices List. \r\n244 Attempting a Service mode restart from 9333 subsystem device specified in NVRAM device list. \r\n245 Attempting a Service mode IPL from IBM 7012 DBA disk attached devices specified in NVRAM IPL Devices List. \r\n246 Attempting a Service mode restart from Ethernet specified in NVRAM device list. \r\n247 Attempting a Service mode restart from Token Ring specified in NVRAM device list. \r\n248 Attempting a Service mode IPL from NVRAM expansion code. \r\n249 Attempting a Service mode IPL from NVRAM IPL Devices List; cannot IPL from any of the listed devices, or there areno valid entries in the Devices List. \r\n \r\n24c Attempting a service mode IPL from FDDI specified in NVRAM IPL device list. \r\n250 Attempting a Service mode restart from adapter feature ROM specified in IPL ROM device list. \r\n251 Attempting a Service mode restart from Ethernet specified in IPL ROM device list. \r\n252 Attempting a Service mode IPL from standard I/O planar attached devicesspecified in ROM Default Device List. \r\n253 Attempting a Service mode IPL from SCSI attached devices specified in IPL ROM Default Device List. \r\n254 Attempting a Service mode restart from 9333 subsystem device specified in IPL ROM device list. \r\n255 Attempting a Service mode IPL from IBM 7012 DBA disk\'attached devices specified in IPL ROM Default Devices List. \r\n256 Attempting a Service mode restart from Ethernet specified in IPL ROM default device list. \r\n257 Attempting a Service mode restart from Token Ring specified in IPL ROM default device list. \r\n258 Attempting a Service mode restart from Token Ring specified by the operator. \r\n259 Attempting a Service mode restart from FDDI specified by the operator. \r\n \r\n25c Attempting a normal mode IPL from FDDI specified in IPL ROM device list. \r\n260 Information is being displayed on the display console. \r\n261 Information will be displayed on the tty terminal when the \"1\" key is pressed on the tty terminal keyboard. \r\n262 A keyboard was not detected as being connected to the system\'s \r\n NOTE: Check for blown planar fuses or for a corrupted boot on disk drive \r\n263 Attempting a Normal mode restart from adapter feature ROM specified in NVRAM device list. \r\n269 Stalled state - the system is unable to IPL \r\n271 Mouse port POST. \r\n272 Tablet port POST. \r\n277 Auto Token-Ring LANstreamer MC 32 Adapter \r\n278 Video ROM Scan POST. \r\n279 FDDI adapter POST. \r\n280 3COM Ethernet POST. \r\n281 Keyboard POST executing. \r\n282 Parallel port POST executing \r\n283 Serial port POST executing \r\n284 POWER Gt1 graphadapte POST executing \r\n285 POWER Gt3 graphadapte POST executing \r\n286 Token Ring adapter POST executing. \r\n287 Ethernet adapter POST executing. \r\n288 Adapter card slots being queried. \r\n289 GTO POST. \r\n290 IOCC POST error (irrecoverable). \r\n291 Standard I/O POST running. \r\n292 SCSI POST running. \r\n293 IBM 7012 DBA disk POST running. \r\n294 IOCC bad TCW SIMM in slot location J being tested. \r\n295 Graphics Display adapter POST, color or grayscale. \r\n296 ROM scan POST. \r\n297 System model number does not compare between OCS and ROS \r\n (irrecoverable). Attempting a software IPL. \r\n298 Attempting a software IPL (warm boot). \r\n299 IPL ROM passed control to the loaded program code. \r\n301 Flash Utility ROM failed or checkstop occured (irrecoverable) \r\n302 Flash Utility ROM failed or checkstop occured (irrecoverable) \r\n302 Flash Utility ROM: User prompt, move the key to the service in order to perform an optional Flash Update. LED \r\n will only appear if the key switch is in the SECURE position. This signals the user that a Flash Update may be \r\n initiated by moving the key switch to the SERVICE position. If the key is moved to the SERVICE position, \r\n LED 303 will be displayed. This signals the user to press the reset button and select optional Flash Update. \r\n303 Flash Utility ROM: User prompt, press the reset button in order to perform an optional Flash Update. LED \r\n only appear if the key switch is in the SECURE position. This signals the user that a Flash Update may be initiated \r\n by moving the key switch to the SERVICE position. If the key is moved to the SERVICE position, LED 303 will be \r\n displayed. This signals the user to press the reset button and select optional Flash Update. \r\n304 Flash Utility ROM IOCC POST error (irrecoverable) \r\n305 Flash Utility ROM standard I/O POST running. \r\n306 Flash Utility ROM is attempting IPL from Flash Update Boot Image. \r\n307 Flash Utility ROM system model number does not compare between OCS and ROM (irrecoverable). \r\n308 Flash Utility ROM: IOCC TCW memory is being tested. \r\n309 Flash Utility ROM passed control to a Flash Update Boot Image. \r\n311 Flash Utility ROM CRC comparison error (irrecoverable). \r\n312 Flash Utility ROM RAM POST memory configuration error or no memory found ( iirecoverable). \r\n313 Flash Utility ROM RAM POST failure( irrecoverable). \r\n314 Flash Utility ROM Power status register failed (irrecoverable). \r\n315 Flash Utility ROM detected a low voltage condition. \r\n318 Flash Utility ROM RAM POST is looking for good memory. \r\n319 Flash Utility ROM RAM POST bit map is being generated. \r\n322 CRC error on media Flash Image. No Flash Update performed. \r\n323 Current Flash Image is being erased. \r\n324 CRC error on new Flash Image after Update was performed. (Flash Image is corrupted). \r\n325 Flash Image successful and complete. \r\n \r\n500 Querying Native I/O slot. \r\n501 Querying card in Slot 1 \r\n502 Querying card in Slot 2 \r\n503 Querying card in Slot 3 \r\n504 Querying card in Slot 4 \r\n505 Querying card in Slot 5 \r\n506 Querying card in Slot 6 \r\n507 Querying card in Slot 7 \r\n508 Querying card in Slot 8 \r\n510 Starting device configuration. \r\n511 Device configuration completed. \r\n512 Restoring device configuration files from media. \r\n513 Restoring basic operating system installation files from media. \r\n516 Contacting server during network boot \r\n517 Mounting client remote file system during network IPL. \r\n518 Remote mount of the root and /usr filesystems failed during network boot. \r\n520 Bus configuration running. \r\n521 /etc/init invoked cfgmgr with invalid options; /etc/init has been corrupted or incorrectly modified \r\n (irrecoverable error). \r\n522 The configuration manager has been invoked with conflicting options (irrecoverable error). \r\n523 The configuration manager is unable to access the ODM database (irrecoverable error). \r\n524 The configuration manager is unable to access the config rules object in the ODM database (irrecoverable error). \r\n525 The configuration manager is unable to get data from a customized device object in the ODM database \r\n (irrecoverable error). \r\n526 The configuration manager is unable to get data from a customized device driver objet in the ODM database \r\n (irrecoverable error). \r\n527 The configuration manager was invoked with the phase 1 flag; running phase 1 flag; running phase 1 at this point \r\n is not permitted (irrecoverable error). \r\n528 The configuration manager cannot find sequence rule, or no program was specified in the ODM database \r\n (irrecoverable error). \r\n529 The configuration manager is unable to update ODM data \r\n (irrecoverable error). \r\n530 The program \"savebase\" returned an error. \r\n531 The configuration manager is unable to access PdAt object class \r\n (irrecoverable eroor) \r\n532 There is not enough memory to continue (malloc failure); \r\n irrecoverable error. \r\n533 The configuration manager could not find a configure method for a device. \r\n534 The configuration manager is unable to aquire database lock. irrecoverable error. \r\n536 The configuration manager encountered more than one sequence rule specified in the same phase. (irrecoverable error). \r\n537 The configuration manager encountered an error when invoking the program in the sequence rule. \r\n538 The configuration manager is going to invoke a configuration \r\n539 The configuration method has terminated, and control has returned to the configuration manager. \r\n551 IPL Varyon is running \r\n \r\n552 IPL Varyon failed. \r\n553 IPL phase 1 is complete. \r\n554 Unable to define NFS swap device during network boot \r\n555 Unable to define NFS swap device during network boot \r\n556 Logical Volume Manager encountered error during IPL varyon. \r\n557 The root filesystem will not mount. \r\n558 There is not enough memory to continue the IPL. \r\n559 Less than 2MB of good memory are available to load the AIX kernel. \r\n570 Virtual SCSI devices being configured. \r\n571 HIPPI common function device driver being configured. \r\n572 HIPPI IPI-3 master transport driver being configured. \r\n573 HIPPI IPI-3 slave transport driver being configured. \r\n574 HIPPI IPI-3 transport services user interface device driver being configured. \r\n576 Generic async device driver being configured. \r\n577 Generic SCSI device driver being configured. \r\n578 Generic commo device driver being configured. \r\n579 Device driver being configured for a generic device. \r\n580 HIPPI TCPIP network interface driver being configured. \r\n581 Configuring TCP/IP. \r\n582 Configuring token ring data link control. \r\n583 Configuring an Ethernet data link control. \r\n584 Configuring an IEEE ethernet data link control. \r\n585 Configuring an SDLC MPQP data link control. \r\n586 Configuring a QLLC X.25 data link control. \r\n587 Configuring NETBIOS. \r\n588 Configuring a Bisync Read-Write (BSCRW). \r\n589 SCSI target mode device being configured. \r\n590 Diskless remote paging device being configured. \r\n591 Configuring an LVM device driver \r\n592 Configuring an HFT device driver \r\n593 Configuring SNA device drivers. \r\n594 Asynchronous I/O being defined or configured. \r\n595 X.31 pseudo device being configured. \r\n596 SNA DLC/LAPE pseudo device being configured. \r\n597 OCS software being configured. \r\n598 OCS hosts being configured during system reboot. \r\n599 Configuring FDDI data link control. \r\n5c0 Streams-based hardware drive being configured. \r\n5c1 Streams-based X.25 protocol being configured. \r\n5c2 Streams-based X.25 COMIO emulator driver being configured. \r\n5c3 Streams-based X.25 TCP/IP interface driver being configured. \r\n5c4 FCS adapter device driver being configured. \r\n5c5 SCB network device driver for FCS is being configured. \r\n5c6 AIX SNA channel being configured. \r\n600 Starting network boot portion of /sbin/rs.boot \r\n602 Configuring network parent devices. \r\n603 /usr/lib/methods/defsys \r\n /usr/lib/methods/cggsys, or \r\n /usr/lib/methods/cggbus failed. \r\n604 Configuring physical network boot device. \r\n605 Configuring physical network boot device failed. \r\n606 Running /usr/sbin/ifconfig on logical network boot device. \r\n607 /usr/sbin/ifconfig failed. \r\n608 Attempting to retrieve the client.info file with tftp. Note that a flashing 608 indicates multiple attempts \r\n to retrieve the client_info file are occuring. \r\n609 The client.info file does not exist or it is zero length. \r\n610 Attempting remote mount of NFS file system \r\n611 Remote mount of the NFS filesystem failed. \r\n612 Accessing remote files; unconfiguring network boot device. \r\n614 Configuring local paging devices. \r\n615 Configuring of a local paging device failed. \r\n616 Converting from diskette to dataless configuration. \r\n617 Diskless to dataless configuration failed. \r\n618 Configuring remote (NFS) paging devices. \r\n619 Configuration of a remote (NFS) paging device failed. \r\n620 Updating special device files and ODM in permanent filesystem with data from boot RAM filesystem. \r\n622 Boot process configuring for operating system installation. \r\n \r\n650 IBM SCSD disk drive drive being configured \r\n700 Progress indicator. A 1.1GB 8-bit SCSI disk drive being identified or configured. \r\n701 Progress indicator. A 1.1GB 16-bit SCSI SE disk drive being identified or configured. \r\n702 Progress indicator. A 1.1GB 16-bit SCSI differential disk drive being identified or configured. \r\n703 Progress indicator. A 2.2GB 8-bit SCSI disk drive being identified or configured. \r\n704 Progress indicator. A 2.2GB 16-bit SCSI SE disk drive being identified or configured. \r\n705 The configuration method for the 2.2GB 16-bit differential SCSI disk drive is being run. If a irrecoverableerror occurs, the system halts. identified or configured. \r\n \r\n706 Progress indicator. A 4.5GB 16-bit SE SCSI disk drive is being identified or configured. \r\n707 Progress indicator. A 4.5GB 16-bit differential SCSI drive is being identified or configured. \r\n708 Progress indicator: A L2 cache is being identified or configured. \r\n710 POWER GXT150M graphics adapterbeing ientifyied or configured. \r\n711 Unknown adapter being identified or configured. \r\n712 Graphics slot bus configuration is executing. \r\n713 The IBM ARTIC960 device is being configured. \r\n714 A video capture adapter is being configured. \r\n715 The Ultimedia Services audio adapter is being configured. This LED displays briefly on the panel. \r\n720 Unknown read/write optical drive type being configured. \r\n721 Unknown disk or SCSI device being identified or configured. \r\n722 Unknown disk being identified or configured. \r\n723 Unknown CDROM being identified or configured. \r\n724 Unknown tape drive being identified or configured. \r\n725 Unknown display being identified or configured. \r\n726 Unknown input device being idenor configured \r\n727 Unknown adync device being idenor configured |
|
免费注册
发表于 2004-03-26 15:08
