0c0 User Requested Dump completed successfully. You requested a dump
using the sysdumpstart command, a dump key-sequence, or the RESET
button.
ACTION:
Examine dump now or save dump for later examination.
-
0c2 User Requested Dump started. You requested a dump using the
sysdumpstart command, a dump key-sequence, or the RESET button.
ACTION:
Wait 1 minute for dump to complete and the 3-Digit Display code
to change. If the the 3-Digit Display code is still '0c2' after
1 minute, the dump has failed to complete, a partial dump may be
present. Examine dump now or save dump for later examination.
Request dump to alternate dump device.
-
0c3 The dump is inhibited.
-
0c4 The dump did not complete. A partial dump may be present.
ACTION:
Examine partial dump now or save partial dump for later
examination. Request dump to alternate dump device.
Increase size of dump media to prevent recurrence.
-
0c5 Dump failed to start. An unexpected error occurred while
attempting to write to the dump media.
ACTION:
Request dump to alternate dump device.
-
0c6 User Requested Dump to the secondary dump device requested. You
requested a dump using the sysdumpstart command or the
Ctrl-Alt-Numpad2 key sequence.
ACTION:
Make sure that the device assigned as the secondary dump device
is ready to receive the dump, then key Ctrl-Alt-Numpad2 again.
-
0c7 Remote dump in progress.
-
0c8 Dump disabled. The system configuration did not include a dump
device for the requested dump.
ACTION:
Request dump to alternate dump device.
-
0c9 System initiated dump started. An unexpected system halt has
occurred, dump was started automatically.
ACTION:
Wait for dump to complete.
-
100 BIST completed successfully, control was passed to IPL ROS.
-
101 Initial BIST started following RESET or POR
-
102 BIST started following Power-On-RESET or push button pressed.
-
103 BIST could not determine the system model number.
-
104 BIST could not find the CBA.
-
105 BIST could not read from the OCS EPROM.
-
106 | BIST detected a module failure. CBA not found in S&S area
-
111 | BIST detected a module failure. (Press button for details)
-
112 Checkstop occurred during BIST and checkstop results could not be
logged out.
-
113 The BIST checkstop count was greater than 1. (=3)
-
120 BIST started CRC check on 875X EPROM
-
121 BIST detected a bad CRC on the OCS EPROM.
-
122 BIST started CRC check on the OCS EPROM.
-
123 BIST detected a bad CRC on the OCS NVRAM.
-
124 BIST started CRC check on the OCS NVRAM space.
-
125 BIST detected a bad CRC on the time of day NVRAM.
-
126 BIST started CRC check on the time of day NVRAM.
-
127 BIST detected a bad CRC on the 8752 EPROM
-
130 BIST presence test started or push button stuck.
-
140 BIST Failed, Box Manufacturing BIST bypass - run BIST anyway.
-
142 BIST Failed, Box Manufacturing normal mode of operation.
-
144 BIST Failed.
-
151 BIST started AIPGM test code (array initialiation on all chips).
-
152 BIST started DCLST test code (DC logic self test on all chips).
-
153 BIST started ACLST test code (AC logic self test on all chips).
-
154 BIST started AST test code (arry self test on all chips).
-
160 BIST detected a missing EPOW (Early Power On Warning) connector.
-
164 BIST encountered an error while reading low NVRAM.
-
165 BIST encountered an error while writing low NVRAM.
-
166 BIST encountered an error while reading high NVRAM.
-
167 BIST encountered an error while writing high NVRAM.
-
168 BIST encountered an error while reading the SIO (Serial I/O) register.
-
169 BIST encountered an error while writing the SIO (Serial I/O) register.
-
180 BIST logout failed or logout complete (displayed for 1 minute).
-
185 Checkstop occurred during BIST, 10 sec to hook up ESP before logout.
-
186 |
-
187 BIST was unable to identify the chip release level in the
checkstop logout data.
-
195 BIST logout completed.
-
*********************************************************************
* POST POST POST POST POST POST POST POST POST POST POST *
*********************************************************************
200 You tried to boot the system with the Mode Switch in the SECURE position
-
201 Checkstop occurred during IPL. FATAL
-
202 Machine_check_handler FATAL
-
203 Data_Storage_Interrupt_handler FATAL
-
204 Instruction_Storage_Interrupt_handler FATAL
-
205 External_Interrupt_handler FATAL
-
206 Alignment_Interrupt_handler FATAL
-
207 Program_Interrupt_handler FATAL
-
208 Floating_Point_Unavailable_handler FATAL
-
209 Reserved_900_handler FATAL
-
209 RSC2 POST - same LED value as Reserved_900_hdlr
-
20C | RS2 L2 Cache detected
-
210 SVC_1000_handler FATAL
-
211 IPL ROM CRC miscompare during IPL FATAL
-
212 Processor Planar Bad FATAL
-
212 RAMPOST Memory Configuration Reisters failure FATAL
-
213 Memory Card failure or Processor Planar Bad FATAL
-
213 RAMPOST full/hfwd & byte Load & Store failure FATAL
-
214 Power status register failed FATAL
-
214 RAMPOST PIO Load and Store circuitry failure FATAL
-
215 A low voltage condition is present FATAL
-
215 RAMPOST ECC Generation circuitry failure FATAL
-
216 RAMPOST ECC Correction circuitry failure FATAL
-
216 IPL ROM code being uncompressed into memory
-
217 RAMPOST Bit Steering Logic failure FATAL
-
217 End of Bootlist - same LED as Bit Steer Logic Fail
-
218 RAM POST testing for 1 MB of good memory
-
218 RAMPOST 1 Meg of good memory not found, address/remap fail FATAL
-
219 RAMPOST bit_map_generation FATAL
-
21C | RS2 L2 Cache post completed
-
/* Normal mode Default path selection from NVRAM IPL Device List
220 ROM scan selected for ipl
-
220 IPL Control Block being initialized.
-
221 NVRAM CRC miscompare occurred while trying to boot the AIX
Operating (Mode Switch in NORMAL position.) For systems with an
internal direct attached hard file, IPL ROM attempted to boot
from this hardfile before halting with this 3-Digit Display
code.
ACTION:
If the system halts with this value in the 3-Digit Display, boot
and run diagnostics to determine if there is an NVRAM failure.
The system automatically reinitializes NVRAM when you boot
diagnostics (or AIX Install/ Maintenance, or AIX Maintenance
Mode) so a subsequent attempt to boot the AIX Operating System
should not result in the system halting with this 3-Digit Display
code. The system does not automatically restore the contents of
NVRAM which you may have added, e.g. IPL device lists, you will
need to restore this information using whatever means you
originally used to create it.
-
222 Native I/O selected for ipl
-
223 SCSI devices selected for ipl
-
224 SLA selected for ipl
-
225 SJL or DBA (esdi hardfile) selected for ipl
-
226 Ethernet selected for ipl
-
227 Token Ring selected for ipl
-
228 expansion code selected for ipl
-
229 a normal mode device list is present but has no entries (null
list) or none of the valid entries succeeded in ipl
ACTION:
If the system halts with this value in the three digit display,
either the NVRAM device list is empty, the devices specified in
the list are not valid boot devices, or there is a problem with
the devices in the list. To determine if there is a problem with
the devices in the list, refer to the hardware problem
determination procedures in the RIOS Diagnostics Programs
Operators Guide. To modify the NVRAM device list, boot the AIX
Operating System and use the iplist command.
-
22C FDDI selected for ipl
-
/* Normal mode Default path selection from ROM IPL Device List
230 ROM scan selected for ipl
-
231 Ethernet chosen from menus
-
232 Native I/O selected for ipl
-
233 SCSI devices selected for ipl
-
234 SLA selected for ipl
-
234 9333 subsystem device selected for ipl
-
235 SJL or DBA (esdi hardfile) selected for ipl
-
236 Ethernet selected for ipl
-
237 Token Ring selected for ipl
-
238 Token Ring selected for ipl from menus
-
239 Menu selected device (Ethernat or Token Ring) failed to boot.
-
23C FDDI selected for ipl
-
/* Service mode Default path selection from NVRAM IPL Device List
240 ROM scan selected for ipl
-
241 devices specified in NVRAM IPL Devices List
-
242 Native I/O selected for ipl
-
243 SCSI devices selected for ipl
-
244 SLA selected for ipl
-
244 9333 subsystem device selected for ipl
-
245 SJL or DBA (esdi hardfile) selected for ipl
-
246 Ethernet selected for ipl
-
247 Token Ring selected for ipl
-
248 expansion code selected for ipl
-
249 a service mode device list is present but has no entries (null
list) or none of the valid entries succeeded in ipl
-
24C FDDI selected for ipl
ACTION: See action for error code 229
-
/* Service mode Default path selection from ROM IPL Device List
250 ROM scan selected for ipl
-
251 Ethernet chosen from menus
-
252 Native I/O selected for ipl
-
253 SCSI devices selected for ipl
-
254 SLA selected for ipl
-
254 9333 subsystem device selected for ipl
-
255 SJL or DBA (esdi hardfile) selected for ipl
-
256 Ethernet selected for ipl
-
257 Token Ring selected for ipl
-
258 Token Ring selected for ipl from menus
-
259 FDDI selected for ipl from menus
-
25C FDDI selected for ipl
-
260 Attempting Network IPL, menus and information present on screen
-
260 call to the user interface
-
260 NVRAM not initialized with bootlist, keyboard type and language
type even tho keyboard / display or tty connected to system
-
261 Attempting Network IPL, menus, no console display detected
-
261 Console handlers request led value
-
261 NVRAM not initialized with bootlist, keyboard type and language
type with no keyboard / display or tty connected to system
-
262 Attempting Network IPL, menus, no console keyboard detected
-
262 Console handlers request led value
-
263 Attempting Normal mode system restart from Family 2 feature ROM
specified in the NVRAM boot device list
-
271 Mouse and mouse port POST
-
272 Tablet port POST
-
278 Video ROM scan POST
-
279 FDDI POST
-
281 Keyboard POST
-
282 Parallel POST
-
283 Serial POST
-
284 7011/220 (SGA) POST
-
284 POWER Gt1 graphics adapter POST
-
285 POWER Gt3 (LEGA) graphics adapter POST
-
286 Token Ring POST in progress (Power On Self Test == POST)
-
287 Ethernet POST in progress
-
287 | Adapter card slots being queried
-
288 Microchannel POST in progress
-
288 Family 2 bus scan
-
289 Diskette POST
-
290 IO Planar Bad
-
290 IOCC POST
-
291 NIO POST being executed
-
292 SCSI POST being executed
-
293 SJL or Bus Attached Internal Hard File POST being executed
-
294 SLA POST
-
295 XX3 POST (Ethernet)
-
296 XX2 POST (Tolkenring)
-
296 ROM scan POST
-
297 XX1 POST
-
297 System model number could not be determined.
-
297 | System model number does not compare between OCS and ROS FATAL
| Attempting a software IPL
-
298 Attempting warm IPL
-
299 IPL ROS has completed loading and has passed control to
passed control to the loaded code
-
*********************************************************************
* LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST *
*********************************************************************
500 Querying Native I/O card (NIO or SIO).
-
501 Querying card in slot 1.
-
502 Querying card in slot 2.
-
503 Querying card in slot 3.
-
504 Querying card in slot 4.
-
505 Querying card in slot 5.
-
506 Querying card in slot 6.
-
507 Querying card in slot 7.
-
508 Querying card in slot 8.
-
510 Starting device configuration.
-
511 Device configuration completed.
-
512 Restoring device configuration files from media.
-
513 Restoring basic operating system installation files from media.
-
516 Contacting server during network boot.
-
517 Mounting client remote file system during network IPL (/ and /usr).
-
518 Remote mount of the / (root) and /usr file systems during network
boot did not complete successfully.
-
520 bus configuration running.
-
521 /etc/init invoked cfgmgr with invalid options, /etc/init
has been corrupted or incorrectly modified. FATAL
-
521 The /etc/inittab file has been incorrectly modified or corrupted.
-
522 The configuration manager has been invoked with conflicting
options. FATAL
-
522 The /etc/inittab file has been incorrectly modified or corrupted.
-
523 The configuration manager is unable to access the ODM data base. FATAL
-
523 The /etc/objrepos file is missing or inacessable.
-
524 The configuration manager is unable to access the config
rules object in the ODM data base. FATAL
-
524 The /etc/objrepos/Config_Rules file is missing or inacessable.
-
525 The configuration manager is unable to get data from customized
device object in the ODM data base. FATAL
-
525 The /etc/objrepos/CuDv file is missing or inacessable.
-
526 The configuration manager is unable to get data from customized
device driver object in the ODM data base. FATAL
-
526 The /etc/objrepos/CuDvDr file is missing or inacessable.
-
527 The configuration manager was invoked with the Phase 1 flag,
however, running Phase 1 at this point is not permitted. FATAL
-
527 The /sbir/rc.boot file has been incorrectly modified or corrupted.
-
528 The configuration manager can't find sequence rule or no program
name was specified in the ODM data base. FATAL
-
528 The /etc/objrepos/Config_Rules file has been incorrectly modified,
corrupted, or a program specified in the file is missing.
-
529 The configuration manager is unable to update ODM data or the root
file system is full.
-
530 The program 'savebase' returned an error.
-
531 The configuration manager is unable to access the PdAt object
class. FATAL
-
531 The /usr/lib/objrepos/PdAt file is missing or inacessable.
-
532 There is not enough memory for the configuration manager to
continue (malloc failure). FATAL
-
533 The configuration manager could not find a configure method for
a device.
-
533 The /usr/lib/objrepos/PdDv file has been incorrectly modified,
corrupted, or a program specified in the file is missing.
-
534 The configuration manager is unable to acquire data base lock. FATAL
-
535 HIPPI diagnostic interface being configured.
-
536 The configuration manager encountered more than one sequence
rule specified in the same phase. FATAL
-
536 The /etc/objrepos/Config_Rules has been incorrectly modified or
corrupted.
-
537 The configuration manager encountered an error when invoking
the program in the sequence rule.
-
537 The /etc/objrepos/Config_Rules has been incorrectly modified,
corrupted, or a program specified in the file is missing.
-
538 The configuration manager is passing control to a configuration
method.
-
539 The configuration method has ended and control has returned
to the configuration manager.
-
551 IPL Varyon of the root volume group is running.
-
552 IPL Varyon of the root volume group failed.
-
553 IPL Phase 1 is complete. (/etc/(un)mount missing or / or /tmp full
-
553 The /etc/inittab file has been incorrectly modified or corrupted.
-
554 Unable to define NFS swap device during network boot.
-
555 Unable to create NFS swap device during network boot.
-
555 ODM error when trying to varyon rootvg
-
556 Unable to configure NFS swap device during network boot.
-
556 LVM subroutine error from ipl_varyon
-
557 Unable to fsck or mount the root (/) filesystem
-
558 There is not enough memory available to continue the IPL.
-
570 Configuring virtual SCSI devices.
-
571 Configuring HIPPI common functions driver.
-
572 Configuring IPI-3 master transport driver for use with HIPPI.
-
573 Configuring IPI-3 slave transport driver for use with HIPPI.
-
574 Configuring IPI-3 transport services user interface driver.
-
575 Configuring IBM 9570 (FC9300) RAID 3 disk array driver.
-
576 Configuring vendor Async device driver.
-
577 Configuring vendor SCSI device driver.
-
578 Configuring vendor Commo device driver.
-
579 Configuring generic vendor device driver.
-
580 Configuring HIPPI TCPIP network interface driver.
-
581 Configuring PD TCPIP.
-
581 Configuring TCPIP.
-
582 Configuring a token ring data link control.
-
583 Configuring a ethernet data link control.
-
584 Configuring a IEEE ethernet data link control (802.3).
-
585 Configuring a SDLC MPQP data link control.
-
586 Configuring a QLLC X.25 data link control.
-
587 Configuring a NETBIOS.
-
588 Configuring a BSCRW.
-
590 Configuring diskless remote paging device.
-
591 Configuring LVM device driver (Logical Volume Manager).
-
592 Configuring HFT device driver (High Function Terminal).
-
593 Configuring SNA device drivers.
-
594 Configuring Asynchronous I/O
-
595 Configuring X.31 pseudo device (X.25 over ISDN).
-
596 Configuring SNA DLC/LAPE device.
-
597 Configuring OCS (Outboard Communication Server).
-
598 Configuring OCS hosts during system reboot.
-
599 Configuring FDDI data link control.
-
711 Unknown adapter being identified/configured.
-
712 Special graphics slot (SGA graphics slot) identified/configured.
-
720 Unknown Read/Write optical drive being identified/configured.
-
721 Unknown Disk being identified/configured.
-
721 Unknown SCSI device being identified/configured.
-
722 Unknown Disk being identified/configured.
-
723 Unknown CDROM being identified/configured.
-
724 Unknown Tape being identified/configured.
-
725 Unknown Display being identified/configured.
-
726 Unknown Input device being identified/configured.
-
727 Unknown Async device being identified/configured.
-
728 Parallel Printer being identified/configured.
-
729 Unknown Parallel device being identified/configured.
-
730 Unknown diskette drive type being identified/configured.
-
731 PTY being identified/configured.
-
732 Unknown SCSI Initiator
-
811 Processor Complex being identified/configured.
-
812 Common Standard Adapter Logic being identified/configured.
-
812 Memory being identified/configured.
-
813 Battery for Time-of-Day, NVRAM, etc. being identified/configured.
-
813 System I/O Control Logic being identified/configured.
-
814 NVRAM being identified/configured.
-
815 Floating Point Processor being identified/configured.
-
816 Operator Panel Logic being identified/configured.
-
817 Time of Day Logic being identified/configured.
-
818 Used by DA to report checkstop / machine checks
-
819 Graphics Input Device adapter being identified/configured.
-
821 Standard Keyboard adapter being identified/configured.
-
823 Standard Mouse adapter being identified/configured.
-
824 Standard Tablet adapter being identified/configured.
-
825 Standard Speaker adapter being identified/configured.
-
826 Serial Port 1 adapter being identified/configured.
-
827 Parallel port adapter being identified/configured.
-
828 Standard Diskette adapter being identified/configured.
-
831 3151 adapter being identified/configured.
-
831 Serial Port 2 being identified/configured.
-
834 64-Port Async Controller being identified/configured.
-
835 16-Port Async Concentrator being identified/configured.
-
836 128-Port Async Controller being identified/configured.
-
837 128-Port Remote Async Node (EIA-232) being identified/configured.
-
838 Bitternut Ethernet adapter being identified/configured.
-
839 Bitternut Connection Station being identified/configured.
-
841 8-Port Async adapter (EIA-232) being identified/configured.
-
842 8-Port Async adapter (EIA-422A) being identified/configured.
-
843 8-Port Async adapter (MIL-STD 188) being identified/configured.
-
844 Allthorn Raid array controller being identified/configured.
-
845 Allthorn Raid array being identified/configured.
-
847 16-Port Serial adapter (EIA-232) being identified/configured.
-
848 16-Port Serial adapter (EIA-422) being identified/configured.
-
849 X.25 Communications adapter being identified/configured.
-
850 Token-Ring Network adapter being identified/configured.
-
851 Sandpiper V-A being identified/configured.
-
852 Ethernet adapter being identified/configured.
-
853 SCSI DE I/O adapter being identified/configured.
-
854 3270 Connection being identified/configured.
-
855 4-Port Multiprotocol Controller being identified/configured.
-
857 FSLA adapter being identified/configured.
-
858 5085/86/88 adapter being identified/configured.
-
859 FDDI adapter being identified/configured.
-
860 Twin Tailed (Harrier) adapter being identified/configured.
-
861 Serial Optical Channel converter being identified/configured.
-
862 Block Multiplexer Channel adapter being identified/configured.
-
862 370 Parallel Channel adapter being identified/configured.
-
863 MAP adapter being identified/configured.
-
864 Serial Channel adapter being identified/configured.
-
865 370 Serial Channel adapter being identified/configured.
-
866 SCSI adapter being identified/configured.
-
867 Async Expansion adapter being identified/configured.
-
868 SCSI adapter being identified/configured. (Spock)
-
869 SCSI adapter being identified/configured.
-
870 Serial Disk adapter being identified/configured.
-
870 Harrier 2 adapter being identified/configured.
-
871 Graphics Subsystem adapter being identified/configured.
-
872 Grayscale Graphics adapter being identified/configured.
-
873 Skyway 16 Graphics adapter being identified/configured.
-
874 Color Graphics adapter being identified/configured.
-
875 Skyway 256 Graphics adapter being identified/configured.
-
876 8-Bit Color Graphics Processor being identified/configured.
-
877 Power Gt3/Gt4 being identified/configured.
-
877 LEGA Display adapter being identified/configured.
-
878 Pedernales Graphics adapter being identified/configured.
-
879 24-bit Color Graphics Processor being identified/configured.
-
880 7011/220 Graphics adapter being identified/configured. (SGA)
-
881 Channel Attached printer being identified/configured.
-
882 Serial Attached printer being identified/configured.
-
883 Pegasus Support (Japan)
-
884 3117 Scanner adapter being identified/configured.
-
885 3118 Scanner adapter being identified/configured.
-
886 3119 Scanner adapter being identified/configured.
-
887 Integrated Ethernet adapter being identified/configured.
-
888 System has halted.
-
889 SCSI adapter being identified/configured.
-
889 LACE SCSI DE adapter being identified/configured.
-
890 Corvette SCSI adapter being identified/configured.
-
891 Vendor SCSI adapter being identified/configured.
-
892 Vendor Display adapter being identified/configured.
-
893 Vendor LAN adapter being identified/configured.
-
894 Vendor Async/Communications adapter being identified/configured.
-
895 Vendor IEEE 488 adapter being identified/configured.
-
896 Vendor VME buss adapter being identified/configured.
-
897 HATSCON 370 channel adapter being identified/configured.
-
898 White Oak graphics adapter being identified/configured.
-
899 YUMA/CALVA attachment adapter being identified/configured.
-
900 ??? Attempting to boot from tape but mksysb missing after /bootrec
-
901 Vendor SCSI device being identified/configured.
-
902 Vendor Display being identified/configured.
-
903 Vendor Async device being identified/configured.
-
904 Vendor Parallel device being identified/configured.
-
905 Vendor other device being identified/configured.
-
906 IBM Premier Speech Recognition adapter I being identified/configured.
-
907 IBM Premier Speech Recognition adapter II being identified/configured.
-
908 Ruby graphics adapter being identified/configured.
-
909 PEGASUS LSA (LAN SCSI) adapter being identified/configured.
-
910 FCS 1/4 speed adapter being identified/configured.
-
911 FCS full speed adapter being identified/configured.
-
912 Allicat 2GB DE drive being identified/configured.
-
913 Corsair 2E DE drive being identified/configured.
-
914 Snobird SE tape drive being identified/configured.
-
915 Sonata-2 tape drive being identified/configured.
-
920 Bridge Box being identified/configured.
-
921 Keyboard 101 being identified/configured.
-
922 Keyboard 102 being identified/configured.
-
923 Keyboard Kanji being identified/configured.
-
924 Two-Button Mouse being identified/configured.
-
925 Three-Button Mouse being identified/configured.
-
926 Tablet 5083 Model 21 being identified/configured.
-
927 Tablet 5083 Model 22 being identified/configured.
-
928 Standard Speaker being identified/configured.
-
929 Dials being identified/configured.
-
930 Lighted Program Function Keys (LPFK) keyboard being
-
931 IP Router being identified/configured.
-
931 5086 Keyboard being identified/configured.
-
932 IP Router being identified/configured.
-
933 Async Planar being identified/configured.
-
934 Async Expansion Drawer being identified/configured.
-
935 1.44 MB 3.5-Inch diskette drive being identified/configured.
-
936 1.2 MB 5.25-Inch diskette drive being identified/configured.
-
937 HIPPI adapter being identified/configured.
-
938 122 Keyboard being identified/configured.
-
939 Tablet for 6 button cursor being identified/configured.
-
940 Used by memory DA
-
941 6180 plotter being identified/configured.
-
942 Baby Blue graphics adapter being identified/configured.
-
948 Portable disk drive being identified/configured.
-
949 Unknown direct buss-attached device being identified/configured.
-
950 Missing SCSI Options being identified/configured.
-
951 670 MB SCSI disk drive being identified/configured.
-
952 355 MB SCSI disk drive being identified/configured.
-
953 320 MB SCSI disk drive being identified/configured.
-
954 400 MB SCSI disk drive being identified/configured.
-
955 857 MB SCSI disk drive being identified/configured.
-
956 670 MB SCSI disk drive electronics card being identified/configured.
-
957 Direct Bus Attached disk drive being identified/configured.
-
957 120 MB Bus Attached disk drive being identified/configured.
-
958 160 MB Bus Attached disk drive being identified/configured.
-
959 160 MB SCSI disk drive being identified/configured.
-
960 1.37 GB SCSI disk drive being identified/configured. (Wannamingo
-
961 Route 66 - 2 Port Serial adapter being identified/configured.
-
962 Route 66 - Ethernet adapter being identified/configured.
-
963 SCSI Scanner (2456) adapter being identified/configured.
-
965 Route 66 - Token Ring adapter being identified/configured.
-
968 1.2 GB SCSI disk drive being identified/configured. (Corsair)
-
968 160 MB disk drive being identified/configured.
-
970 .5-Inch 9-Track tape drive being identified/configured.
-
971 150 MB .25-Inch tape drive being identified/configured.
-
972 8mm SCSI tape drive being identified/configured.
-
973 Other SCSI tape drive being identified/configured.
-
974 CDROM drive being identified/configured.
-
975 ERIMO R/W Optical drive being identified/configured.
-
976 RISC System 6000 SCSI I/O Controller Initiator
-
977 M-Audio capture and playback adapter being identified/configured.
-
977 ACPA adapter being identified/configured.
-
978 IEEE 488 adapter being identified/configured.
-
979 7246 SBS Frame Buffer adapter being identified/configured.
-
980 ISDN Basic adapter being identified/configured. (Athens/Pegasus)
-
980 IBM Switching Network Interface adapter being identified/configured.
-
981 ISDN Primary adapter being identified/configured. (Athens/Sparta)
-
981 UTE SCSI disk drive 540MB being identified/configured. (formerly AKAGI)
-
982 Graphics Visulation Server adapter being identified/configured .
-
983 XGA graphics adapter being identified/configured .
-
984 ISDN port being identified/configured.
-
984 SPITFIRE SCSI disk drive 1GB being identified/configured.
-
985 M-Video adapter being identified/configured. (VCA)
-
986 2.4 GB SCSI disk drive being identified/configured. (Wildcat)
-
987 CD-ROM XA being identified/configured. (Atlantis MM)
-
988 KILLY FDDI adapter being identified/configured.
-
989 200 MB SCSI disk drive being identified/configured. (KAI)
-
990 5 GB 8mm SCSI tape drive being identified/configured.
-
990 2.0B SCSI disk drive being identified/configured. (Allicat)
-
991 525 MB 1/4" SCSI tape drive being identified/configured. (Tundra)
-
992 4755 Crytographic adapter being identified/configured.
-
993 Raven File Server product being identified/configured.
-
994 5 GB 8mm SCSI tape drive being identified/configured. (Snobird / 990)
-
995 1/4" tape drive being identified/configured.
-
995 1.2 GB 1/4" SCSI tape drive being identified/configured.(Polar/Tundra 2)
-
996 1.0 GB SCSI Tape drive being identified/configured.
-
996 MP/A adapter being identified/configured.
-
997 FDDI adapter being identified/configured. (Foxtroft / twisted pair)
-
998 4mm tape drive being identified/configured. (Suite / HP)
-
999 OHIO Compression adapter being identified/configured.
-
c00 AIX Install / Maintance loaded correctly.
-
c01 Insert the first diagnostics diskette.
-
c02 Wrong diskette sequence used. REBOOT !!!
-
c03 The wrong diskette is in the diskette drive.
-
c04 The loading stopped with an irrecoverable error.
-
c05 A diskette error occured.
-
c06 The rc.boot configuration script is unable to determine type of boot.
-
c07 Insert the next diskette.
-
c08 RAM file system started incorrectly.
-
c09 The diskette drive is reading or writing a diskette.
-
c20 Low Level Debugger activated. An unexpected system halt has
occurred, and you have configured the system to activate the low
level debugger instead of doing a dump.
ACTION:
You can run debugger commands, including requesting a dump. When
you exit the debugger, the LED code will change, find the new LED
code in this list.
-
c21 The ifconfig command was unable to configure the network for the
client network host to boot.
-
c22 The tftp command was unable to read the client's ClientHostName.info
file during a client network boot.
-
c23 NFS qfsinstall failed for client network boot.
-
c24 Unable to read the client's ClientHostName.info file during client
network boot.
-
c25 Client did not mount miniroot during network install.
-
c26 Client did not mount the /usr file system during network boot.
-
c27 Attempting to boot from device other than tok(0-3) or ent(0-3).
-
c28 The system is unable to set the attributes of the network device.
-
c29 The system is unable to configure the network device.
-
c31 If no console has been configured, the system halts with this
value in the three-digit-display and the system displays
instructions for choosing a console on the native display.
System initialization and configuration will continue after
you choose a console.
If you are starting the system in SERVICE mode and the system
does not have a display or the display is not working and you
are unable to choose a console, system initialization and
configuration will complete without a console configured if you
turn the keyswitch to the NORMAL position.
-
c32 The console is a HFT. (Informational only)
-
c33 The console is a TTY. (Informational only)
-
c34 The console is a file. (Informational only)
-
c99 Diagnostics have completed. This code is only used when there
is no console.
-
EEE (hex 14 14 14) reserved for FAA to do a reset to control pqnel
This displays as a big E with the top bar missing
-
-----------------------------------------------------------------------
SP1 - 9076 error codes from Al Dix in Harrisburg, PA.
-----------------------------------------------------------------------
unn | SP2-specific LED values (page 299 Admin guide SH26-2486)
-
u00 | Invalid bootp_response in install_info file
-
u01 | Getting boot information
-
u02 | Configuring the boot network
-
u03 | tftp of /tftpboot/.install_info from boot install serve r failed
-
u04 | Expanding .install_info variables for use in rc.boot
-
u05 | tftp of /usr/lpp/ssp/install/backup/config.bff file failed
-
u06 | Starting to setup the display
-
u07 | Exiting phase 1 network boot
-
u20 | tftp of /usr/lpp/ssp/install/backup/dispdskt.bff file failed
-
u21 | Reconfiguring the network
-
u22 | Replacing the default network boot ODM cfgrules
-
u23 | Issuing config manager (cfgmgr)
-
u24 | Reconfiguring the network
-
u25 | Issuing config manager again (cfgmgr)
-
u26 | Configuring the console (cfgcon)
-
u30 | tftp of /usr/lpp/ssp/install/backup/instmaint.diskette failed
-
u31 | Restoring files in instmaint.diskette backup file
-
u32 | Configuring tape drives, if any
-
u33 | Invoking mk_autoinst_files to proceed with automatic netinsta ll
| (possible corruption of /usr/lpp/ssp/install/bin/config.bff)
-
u34 | Exiting prepare_auto_install routine
-
u50 | Beginning rc.boot phase 2 (get boot info & expand install_in fo
-
u54 | bosmain has been invoked to perform the netinstall
-
u56 | if node is /usr client, /usr filesystem mounted here
-
u61 | tftp of /etc/SDR_dest_info from boot/install server failed
-
u62 | Creating the /etc/firstboot file
-
u63 | tftp of /usr/lpp/ssp/install/config/firstboot.ssp from server f ailed
-
u64 | tftp of /usr/lpp/ssp/install/config/rc.boot.config from server failed
-
u65 | install/customize/maint has completed now rebooting (shutdown - Fr)
-
u70 | Beginning of rc.boot setup
-
u71 | Start of boot process for a network boot
-
u72 | Beginning of initialization for rc.boot
-
u88 | rc.boot determined that bootp_response is set to disk (invalid)
-
u89 | /usr client field (usr_client_adapter) has an invalid value
-
u90 | Use bootinfo cmd to get boot info and initialize for rc.boot
-
u91 | Gathering of boot information is complete
-
u92 | Determining the boot network information
-
u93 | Issuing ifconfig for the boot network
-
u94 | /usr not boot network, issuing ifconfig to mount /usr
-
u95 | Boot network configuration is complete
-
u98 | Starting bosmain for maintenance option
-
u99 | Invalid bootp_response specified in install_info file
-
c20 Low Level Debugger started.
-
