Let's say you start a Windows 2003 Server installation and the SCSI adapter and the disk storage attached to the adapter aren't recognized. What could be the cause and what steps can you take to solve the problem?© BrainMass Inc. brainmass.com October 9, 2019, 5:05 pm ad1c9bdddf
Here are some possible causes and answers:
SCSI or fibre channel storage devices do not respond.
Cause: The SCSI bus is not properly terminated.
Solution: Make sure that the SCSI bus is not terminated early and that the SCSI bus is terminated at both ends.
Cause: The SCSI or fibre channel cable is longer than the specification allows.
Solution: Make sure that the SCSI or fibre channel cable is not longer than the cable specification allows.
Cause: The SCSI or fibre channel cable is damaged.
Solution: Make sure that the SCSI or fibre channel cable is not damaged. (For example, check for bent pins and loose connectors on the cable and replace it if necessary.)
Disk groups do not move or stay online pending after move.
Cause: Cables are damaged or not properly installed.
Solution: Check for bent pins on cables and make sure that all cables are firmly anchored to the chassis of the server and drive cabinet.
Disks do not come online or Cluster service does not start when a node is turned off.
Cause: If the quorum log is corrupted, the Cluster service cannot start.
Drives do not fail over or come online.
Cause: The drive is not on a shared storage bus.
Solution: If drives on the shared storage bus do not fail over or come online, make sure the disk is on a shared storage bus, not on a nonsystem bus.
Cause: If you have more than one local storage bus, some drives in Shared cluster disks will not be on a shared storage bus.
Solution: If you do not remove these drives from Shared cluster disks, the drives do not fail over, even though you can configure them ...
Windows 2003 Server installation and the SCSI adapter are featured.