Semaphore Timeout

[xiong]

Here's a head scratcher...

I'm getting the "Semaphore Timeout" error on my BE server (Win 2K, SP4). I've searched the threads and KB, and found this:

http://seer.support.veritas.com/sea...Path=seer.support.veritas.com/docs/258341.htm

However, I'm not performing a backup, I'm actually trying to catalog a tape!

Any thoughts?

 

[packdragon]

If Backup Exec for Windows NT/2000 jobs are reporting hardware errors such I/O Errors, Semaphore Timeout errors, and Event ID 9, 11 and 15 the in System Event Log, this may be due the fact that the SCSI driver on the system is out of date. See Veritas TechNote ID: 231918.

- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-

http://www.solien.com

 

[xiong]

Thanks, close, but not dice. I just figured this one out in the past hour.

The drive was a Compaq 20/40 DLT drive, that can be configured on the drive for anyone of the 16 SCSI IDs. In this case, the drive was moved from a server where ID 6 was the controller, to a server where ID 7 was the controller. The drive was configured to use ID 7, and not changed when the move occured. By having it assigned to the Controller ID, the OS found the DLT drive and installed it 16 times for each of the 16 SCSI IDs.

When I tried to catalogue the tape, it evidently would time-out because of the confusion, and return the error. Once I changed the SCSI ID on the unit to match where the SCSI controller actually had it configured, the backup/restore, and catalog functions worked flawlessly.

The Veritas Technical Support thought the unit was bad, but was unfamiliar with this type of drive, but they gave me a good enough lead to figure it out.

~Xiong
If it ain't broke, fix it 'til it is.