On Tue, 28 Mar 2000, Mike Bilow wrote:
> That's a hardware problem. A SCSI parity error is reported by the
> hardware and simply passed up the chain. Unless there is something
> seriously wrong in the aic7xxx sequencer code, which I doubt, this looks
> like a typical cabling and termination issue.
Well, the chassis is an Intel pre-installed rack mountable one with
hot-swappable SCSI backplane. All the cables were there allready connected
to disk racks. All I had to do was to install the disks in the racks and
slide them in.
I think I wasn't able to screw something up there... :/
> Hard to say, but my guess is that your drive has elected to shut down. I
> don't know what devices are on the bus, but the negotiation of aynchronous
> transfers is not a good sign and it may indicated one of the lines is
> being held in a funny state. Are you trying to run slow and fast devices
> on the same SCSI bus?
No, the disks are the only SCSI devices there. No other disk/tape
devices there (except a standard 3,5" floppy, but it really shouldn't
matter).
> I think you have an electrical issue.
I feared that, but what should I do? It's all LVD and all pre-installed by
Intel... except disks, of course.
Besides, it only happens every few weeks even though the machine is
pretty active (in use).
>
> > 19: 358370 359232 IO-APIC-level aic7xxx, aic7xxx
> * * *
> > 1400-14be : aic7xxx
> > 1800-18be : aic7xxx
>
> Are you really running two separate aic7xxx controllers? Do they have the
> same firmware revision?
I guess the motherboard has two chips integrated. I didn't really check
then (now it's off-site), but kernel detects two hosts (scsi0 & scsi1).
The board also features two 68-pin SCSI connectors (the one I use is
marked LVD, the other is marked SE).
Thanks, D.
