K460 problem

[patrick_132]

Jun 17 08:03:09 npgdwm2 vmunix: SCSI: Unexpected Disconnect -- lbolt: 17919, dev: cb01a002, io_id: 1000037
Jun 17 08:03:10 npgdwm2 vmunix:
Jun 17 08:03:10 npgdwm2 vmunix: SCSI: Unexpected Disconnect -- lbolt: 17924, dev: cb01b002, io_id: 1000038
Jun 17 08:03:10 npgdwm2 vmunix:
Jun 17 08:03:10 npgdwm2 vmunix: SCSI: Unexpected Disconnect -- lbolt: 17929, dev: cb01c002, io_id: 1000039
Jun 17 08:03:10 npgdwm2 vmunix:
Jun 17 08:03:10 npgdwm2 vmunix: SCSI: Unexpected Disconnect -- lbolt: 17934, dev: cb01d002, io_id: 100003a
Jun 17 08:03:10 npgdwm2 vmunix:
Jun 17 08:03:10 npgdwm2 vmunix: SCSI: Unexpected Disconnect -- lbolt: 17939, dev: cb01e002, io_id: 100003b
Jun 17 08:03:10 npgdwm2 vmunix:
Jun 17 08:03:10 npgdwm2 vmunix: SCSI: Unexpected Disconnect -- lbolt: 17944, dev: cb01f002, io_id: 100003c
Jun 17 08:03:42 npgdwm2 diagmond[1227]: Exit due to initialization failure

The system was tested on 11I and all devices passed stm testing. the unit was then ignited to 10.2 and the errors started up. any thoughts on what would cause the lbolt on cd' tape and all 4 drives?

I've replaced the drive cage, back plane and cables... Core i/o and system board.

[Joshua Scott]

Patrick,

Actually, lbolt is the number of ticks since the systems was rebooted. Anyway, it looks like you have a device problem. what is connected to the scsi connection on the core I/O (if anything).

If you don't have anything connected, then remove all but the root drive and see if you get any change

Josh

[Jeff Schussele]

Hi patrick,

Unless I'm misreading those errors it appears to me that *everyone* of them is device 203 - sctl. That's normally the tape robot device. So I'd concentrate my troubleshooting there.

HTH,
Jeff

[patrick_132]

Nothing hooked to the Core i/o card.
the xxxxa through xxxxf leads me to belive its hitting the cd, tape, and all 4 internal drives.

[Cheryl Griffin]

Did you check the termination?

[Jeff Schussele]

patrick,

The key info in these errors is:

dev: cb01f002

You translate this as follows. The first two characters are the major number of the device:

cb (hex) = 203 (dec)

#lsdev 203
Character Block Driver Class
203 -1 sctl ctl

sctl is the tape library robot device. The tape drives would be stape & they're 205.
So I'd say you have a problem with the robot. how it's setup or the sctl driver itself.

Rgds,
Jeff

[patrick_132]

Sorry here is the break down on the box's hardware. K460 (2) 180 mhz cpu's
(1) cd rom
(1) dds2
(4) A3353A 4gb drives
(1) HSC expansion with
(4) A2969A scsi adapters.
(2) J2166A's
(4) 256mb mem kits
(2) 128mb mem kits

Terminator on the Core i/o and the A2969A's

no other tape devices than the dds2 hooked to the system.

could a bad dds2 cause an lbolt on all devices on its scsi chain and all devices on the HD scsi chain?

when testing on 11I the cd rom, dds2 and all 4 drives passed stm testing. sence igniting to 10.2 attempts to run stm hang the system.

Is there any chance the lbolt's could be caused by a bad ignite load?

[Jeff Schussele]

Yep - I guess that's a possibility IF the image came from a system that had a tape library.

Does an ioscn -fn return any sctl devices?

Jeff

[patrick_132]

Problem found.

Removed every thing save the root drive and the core i/o, no lbolts.

added the drives back one at a time till all 4 were running, no lbolts.

added the cd rom back no lbolts.

added the tape drive back no lbolts.

added the token ring cards back no lbolts.

added the HCS card back and the lbolts started up again.

Why would the HSC card cause lbolts on devices not even related to it?