Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

SCSI Reset on DLT8000

SOLVED
Go to solution
catastro
Super Advisor

SCSI Reset on DLT8000

Hi to all. I have an issue that I don´t know now where the problem is.
I have a L3000 class server running HP-UX 11iv1 with a TapeArray 5300 connected to it, and with two units. A DDS3 tape that is working just fine and a DLT8000 tape drive that is driving me crazy.
It does work sometimes. I already changed the SCSI card, the TapeArray, cables, terminator and unit. The SCSI id in the back of the array are correctly set.
When I try to run the DLT with tar, it writes, but when I try to extarct, it says Tape I/O error (and the tape is brand new).
I tried the tape with the cables and card of the DDS3 and it worked fine.
I think it can be caused because of the PCI bus the SCSI card is in, isn´t it? How could I see if the SCSI Bus is sending resets?
By the way, the DLT drive appears now in the ioscan as NO_HW.
Thanks to all
19 REPLIES
Luk Vandenbussche
Honored Contributor

Re: SCSI Reset on DLT8000

NO_HW => Not OK

Is the DLT direct connected to a PCI a card? Or is it a daisy-chain with a DDS3

The best is a direct connection.

You have replaced everything, but did you replace also the DLT once?
catastro
Super Advisor

Re: SCSI Reset on DLT8000

The DLT is directly connected to the PCI card, and yes, I replaced the drive already twice and still fails sometimes.
Luk Vandenbussche
Honored Contributor
Solution

Re: SCSI Reset on DLT8000

Have you installed the latest stape cumulative patch?

=> PHKL_34552
catastro
Super Advisor

Re: SCSI Reset on DLT8000

Yes, I already installed it when it first happened to me all this. When I try to use the DLT tape drive, there are messages appearing in the syslog file:

