Xserve - ServiceMan [Early2009]

7/27/2019 Xserve - ServiceMan [Early2009]

1/167

Apple Technician Guide

Xserve (Early 2009)Updated: 2011-05-05


2/167

Apple Inc.

2011 Apple Inc. All rights reserved.

Under the copyright laws, this document may not be copied, in whole or in part, without thewritten consent of Apple.

Every eort has been made to ensure that the information in this document is accurate. Apple

is not responsible for printing or clerical errors.

Apple1 Innite LoopCupertino, CA 95014-2084USA+ 1 408 996 1010www.apple.com

Apple, the Apple logo, Mac, and Macintosh are trademarks of Apple Inc., registered in the U.S.and other countries.


3/167

Xserve (Early 2009)

Contents

Basics

Overview 9Front View 10Rear View 10Serial Number Location 11Hot-Pluggable SATA or SAS Drives 12How to Identify Single- and Dual-Processor Congurations 13

Troubleshooting

General Troubleshooting 15Update System Software 15Emerging Issues 15Hardware vs. Software 15Xserve Firmware Updates 16Memory Conguration 16Block Diagram 21

Diagnostic LEDs 22Symptom Charts 31

Startup and Power Issues 31No Power / Dead Unit 31Burnt Smell or Odor 34Wont Start Up / No Video/ LED On 36Wont Start Up / No Video/ Activity LEDs Flashing 38Intermittent Shutdown 39Kernel Panic/System Crashes 41Uncategorized Symptom 43

Mass Storage 44Apple Drive Module Read/Write Issue 44RAID Battery Not Charging 58Uncategorized Symptom 60

Input/Output Devices 61Rear USB Port Does Not Recognize Known Devices 61Front USB Port Does Not Recognize Known Devices 62FireWire Port Does Not Recognize Known Devices 63PCI-E Expansion Card/Slot Not Recognized 64


4/167

Communications 67Ethernet Port/Device Issues 67

Video 70Video Distortion 70No Video 71

Mechanical Issues: Thermal and Enclosure 72Failed or Fast Fans 72

Take Apart

General Information 76Orientation 76

Tools 76How to Identify Single- and Dual-Processor Congurations 76Mounting in a Rack 76Icon Legend 77

Note on Illustrations 77

Apple Drive Module 78Removal 79Replacement 80

Power Supply 81Removal 82Replacement 82

Power Supply Blank 83Removal 84

Replacement 84

Top Cover 85Removal 86Replace 86

Solid State Drive 87Removal 88Replacement 88

Solid State Drive Cable 89Removal 90Replacement 90

Solid State Drive Carrier 91Removal 92Replacement 92

Memory 93Removal 94


5/167

Memory Slot Utility 94Replacement 95Memory Conguration 95

PCI-E Riser Cards 96Removal 97

Replacement 97PCI-E Expansion Cards 98

Removal 99Replacement 100

Optical Drive 101Removal 102Replacement 103

Airow Duct 104Removal 105

Replacement 106Fan Array 107


Battery 109Removal 110Replacement 110

Front Panel Cable 111Removal 112

Replacement 112

Backplane-to-Logic Board I/O Cable 113Removal 114Replacement 114

Optical Drive Cable 116Removal 117Replacement 118

Locking Mechanism Rod 119Removal 120

Replacement 120

Front Bezel Brackets 121Removal 122Replacement 122

Front Bezel Assembly 123Removal 124


6/167

Replacement 125

Front Panel Buttons 126Removal 127Replacement 127

Light Pipe 128Removal 129Replacement 129

Front Panel Board 130Removal 131Replacement 131

Drive Interconnect Backplane 132Removal 133Replacement 133

Xserve RAID Card 135Removal 136Replacement 137

Power Distribution Board 138Removal 139Replacement 139

Power Distribution Board Cable 140Removal 141Replacement 141

Xserve RAID Card Battery 142Removal 143Replacement 143

Processor Heat Sink 144Removal 145Replacement 147

Processor 148Removal 149Replacement 150

Video Mezzanine Card 152Removal 153Replacement 153

Logic Board 154Removal 155Replacement 157

Rear ID Button 158


7/167


ID Tab 160Removal 161Replacement 161

Enclosure 162Removal 163Replacement 163

Views

Exploded View 165

Feedback 167


8/167



BasicsXserve (Early 2009)


9/167

Xserve (Early 2009) Basics Overview 92011-05-05

Overview

The Xserve (Early 2009) rack-optimized server features single or dual Quad-Core Intel XeonNehalem processors, integrated memory controllers featuring up to 12 DIMMs of 1066MHzDDR3 ECC RAM, three hot-plug drive bays supporting SATA or SAS Apple Drive Modules,support for a Solid-State Drive (SSD) boot drive, dual x16 PCI Express 2.0 slots, NVIDIA GeForceGT 120 graphics subsystem and integrated lights-out management.

Identifying FeaturesThe main features and service dierences include: single and dual Intel Xeon Nehalem processors 6 or 12 DIMM slots depending on processor conguration Solid-State Drive Support Mini DisplayPort connector on rear panel
mailto:[email protected]?subject=Xserve%20(Early%202009)%20Apple%20Technician%20Guide:


10/167


Drive moduleactivity light

Drive modulestatus light

Optical driveSystem identifierbutton/light

Enclosure lockand status light

USB 2.0port

On/standby buttonand light

Drive modulebays (3)

Ethernet link light(Port 1)

Ethernet link light(Port 2)

System activitylights

Rear View

System information tag(pullout tab)System identifierbutton/light Power supplybay 2Power supplybay 1FireWire 800ports (2)

Ethernetport 2

Ethernetport 1

Expansionslot 1

Expansionslot 2

Mini DisplayPortSerial consoleport

USB 2.0 ports (2)

Front View


11/167


12/167


Hot-Pluggable SATA or SAS Drives

The server includes three hard drive bays at the front of the Xserve. All bays support Applequalied hot-pluggable Apple Serial ATA (SATA) or Serial Attached SCSI (SAS) drive modules.Xserve drive bays support qualied Apple Drive Modules with Apple qualied hard drivesand rmware only. Drive bays not congured with an Apple Drive Module ship with a non-

functional blank drive carrier which do not support third-party hard drive installation.

Drive bays are numbered 1-3, beginning with the far left bay. The drive installed in bay 1 is theboot drive and should have the operating system installed on it. Xserves congured with aSolid-State Drive (SSD) will contain the Mac OS X Server operating system and function as theboot drive.

You can replace or install hard drives while the Xserve is running; you do not need toshutdown or open the Xserve rst, but you may need to dismount the drive from the XserveOS beforehand. A status light on the front of each drive indicates when it is safe to remove thedrive without losing data. For more information, see Apple Drive Module in the Take Apartchapter.

Solid-State Drive

The server may include an optional Solid-State Drive. The drive contains the Mac OS X Server

operating system as the boot drive for the Xserve.


13/167


Power Supply Redundancy

The Xserve (Early 2009) supports up to two power supply modules for redundancy. There aretwo power supply bays in the rear of the enclosure. You can replace or install a power supplyfrom the back panel without removing the Xserve from the rack. If the Xserve has two powersupplies, they are hot-swappable; the Xserve will continue to operate using only one supplywhile the second is removed. For more information about removing or installing power supply

modules, see Power Supply in the Take Apart chapter.

How to Identify Single- and Dual-Processor Congurations

To identify the conguration of an Xserve (Early 2009) computer, check the code on thecomputers ID Tab, which is located on the computers back panel. See Serial NumberLocation.

There are three options for identifying single and dual processor congurations: Quad-Core Xserve (Early 2009): Single processor logic board with 6DIMM slots, and one

large heat sink 8-Core Xserve (Early 2009): Dual processor logic board with 12 DIMM slots, and two large

heat sinks: Quad-Core Xserve (Early 2009): Single processor logic board, 12 DIMM slots and one large

heat sink. This option is present only when a single-processor logic board has previouslybeen replaced via the Xserve service parts kit.
http://-/?-http://-/?-http://-/?-http://-/?-mailto:[email protected]?subject=Xserve%20(Early%202009)%20Apple%20Technician%20Guide:


14/167



TroubleshootingXserve (Early 2009)


15/167

Xserve (Early 2009) General Troubleshooting Update System Software 152011-05-05

General Troubleshooting

Update System Software

Important: Whenever possible before beginning troubleshooting, ensure the latest softwareand rmware updates have been applied.

Troubleshooting Theory

