Troubleshooting SCSI issues

1. To begin troubleshooting, check the following top issues. If your issue is listed, select the link, otherwise proceed to step 2.

   	SCSI adapter is not seen during POST/startup
   	SCSI adapter is not seen in the operating system
   	SCSI device is not seen during POST/startup
   	SCSI device is not seen in the operating system
   	Operating system not found after adding a SCSI adapter
   	POST error 1801 when multiple SCSI adapters installed
   	SCSI errors

2. Check IBM ServerProven to ensure all options are compatible with your system.
   
3. Refer to your system's Hardware Maintenance Manual for appropriate installation and removal instructions.
   
4. Run diagnostics to test the hardware. If a failure is indicated, use the error code extension to isolate the cause. Complete SCSI device error codes are 12 characters long. The first eight characters of the SCSI error code are for device information - not error information. The error information is in the next four characters (error extension bytes). Failure to use the entire error code may result in incorrect FRU parts replacement.
   
   
   • Read errors may be caused by a bad or interrupted write operation if the drive was bumped or power failed during the write operation (sector incompletely written).
     
     
     1. If only the data is corrupted, rewriting the data will correct the error.
     2. If the error occurs in the directory or the operating system's file structure, it may be necessary to perform a high-level format (Format C), or even to re-create the partition with FDISK.
     3. If the sector ID is corrupted (ID or Sector Not Found errors), an advanced diagnostic format should be attempted prior to replacement of the fixed disk. The advanced diagnostic format will re-write all sector addresses and data fields. When the format completes, the diagnostics should be re-run. If the diagnostics then run error-free, it is unlikely that a hardware failure has occurred.
        
   • If failures return after a particular software application has been loaded, it could mean that the software is corrupting the fixed disk. Assistance should be sought from the appropriate software source. Failures may occur during system operation, yet diagnostics might run error-free. This could be due to improper termination (see below for more information on termination).
     
5. Check all SCSI IDs. Each device must be set for a unique SCSI ID via jumpers, switches, or remotely with a cable-connected switch. Run 'Set and View SCSI Configuration' from the Configuration menu - to configure new or powered-off devices.
   
6. Check that all devices are receiving power:
   
   1. Is the 'Power Good' (green) light illuminated on the system unit? 'Power Good' is more complex than a 'Power On' light. It indicates that the power supply is delivering all the correct dc output voltages within specifications (that is, +5 Vdc for logic circuits and +12 Vdc for motor circuits, though some SCSI fixed disks may also use +5 Vdc). Any missing or incorrect voltage will cause the system to shut down (self-protect).
   2. Is the power cable connected correctly (that is, not inverted)?
   3. Check whether any contacts have been inadvertently pushed back into the power cable connector. Examine all power cable connections and check whether any female contacts are distorted and thereby making intermittent contact. If so, reform them using the tip of a small screwdriver (or similar tool).
      
7. Check that all other connections and cabling are correct:

   View CRU parts installation and removal movies for your system

   
   
   1. Ensure that the SCSI adapter is fully seated. Tension on the external SCSI interface cable may cause the SCSI adapter to partially unplug (unseat) from the system board. (Systems jammed against a wall are subject to this).
   2. Ensure both ends of all cables are firmly and properly seated.
      
8. Check termination. It is critical that the SCSI Bus is terminated properly. The physical ends of the internal and external SCSI Bus must be terminated at the last device. Devices connected to the middle of the Bus MUST NOT BE TERMINATED.
   
   
   1. Terminator types include the following:
      • Socketed DIP (Dual In-line Package) on the adapter
      • Connector plug on the adapter's internal or external connector or cable
      • Two or more socketed SIPs (Single In-line Packages) on a device
      • In-line terminator attached between device and cable
      • Enabled via a jumper
        
   2. The polarity of terminators must be correct:
      • Pin 1 on DIPs and SIP are usually indicated by a dot or arrow
      • Pin 1 on sockets are usually indicated by a 1, dot, or square solder pad
        
9. For a SCSI device to 'come ready' and be configured, the following events must occur:
   
   
   1. Upon Power-on Reset, SCSI Post issues an Inquiry command to each SCSI address - to poll all devices present.
   2. All SCSI devices attached to the SCSI Bus must answer with their inquiry data.
   3. A Test Unit Ready command is issued to all devices that responded to the Inquiry command.
   4. If a hard disk drive answers 'Not Ready', a Start Unit command is then issued to sequentially start the drive (Motor Start). The devices must then run 'Self Test' and report their status.
   5. Once the drive is ready, the Read Device Capacity command is issued - to determine the device size for example 320MB, 1GB, etc).
   6. All responding devices are compared with the configuration data.
   7. Post beeps twice and displays errors if there are any new, missing, or defective SCSI devices.
   8. Following a successful Post (one beep), the system will attempt to load the operating system.
      
10. If these steps have not solved your problem,
    refer to your system's Hardware Maintenance Manual (HMM), or refer to "Need more help?"

Need more help?

Please select one of the the following options for further assistance:

Support forums

Submit a technical question

Before you call IBM Service

---

Applicable countries and regions
Worldwide

Back to top

Document id: MIGR-50643
Last modified: 2007-09-05
Copyright © 2008 IBM Corporation

引自:https://www-304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-50643&brandind=5000019

[@more@]

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/743764/viewspace-1004031/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/743764/viewspace-1004031/