Re: SCSI Error when connect tape drive (534 Views)
Reply
Occasional Contributor
Posts: 4
Registered: ‎04-04-2013
Message 1 of 7 (574 Views)

SCSI Error when connect tape drive

Hi Gurus,

I've a problem in my 9000/800/A500-6X (RP2450) server. When I tried to connect DS40 tape drive, it didn't show any tape drive attached after ioscan. But on dmesg it shows the error as below:

 

# dmesg

Nov 28 14:25
...
SIST0: 00 SIEN1: 97 SIEN0: 8f
44: GPCNTL: 2f MACNTL: 00 SWIDE: 00 SLPAR: 00
48: RESPID1: 00 RESPID0: 80 STIME1: 00 STIME0: fc
4c: STEST3: 80 STEST2: 00 STEST1: 0c STEST0: 07
50: RESV50: 00 RESV51: c0 SIDL1: 00 SIDL0: 29
54: CCNTL1: 01 CCNTL0: 00 SODL1: 00 SODL0: 00
58: RESV58: 00 RESV59: 00 SBDL1: 00 SBDL0: 00
5c: SCRATCHB: 00030001
60: SCRATCHC: c0ffffff
64: SCRATCHD: 00121100
68: SCRATCHE: fb7fcc00
6c: SCRATCHF: 00120000
70: SCRATCHG: 00030201
74: SCRATCHH: 00125700
78: SCRATCHI: ff057700
7c: SCRATCHJ: 01005840
bc: SCNTL4: 00
PCI configuration register dump:
Command: 0157
Latency Timer: ff
Cache Line Size: 10

SCSI: Resetting SCSI -- lbolt: 95836715, bus: 6 path: 0/6/2/0

SCSI: Reset detected -- lbolt: 95836715, bus: 6 path: 0/6/2/0
SCSI: Ultra160 Controller at 0/6/2/0: Error: The domain validation test for target 3 determined that communication may not be possible to this target. Verify the hardware configuration.
SCSI: isrEscape Controller at 0/6/2/0.

SCSI: Parity error -- lbolt: 95837015, dev: cb063000
lbp->state: 30008
lbp->offset: ffffffff
lbp->nominalOffset: 3f0
lbp->Cmdindex: 1
lbp->last_nexus_index: 0
lbp->nexus_index: 0
uCmdSent: 1005840 uNexus_index: 0
lbp->puStatus [00000000401ad700]:
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
From most recent interrupt:
ISTAT: 0a, SIST0: c1, SIST1: 00, DSTAT: 80, DSPS: 00000000
lsp: 0x00000000401a11b0
bp->b_dev: cb063000
scb->io_id: 64204e4
scb->cdb: 12 00 00 00 24 00
lbolt_at_timeout: 0, lbolt_at_start: 0
lsp->state: 4005
Jump Table entry [00000000401a8300]: ff011300 00121140
lsp->puScript [00000000401a9140]:
09000008 001f0f00 00000000 0900001c
002309c0 00000000 78370000 00000000
DSAtbl->host_iocb_index: 1
DSAtbl->host_iocb_addr: 125840
stored scratcha: 0xff035300
scratch_lsp: 0x00000000401a11b0
c8xx_iocb [fffffffffb7fcb00]:
01005840 ff007300 00121140 77030000
00000005 00125820 00000006 00125828
Pre-DSP script dump [00000000401a9124]:
78370000 00000000 80080000 fb7fc240
00000000 00000000 00000000 09000008
Script dump [00000000401a9144]:
001f0f00 00000000 0900001c 002309c0
00000000 78370000 00000000 80080000
NCR chip register dump for: 0x400200a
00: SCNTL3: 77 SCNTL2: 80 SCNTL1: 10 SCNTL0: da
04: GPREG: 0a SDID: 03 SXFER: 00 SCID: 47
08: SBCL: ae SSID: 00 SOCL: 09 SFBR: 01
0c: SSTAT2: 08 SSTAT1: 0e SSTAT0: 01 DSTAT: 80
10: DSA: fb7fcb00
14: MBOX1: 00 MBOX0: 00 ISTAT1: 00 ISTAT: 08
18: CTEST3: 01 CTEST2: 30 CTEST1: 00 CTEST0: ff
1c: TEMP: 00121140
20: CTEST6: 00 CTEST5: 24 CTEST4: 08 DFIFO: 03
24: DCMDDBC: 09000003 28: DNAD: 001f0f08
2c: DSP: 0012114c
30: DSPS: 001f0f00
34: SCRATCHA: ff035300
38: DCNTL: a1 DWT: 00 DIEN: 7f DMODE: 4c
3c: ADDER: 0031204c
40: SIST1: 00 SIST0: 00 SIEN1: 97 SIEN0: 8f
44: GPCNTL: 2f MACNTL: 00 SWIDE: 00 SLPAR: 00
48: RESPID1: 00 RESPID0: 80 STIME1: 00 STIME0: fc
4c: STEST3: 80 STEST2: 00 STEST1: 0c STEST0: 07
50: RESV50: 00 RESV51: c0 SIDL1: 00 SIDL0: 29
54: CCNTL1: 01 CCNTL0: 00 SODL1: 00 SODL0: 00
58: RESV58: 00 RESV59: 00 SBDL1: 00 SBDL0: 00
5c: SCRATCHB: 00030001
60: SCRATCHC: c0ffffff
64: SCRATCHD: 00121140
68: SCRATCHE: fb7fcc00
6c: SCRATCHF: 00120000
70: SCRATCHG: 00030201
74: SCRATCHH: 00125700
78: SCRATCHI: ff057700
7c: SCRATCHJ: 01005840
bc: SCNTL4: 00
PCI configuration register dump:
Command: 0157
Latency Timer: ff
Cache Line Size: 10