For general information on troubleshooting theory, refer to:

http://service.info.apple.com/service_training/en/006/troubleshoot/index.php?page=intro

Emerging Issues

For the latest on troubleshooting issues, refer to:

http://support.apple.com/kb/index?page=search&q=khot%20Xserve%20Emerging%20Issue

Hardware vs. Software

For information on how to isolate a hardware issue from a software issue, refer to:

http://support.apple.com/kb/TS1388

TS1394Mac OS X: Troubleshooting installation and software updates

HT2956Troubleshooting Mac OS X installation from CD or DVD

For information on how to troubleshoot a software issue, refer to:

HT1199Mac OS X: How to troubleshoot a software issue

HT1219Xserve, Xserve RAID: Apple Drive Module (ADM) compatibility
http://service.info.apple.com/service_training/en/006/troubleshoot/index.php?page=introhttp://support.apple.com/kb/index?page=search&q=khot%20Xserve%20Emerging%20Issuehttp://support.apple.com/kb/index?page=search&q=khot%20Xserve%20Emerging%20Issuehttp://support.apple.com/kb/TS1388?viewlocale=en_UShttp://support.apple.com/kb/TS1394http://support.apple.com/kb/TS1394http://support.apple.com/kb/HT2956http://support.apple.com/kb/HT2956http://support.apple.com/kb/HT1199http://support.apple.com/kb/HT1199http://support.apple.com/kb/HT1219http://support.apple.com/kb/HT1219http://support.apple.com/kb/HT1219http://support.apple.com/kb/HT1219http://support.apple.com/kb/HT1199http://support.apple.com/kb/HT1199http://support.apple.com/kb/HT2956http://support.apple.com/kb/HT2956http://support.apple.com/kb/TS1394http://support.apple.com/kb/TS1394http://support.apple.com/kb/TS1388?viewlocale=en_UShttp://support.apple.com/kb/index?page=search&q=khot%20Xserve%20Emerging%20Issuehttp://support.apple.com/kb/index?page=search&q=khot%20Xserve%20Emerging%20Issuehttp://service.info.apple.com/service_training/en/006/troubleshoot/index.php?page=intromailto:[email protected]?subject=Xserve%20(Early%202009)%20Apple%20Technician%20Guide:


16/167

Xserve (Early 2009) General Troubleshooting Xserve Firmware Updates 162011-05-05

Xserve Firmware Updates

Firmware is the name given to software that is written into memory circuits, such as ashmemory, that will hold the software code indenitely, even when power is removed from thehardware. Firmware on Intel Mac computers is designed to be updated if necessary through asoftware update.

EFI and SMC rmware is stored on the Xserve (Early 2009) backplane board. EFI rmwareupdates update the Boot ROM, and SMC updates update the System Management Controllerrmware. The SMC manages fans and other environmental parameters that are independent ofthe Boot ROM.

Firmware symptoms can be easily mistaken for hardware issues (e.g., overheating issues, fannoise issues, etc.). Always check both EFI and SMC rmware versions and update if necessarybefore replacing any hardware components.

The following lists describe the type of symptoms that may be resolved by updating the EFIand SMC rmware.

Symptoms that may be resolved by updating EFI rmware: Cannot eject media (various conditions) No video on start up Not waking or sleeping when expected Bad media taking too long to eject (including holding mouse button down at startup taking

minutes to eject)

Symptoms that may be resolved by updating SMC rmware: Fan related behavior (excessive speed or noise) Loud audible clicking from some fans

Thermal shut down or warnings Diagnostics reporting failures Sleep/wake issues Intermittent shut down SMC causes bad/missing ambient sensor to cause the computer to go to sleep Hangs, black screen on restart from Windows

Please follow the steps outlined in KnowledgeBase article HT2013, About Firmware Updatesfor Xserve, to perform an EFI and/or SMC rmware update. Information about rmwareversions for Intel Macs can be found in KnowledgeBase article HT1237, Mac OS X: FirmwareUpdates for Intel-based Macs.

Memory Conguration

Xserve (Early 2009) comes with a minimum of 3 GB of 1066MHz DDR3 ECC memory, installed asthree 1 GB unbuered dual inline memory modules (UDIMMs).
http://support.apple.com/kb/HT2013http://support.apple.com/kb/HT2013http://support.apple.com/kb/HT1237http://support.apple.com/kb/HT1237http://support.apple.com/kb/HT1237http://support.apple.com/kb/HT1237http://support.apple.com/kb/HT2013http://support.apple.com/kb/HT2013mailto:[email protected]?subject=Xserve%20(Early%202009)%20Apple%20Technician%20Guide:


17/167

Xserve (Early 2009) General Troubleshooting Memory Conguration 172011-05-05

DIMMs must t these specications: PC3-8500,1066 MHz, DDR3 SDRAM UDIMMs 72-bit wide, 240-pin modules 36 memory ICs maximum per UDIMM Error-correcting code (ECC)

For proper operation of Xserve (Early 2009) computers, Apple recommends using only Apple-approved DIMMs. Refer to GSX for Apple DIMM service part numbers. Memory from olderXserve computers is not compatible with Xserve (Early 2009).

Single Processor

Single-processor (quad-core) computers have six memory slots. You can install 1 GB, 2 GB or4GB DIMMs for a total of up to 24 GB of memory.

You can install dierent size DIMMs in Xserve (Early 2009). However, for best performance,Apple recommends you install equal-size DIMMs (all 1, 2 or 4GB) lling the slots in the order

listed in this table.

If you have Fill these slots

Three DIMMs A1, A2, and A3

Four DIMMs A1, A2, A3, and A4

Five DIMMs A1, A2, A3, A4, and A5

Six DIMMs A1, A2, A3, A4, A5, and A6

See also Memory Slot Utility below.


18/167


Dual Processor

Dual-processor (eight-core) computers have twelve memory slots. You can install 1 GB, 2 GB, or4 GB DIMMs for a total of up to 48 GB of memory.

You can install dierent size DIMMs. in Xserve (Early 2009) However, for best performance, Applerecommends you install equal-size DIMMs (all 1, 2, or 4 GB) lling the slots in the order listed inthis table.

If you have Fill in these slots

Three DIMMs A1, A2, and A3

Four DIMMs A1, A2, and B1, B2

Five DIMMs A1, A2, A3 and B1, B2

Six DIMMs A1, A2, A3 and B1, B2, B3

Seven DIMMs A1, A2, A3, A4 and B1, B2, B3

Eight DIMMs A1, A2, A3, A4 and B1, B2, B3, B4Nine DIMMs A1, A2, A3, A4, A5 and B1, B2, B3, B4

Ten DIMMs A1, A2, A3, A4, A5, A6 and B1, B2, B3, B4

Eleven DIMMs A1, A2, A3, A4, A5, A6 and B1, B2, B3, B4, B5

Twelve DIMMs A1, A2, A3, A4, A5, A6 and B1, B2, B3, B4, B5, B6

See also Memory Slot Utility below.


19/167


Memory Slot Utility

If you install dierent size DIMMs in single-processor or dual-processor computers, follow theorder in the tables above. If the DIMM conguration you install doesnt provide optimizedperformance, the Memory Slot Utility will appear on screen and recommend an improvedconguration. To use the Memory Slot Utility again, go to /System/Library/Core Services.

Example of Memory Slot Utility Screen for Single-Processor Computer


20/167


Example of Memory Slot Utility Screen for Dual-Processor Computer


21/167

Xserve (Early 2009) General Troubleshooting Block Diagram 212011-05-05

Block Diagram


22/167

Xserve (Early 2009) General Troubleshooting Diagnostic LEDs 222011-05-05

Diagnostic LEDs

Logic Board Diagnostic LEDs

The Xserve (Early 2009) logic board includes a set of LEDs to help service providerstroubleshoot the computer. The LEDs are located on the logic board below the DIMMconnectors, at the rear of the unit, to the left side of the unit (looking from the back), and onthe Drive Interconnect Backplane or Xserve RAID Card.

Some tips:

You must remove the unit from its rack and place it on a sold surface with its cover removedin order to view these LEDs. Most internal diagnostic LEDs are only enabled to come on whenthe cover is removed (memory DIMM LEDs remain ON even with the cover in place).

Do not attempt to troubleshoot the unit solely by these LEDs alone. Use this information toguide your troubleshooting, not lead it.

If a specic error condition exists, there should be corresponding LED evidence to help verifyand isolate the issue. However, it is not possible to deduce a fault or isolate a specic symptomsolely by examining these LEDs out of context.


