How do I diagnose failed SCSI disk?
Posted on 2009-05-16
I'd appreciate some advice re diagnosing and repairing/replacing a failed SCSI disk in an out-of-warranty generic Intel server running Windows Server 2003. The machine runs SQL Server 2000, and I use it only for data analysis. There are three Seagate Cheetahs on one channel of the motherboard SCSI controller, the 34GB boot disk and two 68GB disks. The SQL data files that I'm actively using are on a 600GB MegaRAID SCSI RAID 10 array, and others (e.g., raw and outdated data) are on a 1TB ReadyNAS Duo (via NFS share). One of the 68GB Cheetahs contains the SQL log files, and the other contain(ed) temporary working databases.
In preparation to replace a failing disk (one of those notorious 1TB Seagate Barracudas) in the ReadyNAS Duo, I decided to backup all of the databases on that device. The next morning, I found that one of the 68GB Cheetahs, fortunately not the one containing the SQL log files, had disappeared from the server. Looking in Disk Management, I saw that disk listed as missing/offline with status failed.
I tried reactivating the volume, but that did nothing. Is there anything else that I can do to diagnose the disk before replacing it?
Based on what I've found on Experts Exchange, I gather that one possibility is a bad SCSI cable. Given that the other two disks on that cable are OK, perhaps it's a loose connection. Before replacing the disk, I'll try re-seating all of the connectors on that cable. If that doesn't bring the disk back, I'll replace it, using the same ID for the new disk.
Does that sound reasonable? What have I missed?