Parity Error -- lbolt

[Carina Calarco]

Hi All ~~
I've seen a few posts about lbolt but not with the specific Parity Error that we are receiving. The error shows up in syslog when I try to read from an LTO tape. The writes don't give an error but the read gives Tar: tape read error.
HP-UX 11.00 on HP C360.

Jul 24 15:41:24 hp40 vmunix: SCSI: Parity error -- lbolt: 39026, dev: cd008000
Jul 24 15:41:24 hp40 vmunix: lbp->state: 4060
Jul 24 15:41:24 hp40 vmunix: lbp->offset: ffffffff
Jul 24 15:41:24 hp40 vmunix: lbp->uPhysScript: f2ffe000
Jul 24 15:41:24 hp40 vmunix: From most recent interrupt:
Jul 24 15:41:24 hp40 vmunix: ISTAT: 0a, SIST0: 11, SIST1: 00, DSTAT: 80, DSPS: 00500140
Jul 24 15:41:24 hp40 vmunix: lsp: 928b680
Jul 24 15:41:24 hp40 vmunix: bp->b_dev: cd008000
Jul 24 15:41:24 hp40 vmunix: scb->io_id: 223a
Jul 24 15:41:24 hp40 vmunix: scb->cdb: 08 00 00 28 00 00
Jul 24 15:41:24 hp40 vmunix: lbolt_at_timeout: 0, lbolt_at_start: 0
Jul 24 15:41:24 hp40 vmunix: lsp->state: 5
Jul 24 15:41:24 hp40 vmunix: lbp->owner: 0
Jul 24 15:41:24 hp40 vmunix: scratch_lsp: 928b680
Jul 24 15:41:24 hp40 vmunix: Pre-DSP script dump [73b6000]: 09000038 07f00f80
Jul 24 15:41:24 hp40 vmunix: Script dump [73b6008]:
Jul 24 15:41:24 hp40 vmunix: 090027c0 00500140 09000008 07f00fc0
Jul 24 15:41:24 hp40 vmunix: e25c0004 f2ffe7ac 80080000 f2ffe090

Thanks,
Carina

[Shannon Petry]

This is usually caused by bad devices, mos commonly seen in disks. If you search the forums you will probably find a way to decrypt the device having problems.

This may be the tape drive, or could be another device in the chain erroring when the tape drive is active (still the tape drive causing the errors more than likely though).

If you think the tape is not the cause, see that the device chain is properly terminated and if this fixes the problem.

Regards,
Shannon

[Carina Calarco]

The tape device is the only thing attached ... and the terminator is installed on the unused connector...
Thanks for your reply,
Carina

[melvyn burnard]

This looks like yopu are having a hardware issue. I would suggest checking the cable is seated correctly, that the terminator is ok., and that you have no bent pins on any of the cables/connectors etc.
failing that, you may have to replace the device.

[Vincent Farrugia]

Hello,

Can you give us the output of ioscan -fnk? Seems like device c0t8d0 is giving problems.

HTH,
Vince

[Vincent Farrugia]

Hello,

Can you give us the output of ioscan -fnk? Seems like device c0t8d0 is giving problems.

HTH,
Vince

[Carina Calarco]

Hi Vince ~~
I have no doubt that it is my brand new, just-out-of-the-box Ultrium drive. Here is my ioscan... the fact that I'm getting this error on a brand new device is driving me nuts. I want to rule out an error on my part before I go back to the vendor and request a replacement.
Thanks for your time,
Carina

H/W Path Class Description
===================================================
bc
8 bc I/O Adapter
8/0 ba GSCtoPCI Bridge
8/0/3/0 ext_bus Ultra Wide SCSI
8/0/3/0.5 target
8/0/3/0.5.0 disk SEAGATE ST32430W
8/0/3/0.7 target
8/0/3/0.7.0 ctl Initiator
8/0/19/0 ext_bus Ultra Wide SCSI
8/0/19/0.6 target
8/0/19/0.6.0 disk SEAGATE ST19171W
8/0/19/0.7 target
8/0/19/0.7.0 ctl Initiator
8/0/19/0.8 target
8/0/19/0.8.0 tape SEAGATE ULTRIUM06242-XXX
8/0/20/0 lan HP PCI 10/100Base-TX Core
8/0/63 tty Built-in RS-232C
8/16 ba Core I/O Adapter
8/16/0 ext_bus Built-in Parallel Interface
8/16/1 audio Built-in Audio
8/16/4 tty Built-in RS-232C
8/16/5 ext_bus Built-in SCSI
8/16/5.7 target
8/16/5.7.0 ctl Initiator
8/16/7 ps2 Built-in Keyboard/Mouse
10 bc I/O Adapter
10/0 ba GSCtoPCI Bridge
10/0/2/0 ext_bus Ultra2 Wide SCSI
10/0/2/0.0 target
10/0/2/0.0.0 disk WSI FLASHDISK
10/0/2/0.7 target
10/0/2/0.7.0 ctl Initiator
10/0/4/0 graphics PCI Display (103c1005)
32 processor Processor
49 memory Memory

[Vincent Farrugia]

Hello,

From ioscan it seems like your Ultrium drive is an i one, not an e one (internal not external). Is this correct?

Also, it seems that your Ultrium drive is connected with one of your harddisks (on the same SCSI chain).

Ultrium drives hate that, they are solitary beings. They are greedy, want the SCSI bus all to themselves.

I think that is your problem.

Connect your Ultrium drive on a separate bus, all for itself.

HTH,
Vince

[Carina Calarco]

Hi Vince ~~
This is an external device attached to the built in Ultra wide connector... apparently the same as the internal disk. Yuk.
Thanks so much...
Carina

[Vincent Farrugia · Accepted solution]

Hello (again),

First of all, sorry for saying incorrectly that your Ultrium drive is an internal one. I didn't know that the SCSI adapter on the Core IO of your C360 is on the same bus as one of your internal buses :-)

Second, to solve your problem, buy a SCSI card and attach it in one of your empty slots in your workstation.

http://www.hp.com/products1/storage/compatibility/hardware/ultrium-hp/index.html

The above link shows that your Ultrium drive requires an additional card in order to work in a C360.

Which card should you buy?

Not a problem. HP recommends the AHA-29160lp ultra 3 wide HBA card.

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg50063&locale=en_US&taskId=8414&taskName=setup%2C+install+%26+configure&prodSeriesId=42921&prodTypeId=12169&prodSeriesName=hp+surestore+ultrium+230+drives&docId=82015

Here are other documents of interest:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg50145&locale=en_US&taskId=8414&taskName=setup%2C+install+%26+configure&prodSeriesId=42921&prodTypeId=12169&prodSeriesName=hp+surestore+ultrium+230+drives&docId=40509

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg50331&locale=en_US&taskId=8414&taskName=setup%2C+install+%26+configure&prodSeriesId=42921&prodTypeId=12169&prodSeriesName=hp+surestore+ultrium+230+drives&docId=106014

If you have further problems let us know, we are happy to help you :-)

HTH,
Vince