23/167


1. System State LEDs

Use the following table to interpret the LEDs.

Location Name Color Nominal Indicates

S0 Power ON Green On; o when

in standbymode

System is

running

S3 Sleep Green O, on whenXserve is insleep mode

System is insleep mode

S5 Standby Green O; on whenXserve is instandby

Standbymode,illuminateswhen ACpower isattached


24/167


2. CPU Error LEDs

Use the following table to interpret the LEDs.

Location Color Nominal Indicates

CPU_PWRGD Green O; on to indicate

hardware power haspassed

Power chain in hardware

RSM_RST Yellow, Red O Fault preventing CPU fromexecuting instructions

SYS_PWRGD Green On at power-on toindicate power haspassed

Power chain in hardware

PLT_RST Red O; on Yellow atpower on

Platform reset

CPU B OVERTEMP Red O; on if CPU B coreexceeds normaltemperature

Temperature of CPU B corestatus

IOH OVERTEMP Red O; on if IOH exceedsnormal temperature

Temperature of IOH status

CPU A OVERTEMP Red O; on if CPU A coreexceeds normaltemperature

Temperature of CPU A corestatus

MXM OVERTEMP Red O; on if MXM videocard exceeds normaltemperature

Temperature of MXM videocard status


25/167


Platform Reset

Normally remains on during standby. This LED ashes on (yellow) briey at power-on. LEDshould turn o as system powers up and begins to execute instructions.Overtemp LEDs

Normally o. These LEDs come on if an error occurs.

If LED is solidly on, it may indicate a processor over-temperature condition. Initial processorover-temperature can cause symptoms such as sluggish computer performance. Chronicprocessor over-temperature can cause the computer to hang completely.

Troubleshooting: Verify proper heatsink installation. Verify all fans are operating properly, especially the fan array. If both overtemp LEDs come on immediately when the computer is turned on, a faulty

power supply could be one cause of this behavior. Replace power supply. Try swapping CPU A and CPU B locations. If the CPU Error LED follows the CPU, replace that

CPU.

3. EFI POST (Power On Self Test) LEDs

This group of eight LEDs are arranged into two sets of four LEDs, representing a binary codethat only has any signicance during the short time between power-on and the unit begins toboot the OS, while the CPU is executing EFI code only. At no other time should these LEDs beused or interpreted to mean anything meaningful.

The code is more easily described as two Hexadecimal digits ranging from $00 to $FF, to make

it easier to list and compare during troubleshooting. Each ONE represents an LED that is ON,and each ZERO represents an LED that is OFF

Normal power-up LED sequence:

The sequence of codes below is typical in the rst few seconds of a functioning units bootcycle, immediately following power-on, during the EFI phase of startup.

If your system is not booting you should check these LEDs closely to verify the sequence ofcodes has been executed in addition to your normal troubleshooting steps. Each code will onlyremain ON GREEN for a split-second each. The entire sequence takes only a few seconds toprogress through.

To see this sequence, power-on the unit (use the remote power on/o button on the logicboard) while holding down the option key on an attached USB keyboard, to invoke the EFIstartup manager and prevent the unit from leaving EFI and booting into any OS. Do this as youwatch these LEDs as they progress through the following sequence:

Begin (power-on)


26/167


$Bx = 1 0 1 1 X X X X = All $Bx codes below are memory init codes (x may be any code 0 - F)

$BF = 1 0 0 1 1 1 1 1 = If the unit does not progress past any $Bx memory init codes, this couldindicate a memory issue regardless of whether DIMM diagnostic error LEDs are ON or not.

$12 = 0 0 0 1 0 0 1 0 = After memory initialization has successfully completed

$51 = 0 1 0 1 0 0 0 1 = Video driver enabled beyond this point. Attached display should bedisplaying an image now. If not, this may indicate a graphics card issue.

$F9 = 1 1 1 1 1 0 0 1 = EFI nished and passed on control to OS boot loader

4. CPU Voltage LEDs

This group of LEDs will normally FLASH RED briey during power-on, then should normallyremain ON solidly GREEN when all voltage regulators are functioning properly to providevoltages to CPU A and CPU B, as well as IOH.

If any of these LEDs remain ON RED, this indicates that the corresponding voltage regulator isenabled but not providing any voltage output.

In single processor units the LED group for the second processor are not present.


27/167


5 & 6. Memory Diagnostic LEDs (A1 - A6 and B1 - B6)

This group of LEDs will normally remain OFF during power-on and throughout normaloperation. If any of these LEDs come ON RED, this indicates that the corresponding DIMM (orits slot) may be faulty. To verify whether the fault lies with the DIMM or the slot, power downthe unit and move the DIMM to another slot. If the DIMM is faulty, the LED adjacent to its new

slot should come ON RED when power is reapplied. If a known-good DIMM is installed in thesuspect slot and the LED adjacent to this slot should come ON RED , this may indicate a faultyDIMM slot on the logic board.

How to Troubleshoot Memory LEDs

1. Remove and reseat DIMM

2. Restart computer. If associated LED is no longer illuminated, issue is resolved

3. If associated LED remains illuminated, replace DIMM with new DIMM

4. Restart computer and verify LED is no longer illuminated


28/167


7. Reset Buttons

System Management Controller (SMC) Reset

The System Management Controller (SMC) is a chip on the logic board that controls all powerfunctions for the Xserve. If the Xserve is experiencing any power issue, resetting the SMC mayresolve it. The SMC controls several functions, including:

Telling the Xserve when to turn on, turn o, sleep, wake, idle, and so forth

Handling system resets from various commands

Controlling the fans

It is also recommended that the SMC be reset on any new logic board after it is installed as partof a repair.

Note that resetting the SMC does not reset the PRAM. Resetting the SMC will not resolve issuesin which the Xserve is unresponsivein these situations, restarting the Xserve will generally

suce.

If the Xserve isnt responding, perform these steps one at a time, in the following order, untilthe issue has been resolved:

1. Force Quit (Option-Command-Escape)

2. Restart (Control-Command-Power)

3. Force Shut Down (press the power button for 10 seconds)

4. Remove the Xserve from the rack (if applicable)

5. Remove the Top Case

6. Press the SMC Reset button on the logic board

Resetting the SMC can resolve some Xserve issues such as not starting up, not displaying video,sleep issues, fan noise issues, and so forth. If the Xserve still exhibits these types of issues afteryouve restarted the Xserve, try resetting the SMC. There are two ways to reset the SMC on theXserve.

System Management Control (SMC) Reset in Rack

1. Shut Down the Xserve, either locally or using remote commands (or if the Xserve is notresponding, hold the power button until it turns o).

2. Unplug the AC power cord.

3. Wait at least 15 seconds.

4. Plug the power cord back in, making sure the power button is not being pressed at the time.


29/167


5. Press the power button to start up the Xserve.

Power ON / OFF Button

Behaves exactly like the front panel power button, and can be used as an alternate way to turnthe unit on and o if needed.

Reset Buttons

When pressed, resets CPUs regardless of what is currently running. This reset overrides allsoftware processes and restarts the system. Use with caution as this form of reset may corruptsoftware or les on a drive.

Drive Interconnect Backplane LEDs

Note: The following information describes the diagnostic LEDs present on the interconnectbackplane.

This group of eight LEDs are arranged into two sets of four LEDs, representing informationabout the SATA / SAS communication between the drive controller channels on the driveinterconnect backplane and the drive modules themselves. The optional SSD drive does nothave a representative LED on this board.

There is also a heartbeat LED on this board which starts ashing ON GREEN and OFF when EFIloads immediately after power-on and continues to ash ON and OFF during normal operation.

The rst group of four LEDs indicates activity for the four I/O channels corresponding to thethree drive bays. Since there are only three drive bays, the fourth I/O channel and LED are notused and should remain OFF during normal operation.

The second group of four LEDs indicates that the controller has recognized that a drivemodule is present and connected. These LEDs are normally solidly ON GREEN when no driveis present, and turn OFF when a drive module has been inserted into the corresponding drive


30/167


bay and the controller has recognized this event. The LED will turn ON GREEN again when thecorresponding drive module has been removed from its bay.

Since there are only three drive bays, the fourth I/O channel and LED are not used and shouldremain ON GREEN during normal operation.

When you power-on the system, you should see the following activity sequence on these LEDs:

1. The entire group of eight LEDs should come ON solid GREEN when power is applied andremain on for a few seconds.

