[1209] in linux-scsi channel archive
Re: SCSI woes.
daemon@ATHENA.MIT.EDU (scsi@cococo.net)
Thu Jan 2 13:36:29 1997
Date: Thu, 2 Jan 1997 13:30:15 -0500 (EST)
From: <scsi@cococo.net>
To: "J. Sean Connell" <ankh@canuck.gen.nz>
cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.95.970102140914.11603A-300000@balance.canuck.gen.nz>
On Thu, 2 Jan 1997, J. Sean Connell wrote:
> System
> ------
> P166, 128M RAM (EDO)
> Adaptec 2940 (BIOS 1.23b):
> Seagate ST32550N rev. 0021 (2GB Barracuda) x2
> Adaptec 2940UW (BIOS 1.23b):
> originally 2x Seagate ST34371W 4GB Barracudas, but they got zapped by a bad
> SCSI cage power supply; they were replaced with
> Seagate ST32550N rev. 0019 and 0015 2GB Barracudas
> Linux news.iconz.co.nz 2.0.25 #24 Thu Dec 19 16:14:52 NZDT 1996 i586
>
>
> The most recent crash we've had is:
>
> Jan 1 18:47:25 news kernel: SCSI disk error : host 1 channel 0 id 6 lun 0
> return code = 2
> Jan 1 18:47:25 news kernel: scsidisk I/O error: dev 08:30, sector 2884458
> Jan 1 19:33:52 news kernel: SCSI disk error : host 1 channel 0 id 6 lun 0
> return code = 2
> Jan 1 19:33:52 news kernel: scsidisk I/O error: dev 08:30, sector 1704018
> Jan 1 19:33:52 news kernel:
>
> We are aware of the disk problems, and they're only temporary disks until we
> get replacement 4GBs on Friday/Monday. However, we've had it blow up in any
> number of conceivable ways; back when we had the 2 4GBs, the 2940 would get
> itself into some kind of state whereby it was in a continual reset loop until
> I hit the power switch.
May be a coincidence, but had something very similar happen, replaced
everything, but the kitchen sink and one other thing. The CPU fan went bad
and the P166 was the one that was actually going bonkers. May not be your
problem, but it caused us a fit. We were using the 2940UW when this
happened. Soon as the fan was fixed we ran 24 straight days, then had a
disk failure, which I do believe was a disk failure. Just something to
check.
Later
Kelley
