Apple xserve early 2009 User Manual

							Xserve (Early 2009) Symptom Charts — Startup and Power Issues 41 2010-06-28
Kernel Panic/System Crashes
Quick Check
SymptomQuick Check
Memory Issues/Kernel panic and 
freezes
• Unit has kernel panic or freezes 
on startup or when operating
• Memory not recognized in 
System Profiler or in Memory 
Slot Utility
• Fans running fast
1. After power ON, verify Front Panel power LED 
illuminated, and not flashing any error sequences 
indicating a memory failure.
2.  Verify with known good and compatible memory 
DIMMs. Memory from older computers is not 
compatible and cannot be used.
3. Ensure the compatible memory is filled in the 
correct order in the memory slots. If memory 
is not configured for the best performance the 
“Memory Slot Utility” will appear on screen 
and recommend an improved configuration. 
To use the utility again go to /System/Library/
CoreServices/Memory Slot Utility
4.  Confirm total memory in System Profiler.
5. Startup with ‘Shift’ key down for safe mode boot. 
Check panic.log info for crash cause.
6.  Startup from original install media, or known 
good boot device with compatible Mac OS X.
7. Run all AXD diagnostic tests.
Deep Dive
CheckResultActionCode
1.  Press the SMC Reset button 
on the logic board to reset the 
SMC. Verify Xserve no longer 
shuts down after starting up
YesIssue resolved.
NoGo to Step 2
2.  Check internal diagnostic LEDs.  
Go to diagnostic LED section 
for more information. Verify 
Xserve no longer shuts down 
after starting up.
YesIssue resolved.
NoGo to Step 3  
						

							Xserve (Early 2009) Symptom Charts — Startup and Power Issues 42 2010-06-28
3. Disconnect all peripherals and 
expansion cards. Verify that 
Xserve starts without issue.
YesSuspect peripherals or 
expansion cards as cause. 
Reconnect one at a time, 
verifying system operation at 
each stage
NoSystem had kernel panic or 
freeze during Boot. Go to 
Step 4
4.  Verify all fans in fan array are 
spinning and there is adequate 
airflow inside and around the 
Xserve 
YesAll fans are spinning, and 
adequate airflow. Go to step 5
NoOne or more fans are not 
spinning. Go to “Fast/Failed 
Fans” Flow
5. Attempt to boot with original 
install media or from an 
external hard drive with 
compatible OS X installed. 
Verify the Xserve is able to 
successfully boot to the Finder. 
YesSystem boots without kernel 
panic or freeze using external 
drive. Corrupt OS installed 
or damaged internal startup 
drive module. Run AXD/Disk 
Utility drive test and replace 
drive module if test fails.  
Clean Install with compatible 
Mac OS X 
 
 
 
H03
NoSystem had kernel panic or 
freeze during Boot. Go to 
Step 6
6.  Inspect if any memory error 
LED’s illuminated. Install 1 
only known good compatible 
memory DIMM in memory 
slot#1. Verify System boots 
without kernel panic or freeze.
YesSystem boot without kernel 
panic or freeze with only 1 
DIMM installed.  
Re-install the customer 
memory (using optimized 
recommend configurations) 
until the at fault memory is 
identified. Use extra known 
good memory to identify 
the faulty memory module. 
Replace the faulty memory 
module.
X01
NoSystem had kernel panic or 
freeze during Boot. Replace 
logic board.
M05  
						

							Xserve (Early 2009) Symptom Charts — Startup and Power Issues 43 2010-06-28
Uncategorized Symptom
Quick Check
SymptomQuick Check
Uncategorized Symptom
Unable to locate appropriate 
symptom code
Verify whether existing symptom code applies to the 
issue reported by the user. If not, document reported 
symptoms and send feedback to smfeedback@apple.
com stating that suitable symptom code could not 
be found.  
						

							Xserve (Early 2009) Symptom Charts — Mass Storage 44 2010-06-28
Mass Storage
Apple Drive Module Read/Write Issue
Unlikely cause: Optical drive, logic board, processors.
Quick Check
SymptomQuick Check
Read/Write Issues / Bad Blocks / 
Drive Formatting Issues 
• Cannot save documents
• Read/Write error message
• Hang when accessing or 
saving data.
• Intermittent unexpected 
hanging
• Slow drive module 
performance
1. Reseat any affected drives into other bays.
2.  Boot from Install DVD. Verify S.M.A.R.T. status of 
the affected hard drive using Disk Utility.
3. Repair the affected hard drive using Disk Utility.
4.  Start up system normally and check system.log 
file for  any volume remapping messages. A few 
of these messages at random intervals are typical 
of normal hard drive behavior and can be safely 
ignored.  Excessive numbers of remapped blocks 
(i.e. dozens or hundreds), especially in a short 
period of time, could indicate an imminently 
failing drive module or other serious hardware 
issue. 
Deep Dive
CheckResultActionCode
1. Press the SMC Reset button 
on the logic board to reset 
the SMC. Verify that the 
Xserve now recognizes the 
drive module.
YesIssue resolved.
NoGo to Step 2
2.  Check internal diagnostic 
LEDs.  Go to diagnostic LED 
section for more information. 
Verify that the Xserve now 
recognizes the drive module.
YesIssue resolved.
NoGo to Step 3
3. Start up from Install disc and 
launch Disk Utility. Is user’s 
drive module available for Disk 
Utility to repair?
YesGo to Step 4
NoGo to Step 5  
						

							Xserve (Early 2009) Symptom Charts — Mass Storage 45 2010-06-28