Aug 24 13:25:43 ensnada2 vmunix: SCSI: Unhandled illegal instruction -- lbolt: 1
0144277, dev: cd090000
Aug 24 13:25:43 ensnada2 vmunix: lbp->state: 30008
Aug 24 13:25:43 ensnada2 vmunix: lbp->offset: ffffffff
Aug 24 13:25:43 ensnada2 vmunix: lbp->nominalOffset: 270
Aug 24 13:25:43 ensnada2 vmunix: lbp->Cmdindex: 7
Aug 24 13:25:43 ensnada2 vmunix: lbp->last_nexus_index: 45
Aug 24 13:25:43 ensnada2 vmunix: lbp->nexus_index: 46
Aug 24 13:25:43 ensnada2 vmunix: uCmdSent: 70059c0 uNexus_offset:
105718
Aug 24 13:25:43 ensnada2 vmunix: last lbp->puStatus [0000000068b456f8]:
Aug 24 13:25:43 ensnada2 vmunix: 00031000 00031000 00031000 00031
000
Aug 24 13:25:43 ensnada2 vmunix: next lbp->puStatus [0000000068b45708]:
Aug 24 13:25:43 ensnada2 vmunix: From most recent interrupt:
Aug 24 13:25:43 ensnada2 vmunix: ISTAT: 09, SIST0: 00, SIST1: 00,
DSTAT: 81, DSPS: 00000000
Aug 24 13:25:43 ensnada2 vmunix: lsp: 0x0000000073667e00
Aug 24 13:25:43 ensnada2 vmunix: 00031000 00031000 00031000 00031
000
Aug 24 13:25:43 ensnada2 vmunix: bp->b_dev: cd090000
Aug 24 13:25:43 ensnada2 vmunix: scb->io_id: 9000c1d
Aug 24 13:25:43 ensnada2 vmunix: scb->cdb: 08 00 00 28 00 00
Aug 24 13:25:43 ensnada2 vmunix: lbolt_at_timeout: 0, lbolt_at_st
art: 0
Aug 24 13:25:43 ensnada2 vmunix: lsp->state: 4005
Aug 24 13:25:43 ensnada2 vmunix: Jump Table entry [0000000068b40000]: ff0
11000 00101100
Aug 24 13:25:43 ensnada2 vmunix: lsp->puScript [0000000068b41000]:
Aug 24 13:25:43 ensnada2 vmunix: 09000030 002b8b80 00000000 09000
840
Aug 24 13:25:43 ensnada2 vmunix: 294977c0 0000af01 09001000 f3420
000
Aug 24 13:25:43 ensnada2 vmunix: DSAtbl->host_iocb_index: 7
Aug 24 13:25:43 ensnada2 vmunix: DSAtbl->host_iocb_addr: 1059c0
Aug 24 13:25:43 ensnada2 vmunix: stored scratcha: 0xff031000
Aug 24 13:25:43 ensnada2 vmunix: scratch_lsp: 0x0000000073667e00
Aug 24 13:25:43 ensnada2 vmunix: c8xx_iocb [ffffffff87fdeb00]:
Aug 24 13:25:43 ensnada2 vmunix: 070059c0 ff001000 00101100 5f000
f00
Aug 24 13:25:43 ensnada2 vmunix: 00000001 001059a0 00000006 00105
9a8
Aug 24 13:25:43 ensnada2 vmunix: c8xx_virt(DSP) is NULL
Aug 24 13:26:07 ensnada2 vmunix:
Aug 24 13:26:07 ensnada2 vmunix: SCSI: Unhandled illegal instruction -- lbolt: 1
0146698, dev: cd090000
Aug 24 13:26:07 ensnada2 vmunix: lbp->state: 30008
Aug 24 13:26:07 ensnada2 vmunix: lbp->offset: ffffffff
Aug 24 13:26:07 ensnada2 vmunix: lbp->nominalOffset: 270
Aug 24 13:26:07 ensnada2 vmunix: lbp->Cmdindex: c
Aug 24 13:26:07 ensnada2 vmunix: lbp->last_nexus_index: a
Aug 24 13:26:07 ensnada2 vmunix: lbp->nexus_index: b
Aug 24 13:26:07 ensnada2 vmunix: uCmdSent: c005b00 uNexus_offset:
10562c
Aug 24 13:26:07 ensnada2 vmunix: last lbp->puStatus [0000000068b4560c]:
Aug 24 13:26:07 ensnada2 vmunix: 00031000 00031000 00031000 00031
000
Aug 24 13:26:07 ensnada2 vmunix: next lbp->puStatus [0000000068b4561c]:
Aug 24 13:26:07 ensnada2 vmunix: From most recent interrupt:
Aug 24 13:26:07 ensnada2 vmunix: ISTAT: 09, SIST0: 00, SIST1: 00,
DSTAT: 81, DSPS: 00000000
Aug 24 13:26:07 ensnada2 vmunix: lsp: 0x00000000719acc00
Aug 24 13:26:07 ensnada2 vmunix: 00031000 00031000 00031000 00031
000
Aug 24 13:26:07 ensnada2 vmunix: bp->b_dev: cd090000
Aug 24 13:26:07 ensnada2 vmunix: scb->io_id: 9000d2b
Aug 24 13:26:07 ensnada2 vmunix: scb->cdb: 08 00 00 28 00 00
Aug 24 13:26:07 ensnada2 vmunix: lbolt_at_timeout: 0, lbolt_at_st
art: 0
Aug 24 13:26:07 ensnada2 vmunix: lsp->state: 4005
Aug 24 13:26:07 ensnada2 vmunix: Jump Table entry [0000000068b40000]: ff0
11000 00101100
Aug 24 13:26:07 ensnada2 vmunix: lsp->puScript [0000000068b41000]:
Aug 24 13:26:07 ensnada2 vmunix: 09000030 00268380 00000000 09000
840
Aug 24 13:26:07 ensnada2 vmunix: 359a77c0 00009081 09001000 369e8
000
Aug 24 13:26:07 ensnada2 vmunix: DSAtbl->host_iocb_index: c
Aug 24 13:26:07 ensnada2 vmunix: DSAtbl->host_iocb_addr: 105b00
Aug 24 13:26:07 ensnada2 vmunix: stored scratcha: 0xff031000
Aug 24 13:26:07 ensnada2 vmunix: scratch_lsp: 0x00000000719acc00
Aug 24 13:26:07 ensnada2 vmunix: c8xx_iocb [ffffffff87fdeb00]:
Aug 24 13:26:07 ensnada2 vmunix: 0c005b00 ff001000 00101100 5f000
f00
Aug 24 13:26:07 ensnada2 vmunix: 00000001 00105ae0 00000006 00105
ae8
Aug 24 13:26:07 ensnada2 vmunix: c8xx_virt(DSP) is NULL
Aug 24 13:26:07 ensnada2 vmunix:
Aug 24 13:26:07 ensnada2 vmunix: SCSI: Unhandled illegal instruction -- lbolt: 1
0146699, dev: cd090000
Aug 24 13:26:07 ensnada2 vmunix: lbp->state: 30008
Aug 24 13:26:07 ensnada2 vmunix: lbp->offset: ffffffff
Aug 24 13:26:07 ensnada2 vmunix: lbp->nominalOffset: 450
Aug 24 13:26:07 ensnada2 vmunix: lbp->Cmdindex: d
Aug 24 13:26:07 ensnada2 vmunix: lbp->last_nexus_index: a
Aug 24 13:26:07 ensnada2 vmunix: lbp->nexus_index: b
Aug 24 13:26:07 ensnada2 vmunix: uCmdSent: d005b40 uNexus_offset:
10562c
Aug 24 13:26:07 ensnada2 vmunix: last lbp->puStatus [0000000068b4560c]:
Aug 24 13:26:07 ensnada2 vmunix: 00031000 00031000 00031000 00031
000
Aug 24 13:26:07 ensnada2 vmunix: next lbp->puStatus [0000000068b4561c]:
Aug 24 13:26:07 ensnada2 vmunix: From most recent interrupt:
Aug 24 13:26:07 ensnada2 vmunix: ISTAT: 09, SIST0: 00, SIST1: 00,
DSTAT: 81, DSPS: 00000000
Aug 24 13:26:07 ensnada2 vmunix: lsp: 0x00000000646af3c8
Aug 24 13:26:07 ensnada2 vmunix: 00031000 00031000 00031000 00031
000
Aug 24 13:26:07 ensnada2 vmunix: bp->b_dev: cd090000
Aug 24 13:26:07 ensnada2 vmunix: scb->io_id: 9000d2c
Aug 24 13:26:07 ensnada2 vmunix: scb->cdb: 12 00 00 00 24 00
Aug 24 13:26:07 ensnada2 vmunix: lbolt_at_timeout: 0, lbolt_at_st
art: 0
Aug 24 13:26:07 ensnada2 vmunix: lsp->state: 4005
Aug 24 13:26:07 ensnada2 vmunix: Jump Table entry [0000000068b40000]: 000
01000 87fde288
Aug 24 13:26:07 ensnada2 vmunix: lsp->puScript [0000000068b41000]:
Aug 24 13:26:07 ensnada2 vmunix: 09000024 00330b80 00000000 78370
000
Aug 24 13:26:07 ensnada2 vmunix: 00000000 80080000 87fde288 369e8
000
Aug 24 13:26:07 ensnada2 vmunix: DSAtbl->host_iocb_index: d
Aug 24 13:26:07 ensnada2 vmunix: DSAtbl->host_iocb_addr: 105b40
Aug 24 13:26:07 ensnada2 vmunix: stored scratcha: 0xff031000
Aug 24 13:26:07 ensnada2 vmunix: scratch_lsp: 0x00000000646af3c8
Aug 24 13:26:07 ensnada2 vmunix: c8xx_iocb [ffffffff87fdeb00]:
Aug 24 13:26:07 ensnada2 vmunix: 0d005b40 ff007000 00101100 77000
000
Aug 24 13:26:07 ensnada2 vmunix: 00000005 00105b20 00000006 00105
b28
Aug 24 13:26:07 ensnada2 vmunix: c8xx_virt(DSP) is NULL
Aug 24 13:26:07 ensnada2 vmunix: SCSI: Ultra160 Controller at 0/3/0/0: Error: Th
e domain validation test for target 0 determined that communication may not be p
ossible to this target. Verify the hardware configuration.
Aug 24 13:27:06 ensnada2 vmunix:
Aug 24 13:27:06 ensnada2 vmunix: SCSI: Unhandled illegal instruction -- lbolt: 1
0152565, dev: cd090000
Aug 24 13:27:06 ensnada2 vmunix: lbp->state: 30008
Aug 24 13:26:07 ensnada2 vmunix: SCSI: Ultra160 Controller at 0/3/0/0: Error: Th
e domain validation test for target 0 determined that communication may not be p
ossible to this target. Verify the hardware configuration.
Aug 24 13:27:06 ensnada2 vmunix: lbp->offset: ffffffff
Aug 24 13:27:06 ensnada2 vmunix: lbp->nominalOffset: 270
Aug 24 13:27:06 ensnada2 vmunix: lbp->Cmdindex: d
Aug 24 13:27:06 ensnada2 vmunix: lbp->last_nexus_index: b
Aug 24 13:27:06 ensnada2 vmunix: lbp->nexus_index: c
Aug 24 13:27:06 ensnada2 vmunix: uCmdSent: d005b40 uNexus_offset:
105630
Aug 24 13:27:06 ensnada2 vmunix: last lbp->puStatus [0000000068b45610]:
Aug 24 13:27:06 ensnada2 vmunix: 00031000 00031000 00031000 00031
000
Aug 24 13:27:06 ensnada2 vmunix: next lbp->puStatus [0000000068b45620]:
Aug 24 13:27:06 ensnada2 vmunix: From most recent interrupt:
Aug 24 13:27:06 ensnada2 vmunix: ISTAT: 09, SIST0: 00, SIST1: 00,
DSTAT: 81, DSPS: 00000000
Aug 24 13:27:06 ensnada2 vmunix: lsp: 0x0000000073667e00
Aug 24 13:27:06 ensnada2 vmunix: 00031000 00031000 00031000 00031
000
Aug 24 13:27:06 ensnada2 vmunix: bp->b_dev: cd090000
Aug 24 13:27:06 ensnada2 vmunix: scb->io_id: 9000e3a
Aug 24 13:27:06 ensnada2 vmunix: scb->cdb: 08 00 00 28 00 00
Aug 24 13:27:06 ensnada2 vmunix: lbolt_at_timeout: 0, lbolt_at_st
art: 0
Aug 24 13:27:06 ensnada2 vmunix: lsp->state: 4005
Aug 24 13:27:06 ensnada2 vmunix: Jump Table entry [0000000068b40000]: ff0
11000 00101100
Aug 24 13:27:06 ensnada2 vmunix: lsp->puScript [0000000068b41000]:
Aug 24 13:27:06 ensnada2 vmunix: 09000030 00260180 00000000 09000
840
Aug 24 13:27:06 ensnada2 vmunix: bee2b7c0 00009802 09001000 b70e0
000
Aug 24 13:27:06 ensnada2 vmunix: DSAtbl->host_iocb_index: d
Aug 24 13:27:06 ensnada2 vmunix: DSAtbl->host_iocb_addr: 105b40
Aug 24 13:27:06 ensnada2 vmunix: stored scratcha: 0xff031000
Aug 24 13:27:06 ensnada2 vmunix: scratch_lsp: 0x0000000073667e00
Aug 24 13:27:06 ensnada2 vmunix: c8xx_iocb [ffffffff87fdeb00]:
Aug 24 13:27:06 ensnada2 vmunix: 0d005b40 ff001000 00101100 77000
000
Aug 24 13:27:06 ensnada2 vmunix: 00000001 00105b20 00000006 00105
b28
Aug 24 13:27:06 ensnada2 vmunix: c8xx_virt(DSP) is NULL
Aug 24 13:31:21 ensnada2 sshd[8072]: Rhosts authentication refused for rootsc: b
ad ownership or modes for home directory.
Aug 24 13:31:21 ensnada2 sshd[8072]: Accepted keyboard-interactive/pam for roots
c from 10.57.224.72 port 56677 ssh2
Aug 24 13:32:15 ensnada2 vmunix:
Aug 24 13:32:15 ensnada2 vmunix: SCSI: Unhandled illegal instruction -- lbolt: 1
0183513, dev: cd090000
Aug 24 13:31:21 ensnada2 sshd[8072]: Rhosts authentication refused for rootsc: b
ad ownership or modes for home directory.
Aug 24 13:32:15 ensnada2 vmunix: lbp->state: 30008
Aug 24 13:32:15 ensnada2 vmunix: lbp->offset: ffffffff
Aug 24 13:32:15 ensnada2 vmunix: lbp->nominalOffset: 270
Aug 24 13:32:15 ensnada2 vmunix: lbp->Cmdindex: 17
Aug 24 13:32:15 ensnada2 vmunix: lbp->last_nexus_index: 15
Aug 24 13:32:15 ensnada2 vmunix: lbp->nexus_index: 16
Aug 24 13:32:15 ensnada2 vmunix: uCmdSent: 17005dc0 uNexus_offset
: 105658
Aug 24 13:32:15 ensnada2 vmunix: last lbp->puStatus [0000000068b45638]:
Aug 24 13:32:15 ensnada2 vmunix: 00031000 00031000 00031000 00031
000
Aug 24 13:32:15 ensnada2 vmunix: next lbp->puStatus [0000000068b45648]:
Aug 24 13:32:15 ensnada2 vmunix: From most recent interrupt:
Aug 24 13:32:15 ensnada2 vmunix: ISTAT: 09, SIST0: 00, SIST1: 00,
DSTAT: 81, DSPS: 00000000
Aug 24 13:32:15 ensnada2 vmunix: lsp: 0x0000000071a13800
Aug 24 13:32:15 ensnada2 vmunix: 00031000 00031000 00031000 00031
000
Aug 24 13:32:15 ensnada2 vmunix: bp->b_dev: cd090000
Aug 24 13:32:15 ensnada2 vmunix: scb->io_id: 9001516
Aug 24 13:32:15 ensnada2 vmunix: scb->cdb: 08 00 00 28 00 00
Aug 24 13:32:15 ensnada2 vmunix: lbolt_at_timeout: 0, lbolt_at_st
art: 0
Aug 24 13:32:15 ensnada2 vmunix: lsp->state: 4005
Aug 24 13:32:15 ensnada2 vmunix: Jump Table entry [0000000068b40000]: ff0
11000 00101100
Aug 24 13:32:15 ensnada2 vmunix: lsp->puScript [0000000068b41000]:
Aug 24 13:32:15 ensnada2 vmunix: 09000030 00298b80 00000000 09000
840
Aug 24 13:32:15 ensnada2 vmunix: f607f7c0 0000b782 09001000 f1ea8
000
Aug 24 13:32:15 ensnada2 vmunix: DSAtbl->host_iocb_index: 17
Aug 24 13:32:15 ensnada2 vmunix: DSAtbl->host_iocb_addr: 105dc0
Aug 24 13:32:15 ensnada2 vmunix: stored scratcha: 0xff031000
Aug 24 13:32:15 ensnada2 vmunix: scratch_lsp: 0x0000000071a13800
Aug 24 13:32:15 ensnada2 vmunix: c8xx_iocb [ffffffff87fdeb00]:
Aug 24 13:32:15 ensnada2 vmunix: 17005dc0 ff001000 00101100 5f000
f00
Aug 24 13:32:15 ensnada2 vmunix: 00000001 00105da0 00000006 00105
da8
Aug 24 13:32:15 ensnada2 vmunix: c8xx_virt(DSP) is NULL

