ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

LSI Logic SCSI problem on Proliant ML110 server with Win 2003server as OS

vishy
Occasional Visitor

LSI Logic SCSI problem on Proliant ML110 server with Win 2003server as OS

Having problem with LSI Logic SCSI card. On startup, spins the SCSI hard disk but then shows 15 lines although I have only one hard disk. Any help please?
5 REPLIES
Oleg Koroz
Honored Contributor

Re: LSI Logic SCSI problem on Proliant ML110 server with Win 2003server as OS

is a HDD HP branded ? Non-HOT PLUG? Cabling with Termination? Any additional SCSI devices Connected?
vishy
Occasional Visitor

Re: LSI Logic SCSI problem on Proliant ML110 server with Win 2003server as OS

The Hard disk came with the computer from HP. It is LSI Logic SCSI hard disk. There is no other hard disk or device on SCSI Bus. The scsI cable is terminated
Brian_Murdoch
Honored Contributor

Re: LSI Logic SCSI problem on Proliant ML110 server with Win 2003server as OS


Hi,

I've seen this before on Adaptec and other controllers when the disk SCSI ID is set to 7 (Same as the controller). This confuses it into believing there are 15 devices attached when it polls the bus. Check your SCSI ID jumpers on the drive and set it to 0 (Usually no jumpers installed on the ID pins). Check it with no drive attached to see if the behaviour changes. If possible check the drive on another system to confirm the drive is OK. It might be a controller error but less likely.

I hope this helps.

Brian
vishy
Occasional Visitor

Re: LSI Logic SCSI problem on Proliant ML110 server with Win 2003server as OS

Thanks Brian. The ID was set initially set at "0". I changed it to "1" and the SCSI Disk is working. It solved my problem but I wonder why it happened in the first place.
Jon Ward
Trusted Contributor

Re: LSI Logic SCSI problem on Proliant ML110 server with Win 2003server as OS

There is no doubt there was a problem with the SCSI bus (hard drive, cable, controller). Typically, it is a SCSI ID conflict, but it could be another issue cause the same effect.

However, it appears that simply reseating the hard drive and/or jumpers may have resolved the situation. You may want to return to the old configuration to verify that is indeed the case. Otherwise, you may want to contact Technical Support to have it fixed if it is still under warranty/contract.