2. The heartbeat LED begins ashing when EFI loads in the rst few second after power-on.The rst group of four activity LEDs should now turn OFF. The second group of four drivepresent LEDs should remain on for a few more seconds.

3. The second group of four drive present LEDs should each turn OFF as the controller scansand recognizes each connected drive module in turn, from bay 1 to bay 3 in order. Thefourth LED should remain ON since no drive is present on the fourth I/O channel.

4. Beyond this point, the only LEDs that should be ashing are among the rst group of fourdrive activity LEDs, to indicate drive activity between a corresponding drive module, suchas the boot drive module booting the OS, and the drive controller.


31/167

Xserve (Early 2009) Symptom Charts 312011-05-05

Symptom Charts

Follow the steps in the order indicated below. If an action resolves the issue, retest the systemto verify. If the issue persists after retesting, return to step 1.

Startup and Power Issues

No Power / Dead Unit

Unlikely cause: Optical drive, hard drive(s), fan array, memory, RAID battery

Quick Check

Symptom Quick Check

No Power / Dead Unit No fan or drive module spin No LED activity

1. Check the front panel on/standby light. Thislight should be solid white when the Xserve isrunning, and o when the Xserve is in standbymode. If its ashing white, the Xserve is in sleepmode.

2. Verify the power outlet and power cord areknown good and that AC power is present.

3. Check the power supply status light next to thepower cord connector on the rear of the Xserve(check the LEDs for both supplies in a two-power-supply conguration).

4. Solid green indicates power is available andXserve should be on.

5. Blinking green indicates AC power is availablebut power to the Xserve components from thissupply is on standby (usually because the Xserveis turned o).

6. Red indicates either no AC power is available tothis supply from the power cord or this powersupply has failed.

7. Disconnect all external cables such as network,peripheral, and expansion card connections, andpress the power button again.


32/167


33/167

Xserve (Early 2009) Symptom Charts Startup and Power Issues 332011-05-05

10. Verify all cable connectionsto the logic board and driveinterconnect backplane aresecure.

Yes Go to Step 11

No Ensure all cable connectionsto the logic board and driveinterconnect backplane aresecure. Go to Step 11

11. Replace the power supply.Verify that the Xserve powerson.

Yes Issue resolved. P01

No Go to Step 12

12. Replace the power distributionboard. Verify that the Xservepowers on.

Yes Issue resolved. M01

No Go to Step 13

13. Replace the front panel boardcable. Verify that the Xserve

powers on.

Yes Issue resolved. X03

No Go to Step 1414. Replace the front panel board.

Verify that the Xserve powerson.


No Go to Step 15

15. Replace the drive interconnectbackplane. Verify that theXserve powers on.


No Go to Step 16

16. Reseat both processors. Verifythat the Xserve powers on.

Yes Issue resolved.

No Go to Step 17

17. Replace both processors. Verifythat the Xserve powers on.


No Reinstall original processors.Replace the logic board.

M08


34/167


35/167


Deep Dive

Check Result Action Code

1. Verify source of the odor ieforeign contaminant such asuid ingress, dust, hair etc

Yes Cleanup foreign contaminant,replace any aected modules.Foreign contaminants are notcovered by Apple warranties

P08

No Go to step 2

2. Inspect PCBs and componentsfor indications of a thermalevent

Yes Replace any aected modules P08

No Go to step 3

3. Verify System is functioningcorrectly

Yes Some odors may be presentwhen operating normally.Refer to http://support.apple.com/kb/TA22044

No Please refer to best relatedtroubleshooting section.
http://support.apple.com/kb/TA22044http://support.apple.com/kb/TA22044http://support.apple.com/kb/TA22044http://support.apple.com/kb/TA22044mailto:[email protected]?subject=Xserve%20(Early%202009)%20Apple%20Technician%20Guide:


36/167


Wont Start Up / No Video/ LED On

Unlikely cause: Fan array, front panel board, memory, optical drive, power distribution board,power supply, RAID battery

Quick CheckSymptom Quick Check Wont Startup / No Video / LEDOn Xserve begins to power up but

does not boot Fan array and hard drive are

spinning Power LED is illuminated No activity lights No video on connected

external display

1. Conrm the system conguration supportsan external display. Not all congurations do,although the mini DisplayPort connector on therear of the unit is present regardless.

2. Verify that the rear System Identier buttonon the back of the logic board aligns with theopening in the chassis back panel. If it does not,realign the logic board.

3. Conrm at least one known good andcompatible memory DIMM is installed in thesystem.

4. After power-on, verify front panel power light issolidly on, and not ashing any error sequencesindicating a memory failure.

5. Connect known-good external bootable device,keyboard, and mouse, then press Option keyduring startup and select external startup deviceto bring up system for diagnostics. Run completeAXD diagnostics.

Deep Dive


1. Press the SMC Reset buttonon the logic board to resetthe SMC. Verify Xserve bootsfrom known good externalbootable device

Yes Issue resolved.

No Go to Step 2

2. Check internal diagnostic LEDs.Go to diagnostic LED section

for more information. VerifyXserve boots from knowngood external bootable device.

Yes Issue resolved.

No Go to Step 3

3. Remove all three drivemodules and press the powerbutton. Verify Xserve bootsfrom known good externalbootable device.

Yes Suspect drive module(s) ascause. Go to Step 4

No Go to Step 5


37/167


4. Reconnect each one at a time,verifying unit operation asdrive module is reinstalled.Verify Xserve boots fromknown good external bootabledevice.

Yes Repeat Step 4 until the drivemodule is isolated.

No Failed drive module. Replacedrive module. Issue resolved.

H02

5. Remove both internal PCIriser cards and any installedexpansion cards and press thepower button. Verify Xserveboots from known goodexternal bootable device.

Yes Suspect PCI card(s) and/orriser card(s) as cause. Go toStep 6

No Go to Step 7

6. Reconnect each one at a time,verifying unit operation ascard is reinstalled. Verify Xserveboots from known goodexternal bootable device.

Yes Repeat Step 6 until the card isisolated.

No Failed card. Replace card.Issue resolved.

M17

7. Disconnect backplane-to-logicboard cable. Verify Xserveboots from known goodexternal bootable device.

Yes Go to Step 8

No Go to Step 9

8. Replace drive interconnectbackplane. Reconnectbackplane-to-logic board

cable. Verify Xserve boots fromknown good external bootabledevice.


No Reinstall original driveinterconnect backplane. Go toStep 9

9. Replace backplane-to-logicboard cable. Verify Xserveboots from known goodexternal bootable device.


No Go to Step 10

10. Reseat both processors. VerifyXserve boots from knowngood external bootable device.

Yes Issue resolved. Go to Step 13

No Go to Step 11

11. Replace both processors. VerifyXserve boots from knowngood external bootable device.

Yes Issue resolved. Go to Step 13 M02

No Reinstall original processors.Go to Step 12

12. Replace logic board VerifyXserve boots from knowngood external bootable device.

Yes Issue resolved. Go to Step 13 M02

No Multiple module failure.Return to step 7.


38/167


13. Reinstall users original startupdrive module. Verify Xserveboots from users originalstartup drive module.

Yes Issue resolved.

No Replace users original startupdrive module. Start upfrom Server Install Disc andinstall server OS onto users

replacement startup drivemodule. Verify Xserve bootsfrom replacement startupdrive module. Issue resolved.

H02

Wont Start Up / No Video/ Activity LEDs Flashing

Quick Check

Symptom Quick Check

Wont Boot / No Video / ActivityLEDs Flashing In Sequence Xserve begins to power up but

does not boot Fan array and hard drive are

spinning Power LED is illuminated Top row of activity lights ash

in sequence left to right andthen right to left

No video on external display

1. Press the System Identier button a few times. Ifthe bottom row of activity lights illuminate fromright to left each time you press this button, thenits likely that the System Identier light is stuckin on either the front or rear panel.

2. Verify that the rear System Identier buttonon the back of the logic board aligns with theopening in the chassis back panel. Also checkthe front panel System Identier button. If eitherbutton appears to be stuck in, follow the steps inthe deep-dive section of this symptom.

3. Connect known-good external bootable device,keyboard, and mouse, then press Option keyduring startup and select external startupdevice to bring up system for diagnostics. Runcomplete AXD diagnostics.

Deep Dive


1. Remove the front bezel andmake sure the front SystemIdentier button is not stuck.Reseat the button if necessary.Verify Xserve boots fromusers original startup drivemodule.

Yes Issue resolved.

No Go to Step 2