And as I said before, when I put the dirve in the SCSI attached to the DDS drive (I disconnected the DDS tape in order to do this), I started the LTT drive test, and told me everything was fine and tries a tar and everything worked fine also.
Any ideas?
Arend Lensen
Trusted Contributor

Re: SCSI Reset on DLT8000

Please get an LTT support ticket and post it here...
tkc
Esteemed Contributor

Re: SCSI Reset on DLT8000

hi catastro, I suspect there could be an issue with the Tape Array 5300 backplane, since you have replaced the DLT8000 drive twice. If you do not have part for the tape array 5300, try swapping the position of the dds drive and the dlt8000 drive. remember to swap the scsi cable as well and set the scsi id accordingly at the rear of the tape array 5300.
catastro
Super Advisor

Re: SCSI Reset on DLT8000

Hi. I already swapped the positions of the DLT and DDS drive in the TapeArray and seemed to work fine, but some time after that, again with the same issue. I changed the TapeArray at least twice as well, the SCSI card once and the cable and terminator as well.
The LTT assesment test told me everything was working just fine, with no problems at all.
I am going to change the SCSI PCI slot to keep looking for a solution.
catastro
Super Advisor

Re: SCSI Reset on DLT8000

Hi again. I chenged the PCI slot where the SCSI card was, and now the DLT drive appears as claimed, but still giving me errors.
I tried to do a tar on a tape, and it tells copies to the tape correctly, but I can not list all the contents or extract them. It says me this:

Tar: tape error (5)

And in the syslog file appears this lines, and I am not sure if them are pointing to the SCSI card.

Aug 28 09:24:29 ensnada2 vmunix: SCSI: Ultra160 Controller at 0/5/0/0: Error: Th
e domain validation test for target 0 determined that communication may not be p
ossible to this target. Verify the hardware configuration.
Aug 28 09:27:22 ensnada2 vmunix:
Aug 28 09:27:22 ensnada2 vmunix: SCSI: Unhandled illegal instruction -- lbolt: 8
0622, dev: cd170040
Aug 28 09:27:22 ensnada2 vmunix: lbp->state: 30008

Here is the ioscan output:

Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 3 0/5/0/0.0.0 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/3m /dev/rmt/c23t0d0BEST
/dev/rmt/3mb /dev/rmt/c23t0d0BESTb
/dev/rmt/3mn /dev/rmt/c23t0d0BESTn
/dev/rmt/3mnb /dev/rmt/c23t0d0BESTnb
tkc
Esteemed Contributor

Re: SCSI Reset on DLT8000

can you verify if the system is applied with the following patch ?

PHKL_34552 : s700_800 11.11 SCSI Tape (stape) cumulative
tkc
Esteemed Contributor

Re: SCSI Reset on DLT8000

besides that, apply the following patches as well :