SCSI: Resetting SCSI -- lbolt: 95837115, bus: 6 path: 0/6/2/0

SCSI: Reset detected -- lbolt: 95837115, bus: 6 path: 0/6/2/0
SCSI: Ultra160 Controller at 0/6/2/0: Error: The domain validation test for target 3 determined that communication may not be possible to this target. Verify the hardware configuration.
#

 

I had:

 

1) Swapped with other tape drive. But the problem still persist.

2) Changed the SCSI card. Also don't resolve the issue.

 

I'm really glad if you guys can give me some idea.

 

Thanks.

Highlighted
Honored Contributor
Posts: 511
Registered: ‎10-31-2002
Message 2 of 7 (534 Views)

Re: SCSI Error when connect tape drive

Sounds for me like a faulty cable, wrong adressing or bad termination but to be honest that is a nice "older" setup so that I cannot really find lot of documentation to provide some really riliable information.

 

Of course you can check firmware, drivers etc. that they are on the lastest release but I'm not sure if that will help.

Honored Contributor
Posts: 14,404
Registered: ‎05-29-2000
Message 3 of 7 (529 Views)

Re: SCSI Error when connect tape drive

DS40 tape drive?

 

Is this an HP product? Perhaps a DLT40 or perhaps a DAT40?

 

The errors indicate that either the cable or terminator is defective. The card can't communicate using the current cable. Are you using an Ultra160/320 style terminator?

Frequent Visitor
Posts: 4
Registered: ‎08-27-2012
Message 4 of 7 (490 Views)

Re: SCSI Error when connect tape drive

Hi Bill,

Sorry my bad. The tape drive is HP DAT40. I'm using Ultra160 terminator. The problem still persist. Below are the action that I already took:

 

1) Change the tape drive.

2) Move the tape drive into other SCSI slot.

3) Change the SCSI cable.

 

But the server still cannot detect  the tape drive.

 

Please find attached syslog.log, dmesg and also list of patches that I captured.

Honored Contributor
Posts: 14,404
Registered: ‎05-29-2000
Message 5 of 7 (485 Views)

Re: SCSI Error when connect tape drive

Is this a HP DAT40 drive?

What else do you have conected to this cable besides the tape drive?

The errors are catastrophic SCSI communication problems.

Try connecting the cable to another SCSI card with power off on the server.

 

NOTE: Ultra160/320 cards are much more sensitive (read: easily confused) than older SCSI cards. Tape drives should not be connected or disconnected with power on. This was a very important rule many years ago and it is still valid today. Note that many of us have gotten away with swapping tape drive SCSI cables in recent years but newer systems such as Itanium seem to be much more fragile. Also note that non-HP branded tape drives may also be an issue.

Frequent Visitor
Posts: 4
Registered: ‎08-27-2012
Message 6 of 7 (481 Views)

Re: SCSI Error when connect tape drive

The tape drive connected into single port SCSI card. I will get downtime and perform the action you suggested. I will update the findings here later.

From the note you gave, the tape drive need to turn off first, delete the path (using mksf) and then pull out the cable, right? Thanks for the info

Thanks.
Honored Contributor
Posts: 14,404
Registered: ‎05-29-2000
Message 7 of 7 (465 Views)

Re: SCSI Error when connect tape drive

Not quite.

You need to turn off the tape drive *and* the computer.

Change the cable, then power up the tape drive and finally, the computer can be turned on.

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.