SCSI: First party detected bus hang -- which device?

[kenny chia]

Hi
I have encountered numerous bus hang on one of my HPUX servers. From the dmesg, how do I determine which device is causing this problem?? Thanks

P.S. This thread has been moevd from General to HP-UX > sysadmin. - Hp Forum Moderator

[Denver Osborn]

I would check the device at c3t3d0

"bp->b_dev: cb033000"


Hope this helps,
-denver

[Denver Osborn]

Can you post an ioscan -fn output from this box. Maybe it will help.

-denver

[kenny chia]

hmm..
I guess its my tape drive. Funny thing is, there wasn't any tape operation on the drive at all. From the dmesg what could have gone wrong?

I've been receiving these tape drive messages from some of my HP servers lately. Are there documentation for these messages? I would like to be able to decode these messages. Thanks

[Denver Osborn]

You're tape drive is showing as "NO_HW". Meaning that the hardware has stopped responding. Have you checked cables, termination and ensured the drive is powered on w/out any flashing leds?

If you have h/w support, I'd place a call to resolve if none of these suggestions work.

I'm sure that the problem w/ the h/w is why you've seen the SCSI bus reset.

Good luck!

[Eugeny Brychkov]

Looks like it's D-class server. As soon as drive is external I would check if device is really connected there first. Then cables and termination and other connected device (SCSI id conflicts etc)
Eugeny

[kenny chia]

hmm..I did not notice the NO H/W
Under SAM there is an action called "Diagnose Missing Tape Drive". Will this cause SAM to redetect the DLT drive?

[Denver Osborn]

I'm not sure using SAM to 'diagnose missing tape drive' will help at all.

If you have found the tape drive was powered off or another issue, try ioscan after making the corrections. If the drive is avaialble, ioscan should pick it up as claimed.

# ioscan -fnCtape

-denver