PHKL_34815 : s700_800 11.11 SCSI IO Cumulative Patch

PHKL_36521 : s700_800 11.11 SCSI Ultra160 Cumulative Patch
tkc
Esteemed Contributor

Re: SCSI Reset on DLT8000

i would also be interested to know what is the scsi terminator you are using. Can you provide the part number indicated on the terminator you are using for the DLT8000 drive?
Arend Lensen
Trusted Contributor

Re: SCSI Reset on DLT8000

Once more:
Please get an LTT support ticket and post it here.Maybe something is wrong with the DLT drive...
catastro
Super Advisor

Re: SCSI Reset on DLT8000

Here is all the information. I am running the test again, and will post the result.

- Test 'Test Script' started on device 'QUANTUM DLT8000' at address
'5.0.0[3-23/0/5/0/0.0.0]'
- Failed
- Operations Log
- Executing Rules Based Analysis (rules file is
/var/tmp/LTT_TAAAa09868.tst)
- executing loop 1 (writable test tape message)
- executing loop 2 (SCSI interconnect)
- executing loop 3 (check firmware revision)
- executing loop 4 (check event logs)
- executing loop 5 (load tape)
- waiting 300 sec. for tape load to finish (0)
- waiting 300 sec. for tape load to finish (5)
- waiting 300 sec. for tape load to finish (10)
- waiting 300 sec. for tape load to finish (15)
- waiting 300 sec. for tape load to finish (20)
- executing loop 6 (quick write/read)
- executing loop 7 (quick write/read)
- executing loop 8 (quick write/read)
- executing loop 8 (quick write/read)
- executing loop 9 (quick write/read)
- executing loop 10 (quick write/read)
- executing loop 11 (quick write/read)
- executing loop 12 (soft unload/load)
- executing loop 13 (soft unload/load)
- executing loop 14 (write/read minimum block size)
- executing loop 15 (write/read minimum block size)
- executing loop 16 (write/read minimum block size)
- executing loop 17 (diag self-test)
- executing loop 18 (bug check 8008)
- executing loop 19 (bug check 8008)
- executing loop 20 (write/read pattern5)
- executing loop 21 (write/read pattern5)
- executing loop 22 (write/read pattern4)
- executing loop 23 (write/read pattern4)
- executing loop 24 (write/read pattern3)
- executing loop 25 (write/read pattern3)
- executing loop 26 (write/read pattern2)
- executing loop 26 (write/read pattern2)
- executing loop 27 (write/read pattern2)
- executing loop 28 (write/read pattern1)
- executing loop 29 (write/read pattern1)
- executing loop 30 (write/read pattern0)
- executing loop 31 (write/read pattern0)
- executing loop 32 (error-rate)
- executing loop 33 (error-rate)
- executing loop 34 (error-rate)
- Test failed
- Analysis Results
- DLT Drive Assessment Test, script version V01.06.2005
- Script is unable to verify if this device is using latest firmware -
revision data was not loaded from web.
- Read command failed at block 26 loop 34 (error-rate)
- Byte2 0x6 SenseCode 0x29 SenseQual 0x2
- - The drive failed the error-rate test.
- - Try the test again with a different tape.
- Total test time: 864 seconds