4. Run Repair Disk on the volume 
using Disk Utility. Did Disk 
Utility mount and repair 
volume successfully?
YesReturn to Quick Checks to 
verify that the drive module 
no longer has read-write 
errors.
NoGo to Step 5
5. Remove the original drive 
module from the Xserve and 
inspect it for any damage to its 
connector or the connector in 
that drive bay of the Xserve. Is 
damage present?
YesDo not re-install the drive 
module if its connector is 
damaged or if the drive bay 
connector in the Xserve is 
damaged.  If there is any 
visible damage, replace the 
damaged component.
M19 
H01
NoGo to Step 6
6.  Substitute a known-good drive 
module. Format this drive 
module using Disk Utility and 
select ‘zero all data’ option 
to remap bad blocks. Verify 
this drive module formats 
successfully with no significant 
errors or large numbers of bad 
blocks using Disk Utility log.
YesUser’s drive module appears 
to be defective. Replace 
defective drive module 
with new replacement drive 
module of same or larger 
capacity. Format this drive 
module using Disk Utility 
and select ‘zero all data’ 
option to remap bad blocks. 
Verify this drive module 
formats successfully with 
no significant errors or large 
numbers of bad blocks using 
Disk Utility log.
H03
NoGo to Step 7
7. Reseat connectors on both 
ends of the Backplane-to-
Logic Board I/O Cable.  Format 
known-good drive module 
using Disk Utility and select 
‘zero all data’ option to remap 
bad blocks. Verify this drive 
module formats successfully 
with no significant errors or 
large numbers of bad blocks 
using Disk Utility log.
YesIssue resolved.
NoGo to Step 8  
						

							Xserve (Early 2009) Symptom Charts — Mass Storage 46 2010-06-28
8. Replace the Backplane-to-
Logic Board I/O Cable. Format 
known-good drive module 
using Disk Utility and select 
‘zero all data’ option to remap 
bad blocks. Verify this drive 
module formats successfully 
with no significant errors or 
large numbers of bad blocks 
using Disk Utility log.
YesIssue resolved.X03
NoGo to Step 9
9. Replace Drive Interconnect 
Backplane.  Format known-
good drive module using 
Disk Utility and select ‘zero 
all data’ option to remap bad 
blocks. Verify this drive module 
formats successfully with 
no significant errors or large 
numbers of bad blocks using 
Disk Utility log.
YesIssue resolved.M19
NoReplace logic board. Reinstall 
original drive module. Format 
this drive module using Disk 
Utility and select ‘zero all 
data’ option to remap bad 
blocks. (Caution, doing this 
will erase all user data on 
this drive. Ensure user has 
this data backed up before 
proceeeding). 
Verify this drive module 
formats successfully with 
no significant errors or large 
numbers of bad blocks using 
Disk Utility log. Issue resolved.
M19
Apple Drive Module Not Recognized/Mounting
Unlikely cause: Optical drive, logic board, processors.
Quick Check
SymptomQuick Check
• Non-startup drive module 
not recognized by system / 
not mounting after system is 
booted.
1. Verify drive bay lock is not activated.  If it is, place 
the 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.  
						

							Xserve (Early 2009) Symptom Charts — Mass Storage 47 2010-06-28