39/167


2. Reseat the front panel boardand its cable connectors.Verify Xserve boots from usersoriginal startup drive module.

Yes Issue resolved.

No Go to Step 3

3. Replace front panel board.Verify Xserve boots from usersoriginal startup drive module.


No Go to Step 4

4. Reinstall original front panelboard. Remove and re-seatlogic board to enure rear panelSystem Identier button is notstuck in. Verify Xserve bootsfrom users original startupdrive module.

Yes Issue resolved.

No Replace logic board. M02

Intermittent ShutdownUnlikely cause: hard drive, optical drive

Quick Check

Symptom Quick Check

Shutdown After Startup System shuts down almost

immediately after startup

Intermittent Shutdown System shuts down during

normal use

1. Make sure the power cord is plugged in rmly.

2. Check that the power source is turned on andthe correct voltage is present.

3. Make sure the air vents are clear.4. Replace the power cord.

5. Connect keyboard and start up the system withshift key down for safe mode.

6. Start up from known-good bootable device.

7. Check system.log info for shutdown cause.

8. Run AXD for sensors + thermal test.

9. Verify that the rear System Identier buttonon the back of the logic board aligns with theopening in the chassis back panel. If it does not,

realign the logic board.


40/167


Deep Dive


1. Press the SMC Reset buttonon the logic board to reset theSMC. Verify Xserve no longershuts down after starting up.

Yes Issue resolved.

No Go to Step 2

2. Check internal diagnostic LEDs.Go to diagnostic LED sectionfor more information. Followrecommendations therein.Verify Xserve no longer shutsdown after starting up.

Yes Issue resolved.

No Go to Step 3

3. Check that the fan arrayconnector is connected andthe fan array is operational.

Verify Xserve no longer shutsdown after starting up.

Yes Go to Step 4

No Reconnect or replace fanarray as required. X18

4. Verify that the heat sink isproperly attached to theprocessor. Verify Xserve nolonger shuts down afterstarting up.

Yes Go to Step 5

No Properly reattach heat sink toprocessor. Go to Step 5

5. Verify that all thermal sensorcables are properly connected.Verify Xserve no longer shutsdown after starting up.

Yes Go to Step 6

No Properly reconnect all thermal

sensor cables. Issue Resolved.

X18

6. Replace the power supply.Verify Xserve no longer shutsdown after starting up.

Yes Issue resolved. P02

No Reinstall original powersupply. Go to Step 7

7. Reseat both processors. VerifyXserve no longer shuts downafter starting up.

Yes Issue resolved.

No Go to Step 8

8. Replace both processors. VerifyXserve no longer shuts downafter starting up.


No Reinstall original processors.

Replace the logic board.

M08


41/167


Kernel Panic/System Crashes

Quick CheckSymptom Quick Check

Memory Issues/Kernel panic andfreezes Unit has kernel panic or freezes

on startup or when operating Memory not recognized in

System Proler or in MemorySlot Utility

Fans running fast

1. After power ON, verify Front Panel power LEDilluminated, and not ashing any error sequencesindicating a memory failure.

2. Verify with known good and compatible memoryDIMMs. Memory from older computers is notcompatible and cannot be used.

3. Ensure the compatible memory is lled in thecorrect order in the memory slots. If memoryis not congured for the best performance theMemory Slot Utility will appear on screenand recommend an improved conguration.

To use the utility again go to /System/Library/CoreServices/Memory Slot Utility

4. Conrm total memory in System Proler.

5. Startup with Shift key down for safe mode boot.Check panic.log info for crash cause.

6. Startup from original install media, or knowngood boot device with compatible Mac OS X.

7. Run all AXD diagnostic tests.

Deep Dive


1. Press the SMC Reset buttonon the logic board to reset theSMC. Verify Xserve no longershuts down after starting up

Yes Issue resolved.

No Go to Step 2

2. Check internal diagnostic LEDs.Go to diagnostic LED sectionfor more information. VerifyXserve no longer shuts downafter starting up.

Yes Issue resolved.

No Go to Step 3


42/167


3. Disconnect all peripherals andexpansion cards. Verify thatXserve starts without issue.

Yes Suspect peripherals orexpansion cards as cause.Reconnect one at a time,verifying system operation ateach stage

No System had kernel panic orfreeze during Boot. Go toStep 4

4. Verify all fans in fan array arespinning and there is adequateairow inside and around theXserve

Yes All fans are spinning, andadequate airow. Go to step 5

No One or more fans are notspinning. Go to Fast/FailedFans Flow

5. Attempt to boot with originalinstall media or from anexternal hard drive withcompatible OS X installed.Verify the Xserve is able tosuccessfully boot to the Finder.

Yes System boots without kernelpanic or freeze using externaldrive. Corrupt OS installedor damaged internal startupdrive module. Run AXD/DiskUtility drive test and replacedrive module if test fails.Clean Install with compatibleMac OS X

H03

No System had kernel panic orfreeze during Boot. Go to

Step 6

6. Inspect if any memory errorLEDs illuminated. Install 1only known good compatiblememory DIMM in memoryslot#1. Verify System bootswithout kernel panic or freeze.

Yes System boot without kernelpanic or freeze with only 1DIMM installed.Re-install the customermemory (using optimizedrecommend congurations)until the at fault memory isidentied. Use extra knowngood memory to identifythe faulty memory module.Replace the faulty memorymodule.

X01

No System had kernel panic orfreeze during Boot. Replacelogic board.

M05


43/167


Uncategorized Symptom

Quick Check

Symptom Quick Check

Uncategorized SymptomUnable to locate appropriatesymptom code

Verify whether existing symptom code applies to theissue reported by the user. If not, document reportedsymptoms and send feedback to [email protected] stating that suitable symptom code could notbe found.


44/167

Xserve (Early 2009) Symptom Charts Mass Storage 442011-05-05

Mass Storage

Apple Drive Module Read/Write Issue

Unlikely cause: Optical drive, logic board, processors.

Quick Check

Symptom Quick Check

Read/Write Issues / Bad Blocks /Drive Formatting Issues Cannot save documents Read/Write error message Hang when accessing or

saving data.

Intermittent unexpectedhanging

Slow drive moduleperformance

1. Reseat any aected drives into other bays.

2. Boot from Install DVD. Verify S.M.A.R.T. status ofthe aected hard drive using Disk Utility.

3. Repair the aected hard drive using Disk Utility.

4. Start up system normally and check system.log

le for any volume remapping messages. A fewof these messages at random intervals are typicalof normal hard drive behavior and can be safelyignored. Excessive numbers of remapped blocks(i.e. dozens or hundreds), especially in a shortperiod of time, could indicate an imminentlyfailing drive module or other serious hardwareissue.

Deep Dive


1. Press the SMC Reset buttonon the logic board to resetthe SMC. Verify that theXserve now recognizes thedrive module.

Yes Issue resolved.

No Go to Step 2

2. Check internal diagnosticLEDs. Go to diagnostic LEDsection for more information.Verify that the Xserve now

recognizes the drive module.

Yes Issue resolved.

No Go to Step 3

3. Start up from Install disc andlaunch Disk Utility. Is usersdrive module available for DiskUtility to repair?

Yes Go to Step 4

No Go to Step 5


45/167


4. Run Repair Disk on the volumeusing Disk Utility. Did DiskUtility mount and repairvolume successfully?

Yes Return to Quick Checks toverify that the drive moduleno longer has read-writeerrors.

No Go to Step 5

5. Remove the original drivemodule from the Xserve andinspect it for any damage to itsconnector or the connector inthat drive bay of the Xserve. Isdamage present?

Yes Do not re-install the drivemodule if its connector isdamaged or if the drive bayconnector in the Xserve isdamaged. If there is anyvisible damage, replace thedamaged component.

M19H01

No Go to Step 6

6. Substitute a known-good drivemodule. Format this drivemodule using Disk Utility andselect zero all data optionto remap bad blocks. Verifythis drive module formatssuccessfully with no signicanterrors or large numbers of badblocks using Disk Utility log.

Yes User s drive module appearsto be defective. Replacedefective drive modulewith new replacement drivemodule of same or largercapacity. Format this drivemodule using Disk Utilityand select zero all dataoption to remap bad blocks.Verify this drive moduleformats successfully withno signicant errors or largenumbers of bad blocks using

Disk Utility log.

H03

No Go to Step 7

7. Reseat connectors on bothends of the Backplane-to-Logic Board I/O Cable. Formatknown-good drive moduleusing Disk Utility and selectzero all data option to remapbad blocks. Verify this drive