The terminator: 416709-001 Rev D TSCN 0709
WIDE LVD / SE SCSI

ensnada2:/root#swlist -l patch PHKL_34552
# Initializing...
# Contacting target "ensnada2"...
#
# Target: ensnada2:/
#

# PHKL_34552 1.0 SCSI Tape (stape) cumula
# PHKL_34552.C-INC 1.0 ProgSupport.C-INC
# PHKL_34552.CORE-KRN 1.0 OS-Core.CORE-KRN
# PHKL_34552.CORE2-KRN 1.0 OS-Core.CORE2-KRN
# PHKL_34552.KERN2-RUN 1.0 OS-Core.KERN2-RUN
ensnada2:/root#swlist -l patch PHKL_34815
# Initializing...
# Contacting target "ensnada2"...
#
# Target: ensnada2:/
#

# PHKL_34815 1.0 SCSI IO Cumulative Patch
# PHKL_34815.ADMN-ENG-A-MAN 1.0 OS-Core.ADMN-ENG-A-MAN
# PHKL_34815.C-INC 1.0 ProgSupport.C-INC appli
# PHKL_34815.CORE2-KRN 1.0 OS-Core.CORE2-KRN appli
ensnada2:/root#swlist -l patch PHKL_36521
# Initializing...
# Contacting target "ensnada2"...
#
# Target: ensnada2:/
#

