SCSI: Target detected parity error

[Gabriel Madoz]

Hello to all !!.
I have urgency on this: we have problems in a HP9000 D270, due to this I attach the syslog file.

We had to change a tape drive (DDS3)part number C1537, after this neither this tape nor the CD-ROM works properly
We thinks that perhaps the SCSI cable is bad, or perhaps the firmware of the tape must be updated...

PLEASE, any who can help would be grateful.

See the attachment...I NEED URGENTLY an answer !!

[Magdi KAMAL]

Hi Gabriel,

As it is urgent, here it is, you can choose one or all :

1. Close any scsi interface which left opened ( with a scsi terminator ).

2. Insure that the tape scsi interface is well connected and not part of the pins.

3. Try to remove the scsi tape drive to see if the problem disapear: if yes then this could be scsi ID is conflecting, if no then the problem is permanant now and you need to check which disk is conflecting :

# ioscan
then
# ioscan -fnkCdisk | more

will list all disks and good ones be CLAIMED.

hear from you later !

Magdi

[Scott_14]

Hello:

I have had this in the past, right after replacing a dlt drive, which was what we thought a hot plugable.

Try to dissconnect the drive as mentioned, but I have had to do a system re-boot, to reset the scsi device/card.

Since it sounds like it was dissconnected, during the change, and I bet if you check your time of the change, against the time of the syslog errors, this may be it.

Please also check on the above answer for the correct id.
but agian, we ran into this on tape drive replacements in the past where a reboot, re-set this and cleared it.

[Scott_14]

check on your ID against the one pulled out.

[Gabriel Madoz]

Hey, first of all thanks for your fast help...

I forgot to say that on the first time we put the scsi tape the jumpers were different from the scsi that we take out.

After that, we put the jumpers on the same position but when we try to use the command tar the system detects a scsi parity error and reboots.

Wouldn't be necessary to update the firmware of the tape or something like that?

Thanks

[Magdi KAMAL]

Hi again,

What's about assigning points for volks !

Thanks
Magdi

[Gabriel Madoz]

I attach other file...
Please see it and give me your impression

[Gabriel Madoz]

When we execute ioscan we have the following detail:

ioscan -fnkCdisk | more
Class I H/W Path Driver S/W State H/W Type Description
=============================================================
disk 3 8/12.0.0 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 5 8/12.0.1 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c0t0d1 /dev/rdsk/c0t0d1
disk 7 8/12.0.2 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c0t0d2 /dev/rdsk/c0t0d2
disk 4 8/12.1.0 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 6 8/12.1.1 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c0t1d1 /dev/rdsk/c0t1d1
disk 8 8/12.1.2 sdisk CLAIMED DEVICE HP C5447A
/dev/dsk/c0t1d2 /dev/rdsk/c0t1d2
disk 0 8/12.5.0 sdisk CLAIMED DEVICE SEAGATE ST34572WC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 8/12.8.0 sdisk CLAIMED DEVICE SEAGATE ST34572WC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0

<(root@ibsup003:dsgceml:/)>
>ioscan
H/W Path Class Description
==============================================
bc
8 bc I/O Adapter
8/4 ba PCI Bus Bridge - GSCtoPCI
8/4/1/0 lan PCI(10110009) -- Built-in #1
8/12 ext_bus GSC add-on Fast/Wide SCSI Interface
8/12.0 target
8/12.0.0 disk HP C5447A
8/12.0.1 disk HP C5447A
8/12.0.2 disk HP C5447A
8/12.1 target
8/12.1.0 disk HP C5447A
8/12.1.1 disk HP C5447A
8/12.1.2 disk HP C5447A
8/12.5 target
8/12.5.0 disk SEAGATE ST34572WC
8/12.7 target
8/12.7.0 ctl Initiator
8/12.8 target
8/12.8.0 disk SEAGATE ST34572WC
8/16 ba Core I/O Adapter
8/16/0 ext_bus Built-in Parallel Interface
8/16/4 tty Built-in RS-232C
8/16/5 ext_bus Built-in SCSI
8/16/5.0 target
8/16/5.0.0 tape HP C1537A
8/16/5.7 target
8/16/5.7.0 ctl Initiator
8/16/6 lan Built-in LAN
8/16/7 ps2 Built-in Keyboard/Mouse
8/20 ba Core I/O Adapter
8/20/2 tty Built-in RS-232C
8/20/5 ba EISA Bus Adapter
10 bc I/O Adapter
32 processor Processor
34 processor Processor
49 memory Memory

[Erik Allaert]

Hola,

I have seen these error messages in the syslog file when we had a cable length that was close to or other the limit. Reduced cable length and problem went away.

Laters

[Sanjay_6]

Hi Gabriel,

Suggest you take out all your terminators on that bus and plug them back in. This should solve your probelm.

Hope this helps.

Regds

[Gabriel Madoz]

Hey Sanjay, I don't understand well your response.
You mean disconnect the scsi tape and cd rom from the scsi cable, reboot to release the scsi id devices, connect again and reboot ??

Thanks

[Gabriel Madoz]

Hello: I saw a procedure to follow and I want your suggestion:

SCSI Parity

All devices on a SCSI bus must be consistent in parity-checking capability. If
any device on the SCSI bus does not generate parity, all devices on the bus,
including the adapter, must not check parity. (Although parity-checking is
selectable, the adapter always generates parity.)
If a SCSI device cannot match the parity-checking capability of other devices on
the bus, it must be installed on a separate SCSI bus.

Changing the Bus Address of a SCSI Device

Step 1
Shut down and halt the system using the /usr/sbin/shutdown -h command. On
systems with powerfail mode, be sure to also turn off the battery backup.

Step 2
TURN OFF the computer and unplug the power cord.

Step 3
Turn off the device.

Step 4
Change the bus ID on the device.

Step 5
Turn on the device.
Power on all SCSI peripherals and allow them to complete their selftest before
powering on the SPU.

Step 6
Turn on your system.

Use of non-Hewlett-Packard peripherals is not supported by Hewlett-Packard's
standard support process.

Any opinion would be grateful appreciated.