URGENT! SCSI disk question..

[Jugernot]

A coworker just replaced a SCSI drive in our server and I asked him what SCSI ID he set and he said "Huh? I just stuck it in." We are having read/write problems with the particular servers and it's corrupting files.... would a SCSI drive that isn't terminated or the SCSI ID setup correctly cause corruption problems like this? I'm pretty sure that is the case as I know sometimes SCSI drives will work even configured wrong, but will exibit problems later.

THanks

 

[shansen008]

If it was working fine before and they just replaced the drive with a new one, then termination probablyt isnt the problem. Since it sounds like the person didnt do anyhting other then replace the drive. Sounds like they werent competent enough to even know what termination is. What kind of drive was it? I know most IBM drives come set from the factory at SCSI ID #6. If there is a SCSI ID conflict then there could be many issues. IS this hard drive part of a raid volume or is it a standalone disk? If this person wasnt careful they could have also bent a pin when pluggin and unplugging the cables, this happens a lot.

Need more info.

 

[SCSIfreek]

What kind of idiot works with servers and don't know what the hell they're doing? I mean the first thing you do before switching drives on a server is check their SCSI ID's and make sure they're correctly terminated. Yes data could be corrupted due to incorrect termination and check the power connectors to make sure they're seatting tightly.

 

[mastertech01]

Well if it is a set of drives in an SCA tower or server you wouldnt have to set termination, that is done in the tower itself. I am assuming this was a hotswap in such an environment. Termination and ID would not have to be set in such an array. I am assuming this was some kind of RAID 5 array or similar, so did he rebuild the array or simply replace a stand alone backup drive?

 

[BDawg]

Some SCSI adapters auto assign. Some of our servers will auto assign drives in hot swap 0 as 0, 1 as 1, etc...

 

[Jugernot]

Nope, no hot swapping, this was a older Quad CPU Compaq Proliant that we recently upgraded to our office file server. I ask him to install the drive, not knowing that he didn't know how to use SCSI storage. So I took it out yesterday and configured it and noticed the cables were all scratched and frayed. I'm guessing the doofus just shoved the drive cage back in the server without properly spacing the cables. Anyway, I stuck it in another machine in the office and it's working fine so far.

btw, I did notice the drive wasn't even being shown at bootup for the SCSI controller, but it was available in Windows. I think there was a SCSI ID problem. ANyway, it seems the only files effected (luckily) were ones that people had written to on Monday. Most of those were backed up to tape, so it wasn't as bad as I had thought.

Thanks guys for the help!