LENOVO products, data, computer software, and services have been developed exclusively at private expense and
are sold to governmental entities as commercial items as defined by 48 C.F.R. 2.101 with limited and restricted
rights to use, reproduction and disclosure.
LIMITED AND RESTRICTED RIGHTS NOTICE: If products, data, computer software, or services are delivered
pursuant a General Services Administration ″GSA″ contract, use, reproduction, or disclosure is subject to restrictions
set forth in Contract No. GS-35F-05925.
Contents
Chapter 1. About this manual..........................1
Important Safety Information ..............................1
This Hardware Maintenance Manual contains information to help you solve problems that might occur in
your server. It describes the diagnostic tools that come with the server, error codes and suggested actions,
and instructions for replacing failing components.
Replaceable components are of three types:
v Self-service customer replaceable unit (CRU): Replacement of self-service CRUs is your responsibility.
If Lenovo
v Optional-service customer replaceable unit: You may install an optional-service CRU yourself or
request Lenovo to install it, at no additional charge, under the type of warranty service that is
designated for the server.
v Field replaceable unit (FRU): FRUs must be installed only by trained service technicians.
The most recent version of this document is available at http://www.lenovo.com/support.
Before servicing a Lenovo product, be sure to read the Safety Information. See “Important Safety
Information.”
For information about the terms of the warranty and getting service and assistance, see the Warranty andSupport Information document.
Important Safety Information
®
installs a self-service CRU at your request, you will be charged for the installation.
Be sure to read all caution and danger statements in this book before performing any of the instructions.
Veuillez lire toutes les consignes de type DANGER et ATTENTION du présent document avant
d’exécuter les instructions.
Lesen Sie unbedingt alle Hinweise vom Typ ″ACHTUNG″ oder ″VORSICHT″ in dieser Dokumentation,
bevor Sie irgendwelche Vorgänge durchführen
Leggere le istruzioni introdotte da ATTENZIONE e PERICOLO presenti nel manuale prima di eseguire
una qualsiasi delle istruzioni
Certifique-se de ler todas as instruções de cuidado e perigo neste manual antes de executar qualquer uma
das instruções
Es importante que lea todas las declaraciones de precaución y de peligro de este manual antes de seguir
las instrucciones.
Each caution and danger statement in this document is labeled with a number. This number is used to
cross reference an English-language caution or danger statement with translated versions of the caution
or danger statement in the Safety Information document.
For example, if a caution statement is labeled ″Statement 1,″ translations for that caution statement are in
the Safety Information document under ″Statement 1.″
Be sure to read all caution and danger statements in this document before you perform the procedures.
Read any additional safety information that comes with the server or optional device before you install
the device.
Attention: Use No. 26 AWG or larger UL-listed or CSA certified telecommunication line cord.
Electrical current from power, telephone, and communication cables is hazardous.
To avoid a shock hazard:
v Do not connect or disconnect any cables or perform installation,
maintenance, or reconfiguration of this product during an electrical storm.
v Connect all power cords to a properly wired and grounded electrical outlet.
v Connect to properly wired outlets any equipment that will be attached to this product.
v When possible, use one hand only to connect or disconnect signal cables.
v Never turn on any equipment when there is evidence of fire, water, or structural damage.
v Disconnect the attached power cords, telecommunications systems, networks, and modems before
you open the device covers, unless instructed otherwise in the installation and configuration
procedures.
v Connect and disconnect cables as described in the following table when installing, moving, or
opening covers on this product or attached devices.
To Connect:To Disconnect:
1. Turn everything OFF.
2. First, attach all cables to devices.
3. Attach signal cables to connectors.
4. Attach power cords to outlet.
5. Turn device ON.
1. Turn everything OFF.
2. First, remove power cords from outlet.
3. Remove signal cables from connectors.
4. Remove all cables from devices.
Chapter 1. About this manual3
Statement 2:
CAUTION:
When replacing the lithium battery, use only a type battery recommended by the manufacturer. If your
system has a module containing a lithium battery, replace it only with the same module type made by
the same manufacturer. The battery contains lithium and can explode if not properly used, handled, or
disposed of.
Do not:
v Throw or immerse into water
v Heat to more than 100°C (212°F)
v Repair or disassemble
Dispose of the battery as required by local ordinances or regulations.
CAUTION:
When laser products (such as CD-ROMs, DVD drives, fiber optic devices, or transmitters) are
installed, note the following:
v Do not remove the covers. Removing the covers of the laser product could result in exposure to
hazardous laser radiation. There are no serviceable parts inside the device.
v Use of controls or adjustments or performance of procedures other than those specified herein
might result in hazardous radiation exposure.
DANGER
Some laser products contain an embedded Class 3A or Class 3B laser diode. Note the following.
Laser radiation when open. Do not stare into the beam, do not view directly with optical
instruments, and avoid direct exposure to the beam.
Class 1 Laser Product
Laser Klasse 1
Laser Klass 1
Luokan 1 Laserlaite
Appareil A Laser de Classe 1
`
Chapter 1. About this manual5
Statement 4:
≥ 18 kg (39.7 lb)≥ 32 kg (70.5 lb)≥ 55 kg (121.2 lb)
CAUTION:
Use safe practices when lifting.
Statement 5:
CAUTION:
The power control button on the device and the power switch on the power supply do not turn off the
electrical current supplied to the device. The device also might have more than one power cord. To
remove all electrical current from the device, ensure that all power cords are disconnected from the
power source.
CAUTION:
Never remove the cover on a power supply or any part that has the following label attached.
Hazardous voltage, current, and energy levels are present inside any component that has this label
attached. There are no serviceable parts inside these components. If you suspect a problem with one
of these parts, contact a service technician.
Statement 26:
CAUTION:
Do not place any object on top of rack-mounted devices.
Attention: This server is suitable for use on an IT power distribution system whose maximum
phase-to-phase voltage is 240 V under any distribution fault condition.
Important: This product is not suitable for use with visual display workplace devices according to Clause
2 of the German Ordinance for Work with Visual Display Units.
Important information about replacing RoHS compliant FRUs
RoHS, The Restriction of Hazardous Substances in Electrical and Electronic Equipment Directive
(2002/95/EC) is a European Union legal requirement affecting the global electronics industry. RoHS
requirements must be implemented on Lenovo products placed on the market and sold in the
European Union after June 2006. Products on the market before June 2006 are not required to have
RoHS compliant parts. If the parts are not compliant originally, replacement parts can also be
noncompliant, but in all cases, if the parts are compliant, the replacement parts must also be
compliant.
Note: RoHS and non-RoHS FRU part numbers with the same fit and function are identified with unique
FRU part numbers.
Lenovo plans to transition to RoHS compliance well before the implementation date and expects its
suppliers to be ready to support Lenovo’s requirements and schedule in the EU. Products sold in 2005
will contain some RoHS compliant FRUs. The following statement pertains to these products and any
product Lenovo produces containing RoHS compliant parts.
Chapter 1. About this manual7
RoHS compliant ThinkServer RS210 parts have unique FRU part numbers. Before or after June, 2006,
failed RoHS compliant parts must always be replaced using RoHS compliant FRUs, so only the FRUs
identified as compliant in the system Hardware Maintenance Manual or direct substitutions for those
FRUs can be used.
Products marketed before June 2006Products marketed after June 2006
Current or original partReplacement FRUCurrent or original partReplacement FRU
Non-RoHSCan be Non-RoHSMust be RoHSMust be RoHS
Non-RoHSCan be RoHS
Non-RoHSCan sub to RoHS
RoHSMust be RoHS
Note: A direct substitution is a part with a different FRU part number that is automatically shipped by
the distribution center at the time of order.
Turkish statement of compliance
The Lenovo product meets the requirements of the Republic of Turkey Directive on the Restriction of the
Use of Certain Hazardous Substances in Electrical and Electronic Equipment (EEE).
Türkiye EEE Yönetmeliğine Uygunluk Beyanı
Bu Lenovo ürünü,
ve Elektronik Eşyalarda Bazı Zararlı Maddelerin Kullanımının
Sınırlandırılmasına Dair Yönetmelik (EEE)” direktiflerine uygundur.
This chapter provides general information that applies to all machine types supported by this publication.
Features and technologies
The server uses the following features and technologies:
v UEFI-compliant server firmware
UEFI replaces the basic input/output system (BIOS) and defines a standard interface between the
operating system, platform firmware, and external devices. The server design combines the UEFI
capabilities and features with legacy BIOS compatibility. UEFI-compliant servers are capable of starting
UEFI-compliant operating systems, BIOS-based operating systems, and BIOS-based adapters as well as
UEFI-compliant adapters.
Note: This server does not support DOS.
v Dual-core or quad-core processing
®
The server supports one Intel
v Integrated management module
The Integrated management module (IMM) combines service processor functions, video controller, and
(when an optional virtual media key is installed) remote presence function in a single chip. The IMM
provides advanced service-processor control, monitoring, and alerting function. If an environmental
condition exceeds a threshold or if a system component fails, the IMM lights LEDs to help you
diagnose the problem, records the error in the event log, and alerts you to the problem. Optionally, the
IMM also provides a virtual presence capability for remote server management capabilities. The IMM
provides remote server management through the following industry-standard interfaces:
– Intelligent Platform Management Interface (IPMI) version 2.0
– Simple Network Management Protocol (SNMP) version 3
– Common Information Model (CIM)
– Web browser
For additional information, see “Using the integrated management module” on page 215.
v Remote presence capability and blue-screen capture
The remote presence and blue-screen capture features are integrated functions of the integrated
management module (IMM) and are available with the purchase of the optional Lenovo Virtual Media
Key. A virtual media key is required to enable the remote presence and blue-screen capture features.
The remote presence feature provides the following functions:
– Remotely viewing video with graphics resolutions up to 1280 x 1024, regardless of the system state
– Remotely accessing the server, using the keyboard and mouse from a remote client
– Mapping the DVD drive, diskette drive, and USB flash drive on a remote client, and mapping ISO
and diskette image files as virtual drives that are available for use by the server
– Uploading a diskette image to the IMM memory and mapping it to the server as a virtual drive
The blue-screen capture feature captures the video display contents before the IMM restarts the server
when the IMM detects an operating-system hang condition. A system administrator can use the
blue-screen capture to assist in determining the cause of the hang condition.
See“Using the remote presence capability and blue-screen capture” on page 218 for additional
information.
v Large system-memory capability
Xeon®or Celeron®dual-core or quad-core microprocessor.
The memory bus supports up to 24 GB of memory when registered DIMMs are installed. The server
supports up to 8 GB if unbuffered DIMMs are installed. The memory controller supports error
correcting code (ECC) for up to six industry-standard PC3-8500 or PC3-10600R-999, 1066 and 1333
MHz, DDR3 (third-generation double-data-rate), registered or unbuffered, synchronous dynamic
random access memory (SDRAM) dual inline memory modules (DIMMs).
v Integrated network support
The server comes with an integrated Intel Gigabit Ethernet controller, which supports connection to a
10 Mbps, 100 Mbps, or 1000 Mbps network. For more information, see “Configuring the Gigabit
Ethernet controllers” on page 219.
v Integrated Trust Platform Module
This integrated security chip performs cryptographic functions and stores private and public secure
keys. It provides the hardware support for the Trusted Computing Group (TCG) specification.
v Large data-storage capacity and hot-swap capability
The server supports a maximum of four 2.5-inch hot-swap Serial Attached SCSI (SAS) hard disk drives,
two 3.5-inch simple-swap Serial ATA (SATA) hard disk drives, or two 3.5-inch hot-swap SAS or SATA
hard disk drives, depending on the server model.
With the hot-swap feature, you can add, remove, or replace hard disk drives without turning off the
server.
v PCI card capabilities
The server has two PCI interface slots (one supports low-profile cards and one supports half-length,
full-height cards). Both slots can support PCI Express PCI cards.
v RAID support
The RAID controller provides hardware redundant array of independent disks (RAID) support. The
standard RAID controller provides RAID levels 0, 1, and 1E. Optional RAID PCI cards are available for
purchase that provide additional RAID levels.
v Systems-management capabilities
The server comes with an Integrated Management Module (IMM). When the IMM is used with the
systems-management software that comes with the server, you can manage the functions of the server
locally and remotely. The IMM also provides system monitoring, event recording, and network alert
capability. The systems-management connector provides additional security by physically separating
the management network traffic from the production network. You can use the Setup Utility to
configure the server to use a dedicated systems-management network or a shared network.
v TCP/IP offload engine (TOE) support
The Ethernet controllers in the server support TOE, which is a technology that offloads the TCP/IP
flow from the microprocessor and I/O subsystem to increase the speed of the TCP/IP flow. When an
operating system that supports TOE is running on the server and TOE is enabled, the server supports
TOE operation. See the operating-system documentation for information about enabling TOE.
Note: The Linux operating system does not support TOE.
v Preboot diagnostics program
The preboot diagnostics programs are stored on the integrated USB memory. They collect and analyze
system information to aid in diagnosing server problems. The diagnostic programs collect the following
information about the server:
– System configuration
– Network interfaces and settings
– Installed hardware
– Service processor status and configuration
– Vital product data, firmware, and UEFI (formerly called BIOS) configuration
– Hard disk drive health
– RAID controller configuration
– Event logs for RAID controllers and service processors
The diagnostics programs create a merged log that includes events from all collected logs. The
information is collected into a file that you can send to the Lenovo technical support team to help
diagnose a problem. Additionally, you can view the information locally through a generated text report
file. You can also copy the log to a removable medium and view the HTML log from a Web browser.
For additional information about diagnostics, see Chapter 4, “Diagnostics,” on page 19.
v EasyStartup DVD
The ThinkServer EasyStartup program guides you through the configuration of RAID controllers and
the installation of the operating system and device drivers. See “Using the EasyStartup DVD” on page
209 for details.
v EasyManage DVD
The ThinkServer EasyManage program helps you manage and administer your servers through remote
problem notification as well as monitoring and alerting.
Specifications
The following information is a summary of the features and specifications of the server. Depending on
the server model, some features might not be available, or some specifications might not apply.
Table 1. Features and specifications
Microprocessor:
v Supports one Intel
3400 series) or dual-core (Celeron G1101,
Pentium G6950, or core i3 series)
processor with the IbexPeak 3420 chip
set and Multi-chip Package (MCP)
processor architecture
v Designed for LGA 1156 socket
v Scalable up to four cores
v 32 KB instruction cache, 32 KB data
cache, and up to 8 MB cache that is
shared among the cores
v Support for Intel
Technology (EM64T)
Note:
v Use the Setup utility to determine the
type and speed of the microprocessor.
Memory:
v Minimum: 1 GB
v Maximum: 32 GB
– 16 GB using unbuffered DIMMs
(UDIMMs)
– 32 GB using registered DIMMs
(RDIMMs)
v Types: PC3-8500 or PC3-10600R-999
(single-rank or double-rank), 1066, and
1333 MHz, ECC, DDR3 registered or
unbuffered SDRAM DIMMs only
v Connectors: Six dual inline memory
module (DIMM) connectors, two-way
interleaved
v Supports:
– 1 GB, 2 GB, and 4 GB (when
available) unbuffered DIMMS
– 1 GB, 2 GB, 4 GB, and 8 GB (when
available) registered DIMMs
®
quad-core (Xeon
®
Extended Memory 64
SATA optical drives:
v UltraSlim DVD-ROM combo (optional)
v Multi-burner (optional)
Hard disk drive expansion bays
(depending on the model):
One of the following configurations:
v Four 2.5-inch hot-swap SAS hard disk
drive bays
v Two 3.5-inch hot-swap SAS or hot-swap
SATA hard disk drive bays
v Two 3.5-inch simple-swap SAS hard
disk drive bays
PCI expansion slots:
Supports two PCI riser slots on the riser
card that connects to slots 1 and 2 on the
system board:
v Slot 1 supports low-profile cards (PCI
Express Gen2 x8
v Slot 2 supports 3/4-length, full-height
cards (PCI Express Gen2 x8 or PCI-X
1.0a 64-bit/133 MHz)
Power supply:
One 351-watt power supply or one
351-watt high efficiency power supply.
Fans: The server comes standard with five
speed-controlled fans.
Integrated functions:
v Integrated management module (IMM),
which provides service processor control
and monitoring functions, video
controller, and (when the optional
virtual media key is installed) remote
keyboard, video, mouse, and remote
hard disk drive capabilities
v Intel 82574L Gb Ethernet controller with
TCP/IP Offload Engine (TOE) and Wake
®
on LAN
v Seven Universal Serial Bus (USB) 2.0
ports (two front, four rear, and one
internal for the optional USB
Hypervisor flash device)
v Two Ethernet ports
v Four-port integrated SATA controller
v Integrated Trusted Platform Module
(TPM) support
v One serial port
v One VGA port
support
Chapter 2. General information
11
Table 1. Features and specifications (continued)
RAID controllers:
v An IBM ServeRAID-BR10il SAS/SATA
Controller that provides RAID levels 0,
1, and 1E (comes standard on some
hot-swap SAS and hot-swap SATA
models).
v An optional IBM ServeRAID-MR10i
SAS/SATA Controller SAS/SATA
adapter that provides RAID levels 0, 1,
5, 6, and 10 can be ordered.
v An optional IBM ServeRAID-M1015
SAS/SATA controller that provides
RAID levels 0,1,10, and 5 can be
ordered.
Acoustical noise emissions:
v Sound power, idling: 6.5 bels maximum
v Sound power, operating: 6.5 bels
maximum
Environment:
v Air temperature:
– Server on: 10°C to 35°C (50.0°F to
95.0°F); altitude: 0 to 914.4 m (3000 ft)
– Server on: 10°C to 32°C (50.0°F to
89.6°F); altitude: 914.4 m (3000 ft) to
2133.6 m (7000.0 ft)
– Server off: 10°C to 43°C
(50°F to 109.4°F); maximum altitude:
2133.6 m (7000.0 ft)
– Shipping: -40°C to 60°C
(-104°F to 140°F)
v Humidity:
– Server on: 8% to 80%
– Server off: 8% to 80%
v Particulate contamination:
Attention: Airborne particulates and
reactive gases acting alone or in
combination with other environmental
factors such as humidity or temperature
might pose a risk to the server. For
information about the limits for
particulates and gases, see “Notices,” on
page 221.
Video controller (integrated into IMM):
v Matrox G200
v SVGA compatible video controller
v DDR2 128 MB SDRAM video memory
v Avocent Digital Video Compression
v Video memory is not expandable
Note: The maximum video resolution is
1280 x 1024
Size:
v Height: 43 mm (1.69 inches, 1U)
v Depth: 560.1 mm (22 inches)
v Width: 430 mm (17.3 inches)
v Maximum weight: 11.4 kg (25.1 lb)
when fully configured
Heat output:
Approximate heat output:
v Minimum configuration: 171 BTU per
hour (50 watts)
v Maximum configuration: 1024 BTU per
hour (300 watts)
Electrical input:
v Sine-wave input (50 / 60 Hz) required
v Input voltage low range:
– Minimum: 100 V ac
– Maximum: 127 V ac
v Input voltage high range:
– Minimum: 200 V ac
– Maximum: 240 V ac
v Input kilovolt-amperes (kVA),
approximately:
– Minimum: 0.102 kVA
– Maximum: 0.55 kVA
Notes:
1. Power consumption and heat output
vary depending on the number and
type of optional features installed and
the power-management optional
features in use.
2. The sound levels were measured in
controlled acoustical environments
according to the procedures specified
by the American National Standards
Institute (ANSI) S12.10 and ISO 7779
and are reported in accordance with
ISO 9296. Actual sound-pressure levels
in a given location might exceed the
average values stated because of room
reflections and other nearby noise
sources. The noise emission level stated
in the declared (upper limit)
sound-power level, in bels, for a
random sample of system.
3. There is no keyboard connector or
mouse connector on the server. You
can connect a USB keyboard and USB
mouse to the server by using the USB
connectors.
Software
Lenovo provides software to help get your server up and running.
EasyStartup
The ThinkServer EasyStartup program simplifies the process of configuring your RAID controllers and
installing supported Microsoft Windows and Linux operating systems and device drivers on your server.
The EasyStartup program is provided with your server on DVD. The DVD is self starting (bootable). The
User Guide for the EasyStartup program is on the DVD and can be accessed directly from the program
interface. For additional information, see “Using the EasyStartup DVD” on page 209.
The ThinkServer EasyManage Core server provides centralized hardware and software inventory
management and secure automated system management through a centralized console. The ThinkServer
EasyManage Agent enables other clients on the network to be managed by the centralized console. The
ThinkServer EasyManage Core Server is supported on 32-bit Windows Server 2008 products. The
ThinkServer EasyManage Agent is supported on 32-bit and 64-bit Windows, Red Hat, and SUSE
operating systems.
You can solve many problems without outside assistance by following the troubleshooting procedures in
this Hardware Maintenance Manual and on the Lenovo Web site. This document describes the diagnostic
tests that you can perform, troubleshooting procedures, and explanations of error messages and error
codes. The documentation that comes with your operating system and software also contains
troubleshooting information.
Checkout procedure
The checkout procedure is the sequence of tasks that you should follow to diagnose a problem in the
server.
About the checkout procedure
Before you perform the checkout procedure for diagnosing hardware problems, review the following
information:
v Read the safety information that begins on page 1.
v The diagnostic programs provide the primary methods of testing the major components of the server,
such as the system board, Ethernet controller, keyboard, mouse (pointing device), serial ports, and hard
disk drives. You can also use them to test some external devices. If you are not sure whether a problem
is caused by the hardware or by the software, you can use the diagnostic programs to confirm that the
hardware is working correctly.
v When you run the diagnostic programs, a single problem might cause more than one error message.
When this happens, correct the cause of the first error message. The other error messages usually will
not occur the next time you run the diagnostic programs.
Exception: If multiple error codes or system-board LEDs indicate a microprocessor error, the error
might be in the microprocessor or in the microprocessor socket. See “Microprocessor problems” on
page 58 for information about diagnosing microprocessor problems.
v Before you run the diagnostic programs, you must determine whether the failing server is part of a
shared hard disk drive cluster (two or more servers sharing external storage devices). If it is part of a
cluster, you can run all diagnostic programs except the ones that test the storage unit (that is, a hard
disk drive in the storage unit) or the storage adapter that is attached to the storage unit. The failing
server might be part of a cluster if any of the following conditions is true:
– You have identified the failing server as part of a cluster (two or more servers sharing external
storage devices).
– One or more external storage units are attached to the failing server and at least one of the attached
storage units is also attached to another server or unidentifiable device.
– One or more servers are located near the failing server.
Important: If the server is part of a shared hard disk drive cluster, run one test at a time. Do not run
any suite of tests, such as “quick” or “normal” tests, because this might enable the hard disk drive
diagnostic tests.
v If the server is halted and a POST error code is displayed, see “Event logs” on page 19. If the server is
halted and no error message is displayed, see “Troubleshooting tables” on page 50 and “Solving
undetermined problems” on page 103.
v For information about power-supply problems, see “Solving power problems” on page 102.
v For intermittent problems, check the error log; see “Event logs” on page 19 and “Diagnostic programs
To perform the checkout procedure, complete the following steps:
1. Is the server part of a cluster?
v No: Go to step 2.
v Yes: Shut down all failing servers that are related to the cluster. Go to step 2.
2. Complete the following steps:
a. Check the power supply LEDs (see “Power-supply LEDs” on page 67).
b. Turn off the server and all external devices.
c. Check all internal and external devices for compatibility at http://www.lenovo.com/support.
d. Check all cables and power cords.
e. Set all display controls to the middle positions.
f. Turn on all external devices.
g. Turn on the server. If the server does not start, see “Troubleshooting tables” on page 50.
h. Check the system-error LED on the operator information panel. If it is flashing, check the LEDs on
the system board (see “System-board LEDs” on page 112).
i. Check for the following results:
v Successful completion of POST (see “POST” on page 21 for more information)
v Successful completion of startup
Diagnosing a problem
Before you contact Lenovo or an approved warranty service provider, follow these procedures in the
order in which they are presented to diagnose a problem with your server:
1. Determine what has changed.
Determine whether any of the following items were added, removed, replaced, or updated before the
problem occurred:
v Device drivers
v Server firmware
v Hardware components
v Software
If possible, return the server to the condition it was in before the problem occurred.
2. Collect data.
Thorough data collection is necessary for diagnosing hardware and software problems.
a. Document error codes and system-board LEDs.
v System error codes: See “POST error codes” on page 21 for information about a specific error
code.
v See “System-board LEDs” on page 112 for the location of the system-board LEDs.
v Software or operating-system error codes: See the documentation for the software or operating
system for information about a specific error code. See the manufacturer’s Web site for
documentation.
b. Collect system data.
Run the Dynamic System Analysis (DSA) diagnostics program to collect information about the
hardware, firmware, software, and operating system. Have this information available when you
contact Lenovo or an approved warranty service provider. See “Diagnostic programs and
messages” on page 68 for the instructions to run the DSA program.
If you need to download the latest version of DSA , go to http://www.lenovo.com/support.
The four problem-resolution procedures are presented in the order in which they are most likely to
solve your problem. Follow these procedures in the order in which they are presented:
a. Check for and apply code updates.
Most problems that appear to be caused by faulty hardware are actually caused by the server
firmware (formerly BIOS firmware), device firmware, or device drivers that are not at the latest
levels.
1) Determine the existing code levels.
In DSA, click Firmware/VPD to view system firmware levels, or click Software to view
operating-system levels.
2) Download and install updates of code that is not at the latest level.
Important: Some cluster solutions require specific code levels or coordinated code updates. If
the device is part of a cluster solution, verify that the latest level of code is supported for the
cluster solution before you update the code.
To display a list of available updates for your server, go to http://www.lenovo.com/support.
When you click an update, an information page is displayed, including a list of the problems
that the update fixes. Review this list for your specific problem; however, even if your problem
is not listed, installing the update might solve the problem.
b. Check for and correct an incorrect configuration.
If the server is incorrectly configured, a system function can fail to work when you enable it; if
you make an incorrect change to the server configuration, a system function that has been enabled
can stop working.
1) Make sure that all installed hardware and software are supported.
See http://www.lenovo.com/support to verify that the server supports the installed operating
system, optional devices, and software levels. If any hardware or software component is not
supported, uninstall it to determine whether it is causing the problem. You must remove
nonsupported hardware before you contact Lenovo or an approved warranty service provider
for support.
2) Make sure that the server, operating system, and software are installed and configured
correctly.
Many configuration problems are caused by loose power or signal cables or incorrectly seated
adapters. You might be able to solve the problem by turning off the server, reconnecting cables,
reseating adapters, and turning the server back on. See “Checkout procedure” on page 15 for
the instructions to perform the checkout procedures.
If the problem is associated with a specific function (for example, if a RAID hard disk drive is
marked offline in the RAID array), see the documentation for the associated controller and
management or controlling software to verify that the controller is correctly configured.
Problem determination information is available for many devices such as RAID and network
adapters.
For problems with operating systems or Lenovo software or devices, complete the following
steps.
Note: Changes are made periodically to the Lenovo Web site. The actual procedure might vary
slightly from what is described in this document.
a) Go to: http://www.lenovo.com/support.
b) From the Select your product list, select Servers and Storage.
c) In the Browse by product window Family: list, select ThinkServer RS210.
d) Click Downloads and drivers .
e) Click User’s guides and manuals to look for related documentation.
c. Check for service bulletins.
Chapter 3. General Checkout17
Lenovo service bulletins document known problems and suggested solutions. To search for service
bulletins, complete the following steps.
1) Go to: http://www.lenovo.com/support.
2) From the Select your product list, select Servers and Storage.
3) In the Browse by product window Family: list, select ThinkServer RS210.
4) Click Downloads and drivers to look for service information.
Note: Changes are made periodically to the Lenovo Web site. The actual procedure might vary
slightly from what is described in this document.
d. Check for and replace defective hardware.
If a hardware component is not operating within specifications, it can cause unpredictable results.
Most hardware failures are reported as error codes in a system or operating-system log. See
“Troubleshooting tables” on page 50 and Chapter 6, “Replacing FRUs,” on page 115 for more
information. Hardware errors are also indicated by LEDs on the system board (see “System-board
LEDs” on page 112 for more information).
Troubleshooting procedures are also provided on the Lenovo Web site. A single problem might
cause multiple symptoms. Follow the diagnostic procedure for the most obvious symptom. If that
procedure does not diagnose the problem, use the procedure for another symptom, if possible. To
locate troubleshooting procedures for your server, complete the following steps.
Note: Changes are made periodically to the Lenovo Web site. The actual procedure might vary
slightly from what is described in this document.
1) Go to: http://www.lenovo.com/support.
2) From the Select your product list, select Servers and Storage.
3) In the Browse by product window Family: list, select ThinkServer RS210.
4) Under Support & downloads, click Troubleshoot.
5) Under Diagnostic, select the troubleshooting procedure for the symptom that you are
observing.
For more troubleshooting information, see Chapter 4, “Diagnostics,” on page 19.
If the problem remains, contact Lenovo or an approved warranty service provider for assistance
with additional problem determination and possible hardware replacement. Be prepared to
provide information about any error codes and collected data.
Undocumented problems
If you have completed the diagnostic procedure and the problem remains, the problem might not have
been previously identified by Lenovo. After you have verified that all code is at the latest level, all
hardware and software configurations are valid, and no LEDs or log entries indicate a hardware
component failure, contact Lenovo or an approved warranty service provider for assistance. Be prepared
to provide information about any error codes and collected data and the problem determination
procedures that you have used.
This chapter describes the diagnostic tools that are available to help you solve problems that might occur
in the server.
Diagnostic tools
The following tools are available to help you diagnose and solve hardware-related problems:
v POST error messages and error logs
The power-on self-test (POST) generates messages to indicate successful test completion or the
detection of a problem. See “POST” on page 21, “Event logs,” and “POST error codes” on page 21 for
more information.
v Troubleshooting tables
These tables list problem symptoms and actions to correct the problems. See “Troubleshooting tables”
on page 50 for more information.
v Dynamic System Analysis (DSA) Preboot diagnostic programs
The DSA Preboot diagnostic programs provide problem isolation, configuration analysis, and error log
collection. The diagnostic programs are the primary method of testing the major components of the
server and are stored in integrated USB memory. The diagnostic programs collect the following
information about the server:
– System configuration
– Network interfaces and settings
– Installed hardware
– Service processor status and configuration
– Vital product data, firmware, and UEFI configuration
– Hard disk drive health
– RAID controller configuration
– Controller and service processor event logs, including the following information:
- System error logs
- Temperature, voltage, and fan speed information
- Self-monitoring Analysis, and Reporting Technology (SMART) data
- Machine check registers
- USB information
- Monitor configuration information
- PCI slot information
The diagnostic programs create a merged log that includes events from all collected logs. The
information is collected into a file that you can send to Lenovo service and support. Additionally, you
can view the server information locally through a generated text report file. You can also copy the log
to removable media and view the log from a Web browser. See “Running the diagnostic programs” on
page 69 for more information.
v Server LEDs
Use the LEDs on the server to diagnose system errors quickly. See “System-board LEDs” on page 112
for more information.
Event logs
Error codes and messages are displayed in the following types of event logs:
v POST event log: This log contains the three most recent error codes and messages that were generated
during POST. You can view the POST event log through the Setup utility.
v System-event log: This log contains messages that were generated during POST and all system status
messages from the service processor. You can view the contents of the system-event log from the Setup
utility for more information.
The system-event log is limited in size. When it is full, new entries will not overwrite existing entries;
therefore, you must periodically clear the system-event log through the Setup utility. When you are
troubleshooting, you might have to clear the system-event log to make the most recent events available
for analysis.
Each system-event log entry is displayed on its own page. Message are listed on the left side of the
screen, and details about the selected message is displayed on the right side of the screen. To move
from one entry to the next, use the Up Arrow (↑) and Down Arrow (↓) keys.
The system-event log indicates an assertion event when an event has occurred. It indicates a
de-assertion event when the event is no longer occurring.
v Integrated management module (IMM) event log: This log contains a filtered subset of all IMM,
POST, and system management interrupt (SMI) events. You can view the IMM event log through the
IMM Web interface and through the Dynamic System Analysis (DSA) program (as the ASM event log).
v DSA log: This log is generated by the Dynamic System Analysis (DSA) program, and it is a
chronologically ordered merge of the system-event log (as the IPMI event log), the IMM chassis-event
log (as the ASM event log), and the operating-system event logs. You can view the DSA log through
the DSA program.
Viewing event logs through the Setup utility
To view the POST event log or system-event log, complete the following steps:
1. Turn on the server.
2. When the prompt <F1> Setup is displayed, press F1. If you have set both a power-on password and
an administrator password, you must type the administrator password to view the event logs.
3. Select System Event Logs and use one of the following procedures:
v To view the POST event log, select POST Event Viewer.
v To view the IMM system-event log, select System Event Log.
Viewing event logs without restarting the server
When the server is not hung and the IMM is connected to a network, methods are available for you to
view one or more event logs without having to restart the server.
You can use the DSA Preboot to view the system event log (as the IPMI event log), the IMM event log (as
the ASM event log), or the merged DSA log. You must restart the server to use DSA Preboot to view
those logs.
You can view the IMM system event log through the Event Log link in the integrated management
module (IMM) Web interface.
Table 2. Methods for viewing event logs
ConditionAction
The server is not hung and is connected to a network.
The server is not hung and is not connected to a
network.
v Use IPMItool to view the system-event log.
Use IPMItool locally to view the system-event log.
Table 2. Methods for viewing event logs (continued)
ConditionAction
The server is hung.
v If DSA Preboot is installed, restart the server and press
F2 to start DSA Preboot and view the event logs.
v If DSA Preboot is not installed, insert the DSA Preboot
CD and restart the server to start DSA Preboot and
view the event logs.
v Alternatively, you can restart the server and press F1
to start the Setup utility and view the POST event log
or system-event log. For more information, see
“Viewing event logs without restarting the server” on
page 20.
Clearing the event logs
To clear the event logs, complete the following steps.
Note: The POST event log is automatically cleared each time the server is restarted.
1. Turn on the server.
2. When the prompt <F1> Setup is displayed, press F1. If you have set both a power-on password and
an administrator password, you must type the administrator password to view the error logs.
3. Use one of the following procedures:
v To clear the IMM system-event log, select System Event Logs --> System Event Log. Select Clear
System Event Log; then, press Enter twice.
POST
When you turn on the server, it performs a series of tests to check the operation of the server components
and some optional devices in the server. This series of tests is called the power-on self-test, or POST.
Note: This server does not use beep codes for server status.
If a power-on password is set, you must type the password and press Enter, when you are prompted, for
POST to run.
If POST detects a problem, an error message is displayed. See “POST error codes” for more information.
POST error codes
The following table describes the POST error codes and suggested actions to correct the detected
problems. These errors can appear as severe, warning, or informational.
Chapter 4. Diagnostics21
v Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved.
v See Chapter 7, “Parts listing, RS210 Types 6531, 6532, 6533, and 6534,” on page 177 to determine which
components are customer replaceable units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
v Go to the Lenovo support Web site at http://www.lenovo.com/support to check for technical information, hints,
tips, and new device drivers or to submit a request for information.
Error codeDescriptionAction
0010002Microprocessor not supported.
0011000Invalid microprocessor type.
0011004Microprocessor failed BIST.
001100AMicrocode updated failed.
0050001DIMM disabled.
1. (Trained service technician only) Reseat the
microprocessor and restart the server.
2. (Trained service technician only) Remove the
microprocessor and install a new microprocessor.
Restart the server. If the error is corrected, the old
microprocessor is bad and must be replaced.
3. Replace the following components one at a time,
in the order shown, restarting the server each
time.
a. (Trained service technician only)
Microprocessor
b. (Trained service technician only) System board
1. Update the server firmware to the latest level (see
“Updating the firmware” on page 212).
2. (Trained service technician only) Remove and
replace the affected microprocessor (error LED is
lit) with a supported type (see “Installing the
microprocessor” on page 141).
1. Update the server firmware to the latest level (see
“Updating the firmware” on page 212).
2. (Trained service technician only) Reseat the
microprocessor.
3. Replace the following components one at a time,
in the order shown, restarting the server each
time:
a. (Trained service technician only)
Microprocessor
b. (Trained service technician only) System board
1. Update the server firmware to the latest level (see
“Updating the firmware” on page 212).
2. (Trained service technician only) Replace the
microprocessor.
1. If the server fails the POST memory test, reseat
the DIMMs.
2. Remove and replace any DIMM for which the
associated error LED is lit (see “Removing a
memory module” on page 124 and “Installing a
memory module” on page 125).