Deep Dive
CheckResultActionCode
1. Press the SMC Reset button 
on the logic board to reset 
the SMC. Verify that the 
Xserve now recognizes the 
drive module.
YesIssue resolved.
NoGo to Step 2
2.  Check internal diagnostic 
LEDs.  Go to diagnostic LED 
section for more information. 
Verify that the Xserve now 
recognizes the drive module.
YesIssue resolved.
NoGo to Step 3
3. Start up from Install disc and 
launch Disk Utility. Is user’s 
drive module available for Disk 
Utility to repair? 
YesGo to Step 4
NoGo to Step 5
4.  Run Repair Disk on the volume 
using Disk Utility. Did Disk 
Utility mount and repair 
volume successfully?
YesGo to Step 11
NoGo to Step 5
5. Remove the original drive 
module from the Xserve and 
inspect it for any damage to its 
connector or the connector in 
that drive bay of the Xserve. Is 
damage present?
YesDo not re-install the drive 
module if its connector is 
damaged or if the drive bay 
connector in the Xserve is 
damaged.  If there is any 
visible damage, replace the 
damaged component.
M19 
H01
NoGo to Step 6
6.  Replace the user’s drive 
module that is not mounting 
with a known-good  drive 
module in the same bay. 
Verify that the Xserve now 
recognizes the drive module.
YesReplace failed drive module.  
Issue resolved.
H01
NoGo to Step 7 
7. Reseat connectors on both 
ends of the Backplane-to-Logic 
Board I/O Cable and retest. 
Verify that the Xserve now 
recognizes the drive module.
YesIssue resolved.
NoGo to Step 8  
						

							Xserve (Early 2009) Symptom Charts — Mass Storage 48 2010-06-28
8. Remove and re-seat Drive 
Interconnect Backplane and 
retest. Verify that the Xserve 
now recognizes the drive 
module.
YesIssue resolved.X03
NoGo to Step 9
9. Replace the Backplane-to-
Logic Board I/O Cable and 
retest. Verify that the Xserve 
now recognizes the drive 
module.
YesIssue resolved.X03
NoReinstall the Backplane-to-
Logic Board I/O Cable. Go to 
Step 10
10.  Replace Drive Interconnect 
Backplane and retest. Verify 
that the Xserve now recognizes 
the drive module.
YesIssue resolved.M19
NoReinstall original drive 
interconnect backplane.  
Replace logic board. Issue 
resolved.
M19
11. Start up from user’s startup 
volume. Verify that the Xserve 
now recognizes the drive 
module.
YesIssue resolved.
NoGo to Step 5
Apple Drive Module Noisy
Unlikely cause: Drive interconnect backplane, expansion cards, expansion slot riser cards 
Quick Check
SymptomQuick 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 is 
Optical drive related. 
2.  Check with Activity Monitor for any hard 
drive access when assessing idle drive noise. 
An example is Spotlight indexing in the 
background.
3. Verify if operational noises are excessive when 
compared 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 affected drive module using Disk Utility.
6.  Reseat any affected drive modules into other 
bays. 
7. Repair any affected drive modules using Disk 
Utility.  
						

							Xserve (Early 2009) Symptom Charts — Mass Storage 49 2010-06-28
Deep Dive
CheckResultActionCode
1. Boot from Install DVD and 
launch Disk Utility.  Is the 
affected drive module 
available for Disk Utility to 
repair?
YesGo to Step 2
NoReplace affected drive module 
or branch to “Drive module 
not recognized/mount” 
troubleshoot guide
H01
2.  Repair the affected drive 
module using Disk Utility and 
verify it completed successfully
YesGo to Step 3
NoGo to Step 4
3. Remove the customer drive 
module(s), boot the System 
from an external drive, verify if 
the System remains excessively 
noisy.
YesFan noise or Optical Drive 
noise likely to be the cause. 
See Optical Drive Noisy table 
and Fan Failures/Thermal 
issues table .
NoGo to step 4
4.  Remove the customer drive 
module(s), install a known 
good drive module and verify 
if the noise level is similar to 
customer’s drive modules.
YesDrive module(s) noise levels 
are similar to a known good 
drive. No repair required
NoReplace the affected drive 
module. Issue resolved.
H06  
						

							Xserve (Early 2009) Symptom Charts — Mass Storage 50 2010-06-28
Optical Drive Read/Write Issue
Quick Check
SymptomQuick Check
Optical Drive Read/Write Data 
Error
• 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 same 
type in same type of machine to rule out the 
media issue.
2.  For write issues, check with known-good media 
that performs well in another computer and 
optical drive of the same type.
3. Check both CD and DVD media. If only one type 
of media is producing errors, there is a laser issue. 
(J99)
Deep Dive
CheckResultActionCode
1. Is media free to spin without 
optical drive scraping edge or 
surface of media?
YesGo to Step 2
NoReplace optical drive.J03
2.  Can optical drive read both CD 
and DVD known-good media?
YesGo to Step 6
NoReading CD only or DVD 
only indicates laser issue, 
replace optical drive. Optical 
drive cannot read any media 
reliably, Go to Step 3.
J03
3. Reseat cable connections at 
logic board and optical drive. 
Verify that media is now 
recognized and reads reliably.
YesReseat resolved issue.
NoGo to Step 4.
4.  Disconnect optical drive by 
lifting SATA cable at logic 
board and connecting a 
known-good optical drive. 
Verify that media is now 
recognized and reads reliably.
YesSATA port functional, 
reconnect user’s optical drive 
& SATA cable. Go to Step 5.    
NoReplace logic board.M19