# PHKL_36521 1.0 SCSI Ultra160 Cumulative Patch
# PHKL_36521.CORE2-KRN 1.0 OS-Core.CORE2-KRN applied
# PHKL_36521.KERN2-RUN 1.0 OS-Core.KERN2-RUN applied
tkc
Esteemed Contributor

Re: SCSI Reset on DLT8000

my LVD/SE terminator part is 5183-2657(C2364A). the L&TT test on the drive has failed. you will need to collect the L&TT support ticket for further investigation. something is not right with the setup or the media or the DLT8000 drive itself.
tkc
Esteemed Contributor

Re: SCSI Reset on DLT8000

catastro
Super Advisor

Re: SCSI Reset on DLT8000

I changed the SCSI card and now it is working perfectly and not telling anything at all. Here is the ltt test solution:

- Test 'Test Script' started on device 'QUANTUM DLT8000' at address
'0.0.0[2-0/0/0/1/0.0.0]'
- Passed
- Operations Log
- Executing Rules Based Analysis (rules file is
/var/tmp/LTT_TAAAa07902.tst)
- executing loop 1 (writable test tape message)
- executing loop 2 (SCSI interconnect)
- executing loop 3 (check firmware revision)
- executing loop 4 (check event logs)
- executing loop 5 (load tape)
- waiting 300 sec. for tape load to finish (0)
- waiting 300 sec. for tape load to finish (5)
- waiting 300 sec. for tape load to finish (10)
- waiting 300 sec. for tape load to finish (15)
- waiting 300 sec. for tape load to finish (20)
- waiting 300 sec. for tape load to finish (25)
- waiting 300 sec. for tape load to finish (30)
- waiting 300 sec. for tape load to finish (35)
- waiting 300 sec. for tape load to finish (35)
- waiting 300 sec. for tape load to finish (40)
- waiting 300 sec. for tape load to finish (45)
- waiting 300 sec. for tape load to finish (50)
- waiting 300 sec. for tape load to finish (55)
- waiting 300 sec. for tape load to finish (60)
- waiting 300 sec. for tape load to finish (65)
- waiting 300 sec. for tape load to finish (70)
- waiting 300 sec. for tape load to finish (75)
- waiting 300 sec. for tape load to finish (80)
- executing loop 6 (quick write/read)
- executing loop 7 (quick write/read)
- executing loop 8 (quick write/read)
- executing loop 9 (quick write/read)
- executing loop 10 (quick write/read)
- executing loop 11 (quick write/read)
- executing loop 12 (soft unload/load)
- executing loop 13 (soft unload/load)
- executing loop 14 (write/read minimum block size)
- executing loop 32 (error-rate)
- executing loop 33 (error-rate)
- executing loop 34 (error-rate)
- executing loop 35 (error-rate)
- executing loop 36 (check event logs)
- executing loop 37 (unload tape)
- Test passed
- Analysis Results
- DLT Drive Assessment Test, script version V01.06.2005
- Script is unable to verify if this device is using latest firmware -
revision data was not loaded from web.
- All tests PASSED!
- Total test time: 1204 seconds

In the syslog file nothing appears to be wrong.
Arend Lensen
Trusted Contributor

Re: SCSI Reset on DLT8000

I still have doubts about the drive but if you think its fixed, ok.
catastro
Super Advisor

Re: SCSI Reset on DLT8000

Yes, the drive now is working correctly, and the ltt test says so, I made a tar as well into the tape with no problem, and made an ignite as well and no problem either.
Now, I have put the DDS3 drive with the SCSI card the DLT had before, and is not working. The ioscan knows it´s there, but is not working, nor ltt test, or tar as well.
So, I think the problem is the SCSI card, as the DLT drive is working now well.
I will check tomorrow for Oracle backups in the DLT drive in order to check the last thing.
catastro
Super Advisor

Re: SCSI Reset on DLT8000

After all, I solved the problem changing the SCSI card and some time after that I replaced as well the SCSI terminator as I was having some more SCSI resets after a time without them. Thanks to all for your help