a. Turn off the blade server, remove it from the BladeCenter unit, and open thecover.b. If there are two IDE drives:1) Remove the second drive attached to IDE connector 2.2) Close the cover, reinstall the JS20 server, turn it on, and look for anerror in the BladeCenter management-module event log and the LinuxSyslog (platform log):a) If no error occurs and you are able to log in, then the driveconnected to IDE connector 2 may be faulty; replace that drive.b) If the error reoccurs, continue with step 3c.c. If there is only one IDE drive installed, or if the second IDE drive is notfaulty:1) Turn off the blade server, remove it from the BladeCenter unit, and openthe cover.2) Remove the first drive attached to IDE connector 1.3) Close the cover, reinstall the JS20 server, turn it on, and look for anerror in the BladeCenter management-module event log. If the operatingsystem is Linux, the Linux Syslog (platform log) might have moreinformation to help you isolate the problem.Note: If you are utilizing a network boot there will not be a Syslogavailable.a) If no error occurs (except an indication that the boot device could notbe found), then the drive might be faulty.b) If the error reoccurs, then the drive connected to IDE connector 1does not appear to be faulty; reinstall the drive and continue withstep 4.Note: Minimum operating requirements are:v System board and microprocessorsv Memory (with a minimum of two memory DIMMs of at least 256 MBeach)4. Check the DIMMs:a. Turn off the blade server, remove the blade server from the BladeCenterunit, and open the cover.b. Replace the memory modules one at a time (minimum requirement = twoDIMMs of 256 MB DIMMs or greater); each time, reinstall, turn on, andreconfigure the blade server to the original configuration.If all DIMMs have been replaced and the problem remains, continue withstep 5.5. Install and turn on the blade server. If the problem remains, suspect the systemboard and microprocessors.Notes:1. If the problem goes away when you remove an adapter from the system, andreplacing that adapter does not correct the problem, suspect the system board.2. If you suspect a networking problem and the blade server passes all thesystem tests, suspect a network cabling problem external to the blade server.Chapter 10. Symptom-to-FRU index 157