module formats successfullywith no signicant errors orlarge numbers of bad blocksusing Disk Utility log.

Yes Issue resolved.

No Go to Step 8


46/167


8. Replace the Backplane-to-Logic Board I/O Cable. Formatknown-good drive moduleusing Disk Utility and selectzero all data option to remapbad blocks. Verify this drive

module formats successfullywith no signicant errors orlarge numbers of bad blocksusing Disk Utility log.


No Go to Step 9

9. Replace Drive InterconnectBackplane. Format known-good drive module usingDisk Utility and select zeroall data option to remap badblocks. Verify this drive moduleformats successfully withno signicant errors or large

numbers of bad blocks usingDisk Utility log.


No Replace logic board. Reinstalloriginal drive module. Formatthis drive module using DiskUtility and select zero all

data option to remap badblocks. (Caution, doing thiswill erase all user data onthis drive. Ensure user hasthis data backed up beforeproceeeding).Verify this drive moduleformats successfully withno signicant errors or largenumbers of bad blocks usingDisk Utility log. Issue resolved.

M19

Apple Drive Module Not Recognized/Mounting

Unlikely cause: Optical drive, logic board, processors.

Quick Check

Symptom Quick Check

Non-startup drive modulenot recognized by system /

not mounting after system isbooted.

1. Verify drive bay lock is not activated. If it is, placethe drive bay lock in the unlocked position.

2. Reseat the drive module.3. Boot from Install DVD. Verify S.M.A.R.T. status of

drive module using Disk Utility.

4. Run complete AXD diagnostics.


47/167


Deep Dive

Check Result Action Code1. Press the SMC Reset button

on the logic board to resetthe SMC. Verify that theXserve now recognizes thedrive module.

Yes Issue resolved.

No Go to Step 2

2. Check internal diagnosticLEDs. Go to diagnostic LEDsection for more information.Verify that the Xserve nowrecognizes the drive module.

Yes Issue resolved.

No Go to Step 3

3. Start up from Install disc andlaunch Disk Utility. Is usersdrive module available for DiskUtility to repair?

Yes Go to Step 4

No Go to Step 5

4. Run Repair Disk on the volumeusing Disk Utility. Did DiskUtility mount and repairvolume successfully?

Yes Go to Step 11

No Go to Step 5

5. Remove the original drivemodule from the Xserve andinspect it for any damage to its

connector or the connector inthat drive bay of the Xserve. Isdamage present?

Yes Do not re-install the drivemodule if its connector isdamaged or if the drive bay

connector in the Xserve isdamaged. If there is anyvisible damage, replace thedamaged component.

M19H01

No Go to Step 6

6. Replace the users drivemodule that is not mountingwith a known-good drivemodule in the same bay.

Verify that the Xserve nowrecognizes the drive module.

Yes Replace failed drive module.Issue resolved.

H01

No Go to Step 7

7. Reseat connectors on bothends of the Backplane-to-LogicBoard I/O Cable and retest.Verify that the Xserve nowrecognizes the drive module.

Yes Issue resolved.

No Go to Step 8


48/167


8. Remove and re-seat DriveInterconnect Backplane andretest. Verify that the Xservenow recognizes the drivemodule.


No Go to Step 9

9. Replace the Backplane-to-Logic Board I/O Cable andretest. Verify that the Xservenow recognizes the drivemodule.


No Reinstall the Backplane-to-Logic Board I/O Cable. Go toStep 10

10. Replace Drive InterconnectBackplane and retest. Verifythat the Xserve now recognizesthe drive module.


No Reinstall original driveinterconnect backplane.Replace logic board. Issueresolved.

M19

11. Start up from users startup

volume. Verify that the Xservenow recognizes the drivemodule.

Yes Issue resolved.

No Go to Step 5

Apple Drive Module Noisy

Unlikely cause: Drive interconnect backplane, expansion cards, expansion slot riser cards

Quick Check

Symptom Quick Check

Drive Module Noisy Noise during boot Noise during operation Noise when drive is copying or

saving data

1. Test with known good media to see if noise isOptical drive related.

2. Check with Activity Monitor for any harddrive access when assessing idle drive noise.An example is Spotlight indexing in thebackground.

3. Verify if operational noises are excessive whencompared to another same model Xserve.

4. Boot from a known good Mac OS source to

eliminate possible software issues.5. Boot from Install DVD. Verify S.M.A.R.T. status of

the aected drive module using Disk Utility.

6. Reseat any aected drive modules into otherbays.

7. Repair any aected drive modules using DiskUtility.


49/167


Deep Dive


1. Boot from Install DVD andlaunch Disk Utility. Is the

aected drive moduleavailable for Disk Utility torepair?

Yes Go to Step 2

No Replace aected drive moduleor branch to Drive modulenot recognized/mounttroubleshoot guide

H01

2. Repair the aected drivemodule using Disk Utility andverify it completed successfully

Yes Go to Step 3

No Go to Step 4

3. Remove the customer drive

module(s), boot the Systemfrom an external drive, verify ifthe System remains excessivelynoisy.

Yes Fan noise or Optical Drive

noise likely to be the cause.See Optical Drive Noisy tableand Fan Failures/Thermalissues table .

No Go to step 4

4. Remove the customer drivemodule(s), install a knowngood drive module and verifyif the noise level is similar to

customers drive modules.

Yes Drive module(s) noise levelsare similar to a known gooddrive. No repair required

No Replace the aected drivemodule. Issue resolved.

H06


50/167


Optical Drive Read/Write Issue

Quick Check

Symptom Quick Check

Optical Drive Read/Write DataError Errors when writing optical

media Errors when reading optical

media Hang when accessing or

preparing to write data.

1. Test optical media in another drive of the sametype in same type of machine to rule out themedia issue.

2. For write issues, check with known-good mediathat performs well in another computer andoptical drive of the same type.

3. Check both CD and DVD media. If only one typeof media is producing errors, there is a laser issue.(J99)

Deep Dive


1. Is media free to spin withoutoptical drive scraping edge orsurface of media?

Yes Go to Step 2

No Replace optical drive. J03

2. Can optical drive read both CD

and DVD known-good media?

Yes Go to Step 6

No Reading CD only or DVDonly indicates laser issue,replace optical drive. Opticaldrive cannot read any mediareliably, Go to Step 3.

J03

3. Reseat cable connections atlogic board and optical drive.Verify that media is nowrecognized and reads reliably.

Yes Reseat resolved issue.

No Go to Step 4.

4. Disconnect optical drive bylifting SATA cable at logicboard and connecting aknown-good optical drive.Verify that media is nowrecognized and reads reliably.

Yes SATA port functional,reconnect users optical drive& SATA cable. Go to Step 5.



51/167


5. Install and test withreplacement optical drive SATAex cable. Verify that mediais now recognized and readsreliably.

Yes Cable change resolved issue. X03

No Replace the optical drive.(Mechanical damage tooptical drive, if found)

J01(J05)

6. Test write data to compatibleCD and DVD media. Verifyburned media is recognizedand reads reliably.

Yes Issue resolved.


J03(J06)

Optical Drive Not Recognized/Mount

Quick Check

Symptom Quick Check

Optical Drive Not Recognized/Mount Discs inject and eject, but do

not appear in Finder.

1. Make sure the Xserve is unlocked.

2. Use System Proler ATA section to see if theoptical drive appears.

3. Check Finder Preferences: General and make sureCDs, DVDs and iPods is checked under Showthese items on the Desktop.

4. Check both CD and DVD media. If only one typeof media is recognized, there might be a laserrelated issue. (J99)

Deep Dive


1. Is optical drive listed in thedevice tree for SATA devices inSystem Proler?

Yes Test with a known good CD/DVD media. Did media appearin Finder? Issue resolved.

No Go to step 2.


52/167


2. Verify all connections betweenlogic board, ex cable, opticaldrive are secure. Visuallyinspect cables and connectorsfor any debris, damage, or bentpins. Is optical drive now listed

in System Proler?

Yes Issue resolved.

No Replace any damaged cablesand retest. If connectionsare good and with no visiblecable damage, go to step 3.

X03

3. Disconnect optical drive bylifting SATA cable at logicboard and connecting aknown-good drive. Is opticaldrive now listed in SystemProler?



4. Install and test withreplacement optical drive SATAex cable. Is optical drive nowlisted in System Proler?

Yes Cable change resolved issue X03


M19


