Lenovo NetVista Hardware Maintenance Manual for NetVista 6266, 6270, 6276, 627 - Page 52

BIOS Error Codes, Messages, beeps, Action/FRU, Enter

Get Lenovo NetVista PDF manuals and user guides View all Lenovo NetVista manuals
Add to My Manuals
Save this manual to your list of manuals

Page 52 highlights

Table 2-1 BIOS Error Codes, Messages, and Beeps List BIOS Error Codes, Messages, Action/FRU beeps NOTE: To diagnose a problem, first find the BIOS error messages, codes, or beeps in left column. If directed to a check procedure, replace the FRU indicated in the check procedure. If no check procedure is indicated, the first Action/FRU listed in right column is the most likely cause. Hard Disk(s) failure (40) Hard Disk Drive controller diagnostics failed. Hard Disk(s) failure (20) Hard Disk Drive initialization error. Hard Disk(s) failure (10) Unable to recalibrate fixed disk. Non-System disk or disk error Insert a system disk into Drive A: and press . Replace and strike any key when If you assumed the system would boot from the hard drive, make sure ready the controller is inserted correctly and all cables are properly attached. Be sure the disk is formatted as a boot device. Then reboot the system. OFFENDING SEGMENT: This message is used in conjunction with the I/O CHANNEL CHECK and RAM PARITY ERROR messages when the segment that has caused the problem has been isolated. PRESS A KEY TO REBOOT This will be displayed at the bottom of the screen when an error occurs that requires you to reboot. Press any key and the system will reboot. PRESS F1 TO DISABLE NMI, F2 When BIOS detects a Non-maskable Interrupt condition during boot, TO REBOOT this will allow you to disable the NMI and continue to boot, or you can reboot the system with the NMI enabled. RAM PARITY ERROR - Indicates a parity error in Random Access Memory. CHECKING FOR SEGMENT ... Memory parity Error at ... Indicates a memory parity error at a specific location. You can use this location along with the memory map for your system to find and replace the bad memory chips. Memory Verify Error at. Indicates an error verifying a value already written to memory. Use the location along with your system's memory map to locate the bad chip. OFFENDING ADDRESS NOT FOUND This message is used in conjunction with the I/O CHANNEL CHECK and RAM PARITY ERROR messages when the segment that has caused the problem cannot be isolated. ERROR ENCOUNTERED INITIALIZING HARD DRIVE Hard drive cannot be initialized. Be sure the adapter is installed correctly and all cables are correctly and firmly attached. Also be sure the correct hard drive type is selected in Setup. ERROR INITIALIZING HARD DISK CONTROLLER Cannot initialize controller. Make sure the cord is correctly and firmly installed in the bus. Be sure the correct hard drive type is selected in Setup. Also check to see if any jumper needs to be set correctly on the hard drive. FLOPPY DISK CNTRLR ERROR Cannot find or initialize the floppy drive controller. Make sure the OR NO CNTRLR PRESENT controller is installed correctly and firmly. If there are no floppy drives installed, be sure the Diskette Drive selection in Setup is set to NONE. 52

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
52
Table 2-1 BIOS Error Codes, Messages, and Beeps List
BIOS Error Codes, Messages,
beeps
Action/FRU
NOTE:
To diagnose a problem, first find the BIOS error messages, codes, or beeps in left column. If
directed to a check procedure, replace the FRU indicated in the check procedure. If no check procedure
is indicated, the first Action/FRU listed in right column is the most likely cause.
Hard Disk(s) failure (40)
Hard Disk Drive controller diagnostics failed.
Hard Disk(s) failure (20)
Hard Disk Drive initialization error.
Hard Disk(s) failure (10)
Unable to recalibrate fixed disk.
Non-System disk or disk error
Replace and strike any key when
ready
Insert a system disk into Drive A: and press <
Enter
>.
If you assumed the system would boot from the hard drive, make sure
the controller is inserted correctly and all cables are properly attached.
Be sure the disk is formatted as a boot device. Then reboot the
system.
OFFENDING SEGMENT:
This message is used in conjunction with the I/O CHANNEL CHECK
and RAM PARITY ERROR messages when the segment that has
caused the problem has been isolated.
PRESS A KEY TO REBOOT
This will be displayed at the bottom of the screen when an error
occurs that requires you to reboot. Press any key and the system will
reboot.
PRESS F1 TO DISABLE NMI, F2
TO REBOOT
When BIOS detects a Non-maskable Interrupt condition during boot,
this will allow you to disable the NMI and continue to boot, or you can
reboot the system with the NMI enabled.
RAM PARITY ERROR –
CHECKING FOR SEGMENT ...
Indicates a parity error in Random Access Memory.
Memory parity Error at ...
Indicates a memory parity error at a specific location. You can use this
location along with the memory map for your system to find and
replace the bad memory chips.
Memory Verify Error at.
Indicates an error verifying a value already written to memory. Use the
location along with your system's memory map to locate the bad chip.
OFFENDING ADDRESS NOT
FOUND
This message is used in conjunction with the I/O CHANNEL CHECK
and RAM PARITY ERROR messages when the segment that has
caused the problem cannot be isolated.
ERROR ENCOUNTERED
INITIALIZING HARD DRIVE
Hard drive cannot be initialized. Be sure the adapter is installed
correctly and all cables are correctly and firmly attached. Also be sure
the correct hard drive type is selected in Setup.
ERROR INITIALIZING HARD
DISK CONTROLLER
Cannot initialize controller. Make sure the cord is correctly and firmly
installed in the bus. Be sure the correct hard drive type is selected in
Setup. Also check to see if any jumper needs to be set correctly on
the hard drive.
FLOPPY DISK CNTRLR ERROR
OR NO CNTRLR PRESENT
Cannot find or initialize the floppy drive controller. Make sure the
controller is installed correctly and firmly. If there are no floppy drives
installed, be sure the Diskette Drive selection in Setup is set to NONE.