DLT VS160 multiple listing in device manager

[mrmike_1]

Please can anyone advise if they've seen this issue, and if so if they've managed to resolve the problem.

On some systems have noticed that within device manager and rsm, the drive can be listed 8, 16 or 32 times.

It is only on the DLT VS160, VS80 and ultrim drives are fine

anyone have any ideas

thanks
mrmike

[TapeDrive Killer]

I have seen that this could be a problem with the terminator or the SCSI ID

Check your terminator and make sure that your tape drive doesn't have SCSI ID 7 because that the SCSI ID of the HBA or any ID that its being used by another device on the same bus.

Need more information is the tape drive internal or external to the server ?
Is it daisy chain ?
What HBA are you using ?
What are the SCSI ID's ?

Pablo Alvarado
Tape Storage DPX

[mrmike_1]

We've seen this on 50+ systems, the SCSI ID is correct, usually set to ID 2 or 3, and is the only device on the HBA

LSI Logic Ultra 320 (G3 and G4 servers)

Have this issue under windows 2000 + 2003

If we switch to an ultrium drive on the same HBA and SCSI ID we have no problems

but if replace with another VS160 we get the same problem

[TapeDrive Killer]

Mike are the tape drives external ?
I know Ultrium tape drives have auto termination but the DLT don't

Pablo Alvarado
Tape Strorage DPX

[mrmike_1]

sorry missed that,

they all internal drives

[TapeDrive Killer]

This is getting hard ok more questions

Does the internal cable have a terminator at the end ?

[mrmike_1]

yes - for the dlt's we use LVD cables

[TapeDrive Killer]

This is gettin fun

Mike Im sure this is a SCSI ID problem I need you to check if you SCSI controller has SCSI ID 7

Just for testing purposes you can try to use a different HBA maybe a smart array (make sure there is no HDD with same SCSI ID as the drive) so we can see what is the SCSI ID that the OS reads from the tape drive

[mrmike_1]

all our controllers are on ID 7

we can delete all devices and reboot and problem will go away for a few weeks or more

we've even swapped drives and this fixes it for a while as well

this is what is confusing about it, and also causing problems trying to diagnose the fault - we've also been in touch with hp or say they've never heard of this problem

[mrmike_1]

further info, we've found that this fault usually transpires once a customer has a backup tape jammed in the device

and none of our tapedrives are installed on a raid array, or same channel as any other device