Yes Cable change resolved issue. J03


J03(J05)

Optical Drive Noisy

Quick Check

Symptom Quick Check

Optical Drive Noisy Noisy during boot Noisy during operation Noisy when drive is copying or

writing data.

1. Test optical media in another drive of same typein same type of computer to rule out mediaissue.

2. Check with known-good discs.

3. Check to see if noise occurs without media in

the drive. If so, check for hard drive (H06) and fan(M18) caused noises.


53/167


Deep Dive


1. Is optical drive constantlyseeking or cycling ejectmechanism without an opticaldisc installed? Optical driveshould perform only one resetsequence and rest idle, readyfor media.

Yes Continue and verify withmedia, Go to Step 2.

No Replace optical drive if continuous activity occurswith no disc installed.

J04

2. Insert known good data CD.Is media free to spin withoutoptical drive scraping edge orsurface of media? Verify discdoes not exceed maximumthickness specication.

Yes Continue and verify withmedia, Go to Step 3.

No Internal mechanicalinterference is aectingrotational spin of media,

replace optical drive.

J04

3. Initial disc handling noise isnormal. Disc spinning andhead seek indicate disc ismounting to desktop. Seeknoise should settle downonce mounted. Is noise abovenormal and related to seekactivity?

Yes Replace optical drive. J04

No Go to Step 4.

4. Disc spin should cease 30seconds after mounting dataCD on OS desktop. Is the noiserelated to disc spin?

Yes Go to Step 5.

No Go to Step 6.

5. Remove the optical drive andcheck for the correct seatingof the brackets on the opticaldrive and in the top case.Reinstall drive in unit andretest. Verify if drive is stillnoisy.

Yes Go to Step 6. X03

No Issue resolved. Optical drivewas not properly mounted inenclosure. (Possible physicaldamage to optical drive.)

(J05)

6. Eject known good data CD.

Disc handling noise shouldbe one pop of disc frommotor hub and a motor gearsound driving disc out ofoptical drive. Is noise abovenormal and related to disceject activity or multiple ejectattempts


No Go to Step 7.


54/167


7. Disc spin should cease 30seconds after mounting dataCD on desktop. Media maybe mounting on a defectiveinternal spindle hub. Is thenoise related to disc spin?


No Noise does not appear to berelated to optical drive.

Optical Drive Not Performing to Specs

Quick Check

Symptom Quick Check

Optical Drive Not Performing toSpec Read of write speeds slower

than expected.

1. Test optical media in another drive of the sametype in same type of computer to rule out mediaissue.

2. Check with known-good discs. Install discs thatcame with the computer.

3. For disc write issues, check with known goodmedia that performs well in another computerand drive of the same type.

4. Check both CD and DVD media. If only one typeof media is producing errors, there might be alaser related issue. (J99)

Deep Dive


1. Can optical drive read bothCD and DVD known-goodmedia?

Yes Go to step 5

No Reading CD only or DVDonly indicates laser issue,replace optical drive. Opticaldrive cannot read any mediareliably. Go to step 2.

J03

2. Reseat cable connections atlogic board and optical drive.Verify that media is nowrecognized and reads reliably.

Yes Reseat resolved issue X03

No Go to step 3


55/167


3. Disconnect optical drive bylifting SATA cable at logicboard and connecting aknown-good drive. Verify thatmedia is now recognized andreads reliably.




Yes Cable change resolved issue. X03

No Replace optical drive.(Mechanical damage tooptical drive, if found)

J03(J05)

5. Test write data to compatibleCD and DVD media. Verifyburned media is recognizedand reads reliably.

Yes Issue resolved.

No Replace optical drive.(Mechanical damage tooptical drive, if found)

J03(J06)

Optical Drive Wont Accept/Reject Media

Quick Check

Symptom Quick Check

Cannot insert a disc into thedrive.

Cannot eject a disc placed intothe drive.

1. Inspect optical drive slot for obstructions. Makesure the white shipping bracket is not in place.

2. If Xserve is locked, unlock it.

3. Verify the disc is not warped.

Deep Dive


1. Verify the disc is not thewrong size. Refer to article

HT2446Macintosh: UsingNonstandard Discs in disc-ROM or DVD-ROM Drives.

Yes Remove non-standard mediaand retest the drive with

known good media.

No Inspect System Proler. Go tostep 2.
http://support.apple.com/kb/HT2446http://support.apple.com/kb/HT2446http://support.apple.com/kb/HT2446http://support.apple.com/kb/HT2446http://support.apple.com/kb/HT2446mailto:[email protected]?subject=Xserve%20(Early%202009)%20Apple%20Technician%20Guide:


56/167


2. Verify the optical drive listed inthe device tree for ATA devicesin System Proler?

Yes Optical drive has power,inspect disc acceptance.Re-inspect for non standardmedia.

No Inspect and reseat cables. Goto step 3.

3. Verify all cable connectionsbetween optical drive andlogic board are secure. Visuallyinspect cables and connectorsfor any debris, damage, or bentpins. Is optical drive now listedin System Proler?

Yes Optical drive has power,inspect disc acceptance. Re-inspect for disc acceptanceand inspect for any nonstandard media.

No Replace or reseat anydamaged or loose cables andretest. If connections are goodand with no visible cabledamage, go to step 4.

X03

4. Connect a known good opticaldrive assembly. Is optical drivenow listed in System Proler?

Yes SATA port functional,recoonect users optical drive& SATA cable. Go to step 5.


5. Install and test users opticaldrive with replacement SATAex cable. Is optical drive nowlisted in System Proler?

Yes Cable changed resolved issue. X03


J03(J06)

6. With replacement ex cableand replacement optical driveis the device seen in SystemProler?

Yes Issue resolved.

No Replace logic board. J03

Optical Drive Wont Eject Media

Quick Check

Symptom Quick Check

Cant eject disc from opticaldrive 1. If the Xserve is locked, unlock it.2. Verify the disc is not in use by the system.

3. Drag the disc icon to the trash or select it andpress Command + E.

4. Connect a USB mouse and restart the Xservewhile holding down the mouse button toattempt to eject the disc.


57/167


Deep Dive


1. Verify that the bezel over theslot is not bent. If it is, gentlybend it back into position.

Yes Issue resolved.

No Go to step 2.

2. Verify the disc is not the wrongsize. Refer to article 58641Macintosh: Using NonstandardDiscs in disc-ROM or DVD-ROMDrives.

Yes Remove irregular shapedmedia and retest.

No Go to step 3.

3. Reseat the optical drive cableat both connectors.

Yes Issue resolved.

No Go to step 4.

4. Replace the optical drive cable. Yes Issue resolved. X03

No Go to step 5.

5. Replace the optical drive.Insert known good media andattempt to eject. Does themedia eject without issue?

Yes Issue resolved withreplacement drive.

J02

No Repeat process with anotherknown good drive and knowngood media.


58/167


RAID Battery Not Charging

Quick Check

Symptom Quick Check

RAID Battery Will Not Charge The following messages may be displayed inRAID Utility:

The Apple RAID Card Installed inyour system requires your attention:

Write Caches Disabled, and/or RAID Battery Conditioning:

RAID Battery Missing:

The RAID battery status never achievesCharged status:

Normal Charged Status:

1. If write caches are disabled:The RAID card backup batterymay not be fully charged. Toprotect your data, the RAID cardautomatically disables writecaching whenever the battery isnot fully charged. Once every threemonths the RAID card reconditionsthe battery by completelydischarging and then recharging it.

2. If the battery is not fully charged:Every three months, the RAID cardautomatically reconditions itsbattery by completely dischargingand then recharging it. During thereconditioning cycle, you may seean alert advising you that the 72-hour battery reserve is unavailableand the controller status mayindicate that write caches aredisabled. Performance may beslightly degraded during this time,but will return to normal when thebattery is fully recharged.

3. In most cases, leaving the Xserve

powered ON continuously for 72hours or more (not in Standby andnot in Sleep mode, but actuallypowered ON without interruption)gives the charging systemsucient time to fully chargethe battery and restore the writecaches to full functionality.

4. Examine Xserve log les for cluesand run complete AXD diagnosticson the Xserve to gather moreinformation before continuing

to the Deep Dive section of thissymptom.


59/167


Deep Dive


1. Disconnect RAID batteryconnector from drive

interconnect backplane.Using a multimeter set tomeasure DC voltage in the4 volt range, connect themultimeter probes to theextreme end connector pinsof the RAID battery connector.

Yes Go to Step 2

2. Does the multimeter measureat least 3.5 VDC?

No Replace battery. Go toStep 2

P10 - Batterywill not charge

P11 -Battery notrecognized

3. Reconnect RAID batteryconnector to driveinterconnect backplane. Startup Xserve and check RAIDUtility to verify battery isrecognized and is charging /conditioning.

Yes Go to Step 3

4. Is battery recognized andcharging / conditioning?

No Replace driveinterconnectbackplane (RAID

backplane). Go to Step2

M20

5. Wait 72 continous hourswith Xserve powered ONfor the RAID battery to fullycharge. Check RAID Utilityto verify battery continues tobe recognized and has fullycharged. Has battery fullycharged?

Yes Issue resolved.

No Replace driveinterconnectbackplane (RAIDbackplane). Go to Step2

M20

See Mac Pro RAID Card and Xserve RAID Card: Frequently Asked Questions (FAQ) - HT1346
http://support.apple.com/kb/HT1346http://support.apple.com/kb/HT1346mailto:[email protected]?subject=Xserve%20(Early%202009)%20Apple%20Technician%20Guide:


60/167



Quick Check

Symptom Quick Check




61/167

Xserve (Early 2009) Symptom Charts Input/Output Devices 612011-05-05

Input/Output Devices

Rear USB Port Does Not Recognize Known Devices

Quick Check

Symptom Quick Check

Rear USB Port Does NotRecognize Known Devices USB devices not recognized on

the rear USB port.

1. If the Xserve is locked, unlock it.

2. Check the for latest software updates for Appleand especially third party devices.

3. Use System Proler to verify the Systemrecognizes each of the USB buses in the USBdevice tree.

4. Test both rear ports with known good Apple

keyboard or mouse.5. Test front USB port with known good Apple

keyboard or mouse.

6. Verify any external USB device with large powerrequirements have their own external powersupplies.

7. Verify external USB device cables by using knowngood cables.

Deep Dive


1. Disconnect all peripheralsexcept for a known goodApple USB device.

Yes Go to step 2

No Repeat Step 1

2. Verify the USB ports are freefrom contaminants and debris.

Yes Go to step 3

No Remove contaminants anddebris. Replace aectedmodules if necessary. Defects

caused by contaminants ordebris are not covered byApple warranty. Go to step 3.
mailto:[email protected]?subject=Xserve%20(Early%202009)%20Apple%20Technicians%20Guide:


62/167


3. Reset SMC. Verify each of theUSB buses are recognized, anda known good connected USBdevice is recognized?

Yes Issue resolved. Issue maybecaused by another peripheraldevice.

No Replace Logic Board. M15

Front USB Port Does Not Recognize Known Devices

Quick Check

Symptom Quick Check

Front USB Port Does Not RecognizingKnown Devices USB devices not recognized on the

front USB port.


2. Check the for latest software updates forApple and especially third party devices.

3. Use System Proler to verify the Systemrecognizes each of the USB buses in theUSB device tree.

4. Test both rear ports with known goodApple keyboard or mouse.

5. Verify any external USB device with largepower requirements have their ownexternal power supplies.

6. Verify external USB device cables by usingknown good cables.

Deep Dive


1. Disconnect all peripheralsexcept for a known goodApple USB device.

Yes Go to step 2

No Repeat Step 1

2. Verify the USB ports are freefrom contaminants and debris.

Yes Go to step 3

No Remove contaminants anddebris. Replace aectedmodules if necessary. Defectscaused by contaminants ordebris are not covered byApple warranty. Go to step 3.


63/167


3. Reset SMC. Verify each of theUSB buses are recognized, anda known good connected USBdevice is recognized?


No Go to step 4.

4. Reseat the Front Panel Boardcable.

Yes Issue resolved.

No Replace Front Panel Board. M15N08

FireWire Port Does Not Recognize Known Devices

Quick Check

Symptom Quick Check FireWire Port Does NotRecognize Known Devices FireWire devices not

recognized.


2. Check the for latest software updates for Appleand especially third party devices.

3. Use System Proler to verify the Systemrecognizes each of the FireWire busses in theFireWire device tree.

4. Test both rear ports with known good FireWiredevice and cable.

5. Verify any external FireWire device with large

power requirements have their own externalpower supplies.

6. Verify external FireWire device cables by usingknown good cables.

7. Reset PRAM/NVRAM.

Deep Dive


1. Disconnect all peripheralsexcept for a known goodFireWire device and cable.

Yes Go to step 2

No Repeat Step 1


64/167


2. Verify the FireWire ports arefree from contaminants anddebris.

Yes Go to step 3

No Remove contaminants anddebris. Replace aectedmodules if necessary. Defectscaused by contaminants or

debris are not covered byApple warranty. Go to step 3.

3. Reset SMC. Verify each of theFireWire busses are recognized,and a known good connectedFirewire device is recognized?



PCI-E Expansion Card/Slot Not Recognized

Quick Check

Symptom Quick Check

I/O Expansion Issues Expansion riser/slot issues Cant detect expansion card

1. For Ethernet card issues, make sure to congureusing Network System Preference

2. For Fibre channel card issues, make sure tocongure using Fibre Channel Utility.

3. For SCSI card issues, make sure to congureusing Disk Utility.

4. Check System Proler to see if the card isrecognized.

5. Reset PRAM/NVRAM

6. Run AXD diagnostics and check log les.


65/167


Deep Dive


1. Does the expansion card meetthe requirements for the slot

in which it is being used?

Yes Go to step 2.

No Refer to product specicationsof Xserve then recommendthe card be replaced with theproper specication type ofmodel.

2. Reset SMC. Yes Issue resolved.

No Go to step 3.

3. Reseat the expansion card. Yes Issue resolved.

No Go to step 4.

4. Reseat the PCI riser card intothe logic board, and retest thecard in the same slot.

Yes Issue resolved.

No Go to step 5.

5. Test the expansion card inthe other expansion slot,if available, ensuring thecard being tested meets therequirements of the slot.

Yes Issue resolved.

No Go to step 6.

6. Test with a dierent knowngood compatible card in the

same type of slot.

Yes Issue resolved.

No Go to step 7.

7. Test with a known good PCIriser card.

Yes Issue resolved.


8. Does the expansion card workwith the replacement logicboard?

Yes Issue resolved.

No Repeat steps 3-7.


66/167



Quick Check

Symptom Quick Check




67/167


68/167

Xserve (Early 2009) Symptom Charts Communications 682011-05-05

2. Visually inspect Ethernetconnector to ensure all pinswill make physical contact withCAT5 or better network cable.

Yes Ethernet interface contactsare good. Go to step 3.

No Pins are damaged or bent at,

replace logic board.

M10

3. Isolate OS by booting fromoriginal install media. Verifynetwork link status activeby using Network Utility oninstall DVD and looking for linkLED adjacent to connectedEthernet port. If the Ethernetinterface (en0) link statusis inactive, recheck physicalconnection and link activityindicator on hub/ switch.

Yes Right-hand (1) Ethernetinterface (en0) Link Status isactive, go to step 4.

No Right-hand (1) Ethernetinterface (en0) Link Status isinactive. Replace logic board.

M10

4. Disconnect Xserve andconnect known-goodcomputer to network usingthe same Ethernet cable. Verifyif IP address is listed for theEthernet interface in SystemPreferences: Network. Retest.

Yes Go to step 5.

No If connection is OK on known-good system, replace logicboard.

M10

5. Verify connection by usingNetwork Utility to ping anotherconnected computer on thesame subnet. Ensure thetarget computer IP address isvalid, on the same subnet andpowered on. Ensure no MACaddress ltering or hardwareaccess control devices arepresent. Use a simple hub/switch environment. Is pingsuccessful?

Yes Go to step 6.

No If the symptoms do not

change, replace the logicboard.

M10


69/167

Xserve (Early 2009) Symptom Charts Communications 692011-05-05

6. Verify Ethernet performanceand reliability by starting upfrom a known-good OS install,and downloading a large lefrom a web site or le server.

Yes If there is performance orconnectivity issue isolatedsolely to the system undertest, the problem may be thenetwork environment. Norepair is necessary.

No If there are connectiondropouts or poorperformance not seen ona known-good test system,replace the logic board.

M10


Quick Check

Symptom Quick Check


Unable to locate appropriatesymptom code



70/167

Xserve (Early 2009) Symptom Charts Video 702011-05-05

Video

Video Distortion

Quick Che

Documents

Xserve - ServiceMan [Early2009]