Date: Thu, 18 Sep 1997 09:25:00 -0400 (EDT) From: John Dowdal <jdowdal@destiny.erols.com> To: Walter Hafner <hafner@forwiss.tu-muenchen.de> Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Is my NCR controller broken? Message-ID: <Pine.BSF.3.95q.970918090954.1078A-100000@destiny.erols.com> In-Reply-To: <199709180857.IAA03695@pccog4.forwiss.tu-muenchen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
I just dealt with solving the same problem. In fact there were were
several problems.
1) DEC DSP5400S drive dies with a physical media failure
2) Attempt to low level the drive; it fails and the drive powers down [ie
it is dead, Jim]
3) remove the drive from /etc/fstab and run for two weeks with same
physical setup, waiting for replacement.
4) Remove dead drive [internal] and add new drive [external] with correct
termination. Haul dead drive to school, to try using the Solaris
format comand on it. Attempt to remote log into my machine, its dead.
5) Go back home, and messages like you describe. The old good drive
powering up and powering down. Turns out the Y connector is dead.
Remove it. Sigh of releif; not two dead disks in two weeks.
6) Format the DSP5400S. It powers down on the sun too. The grown
defect list is approx 1000; the primary is approx 200. Seems quite
dead...
7) Return home, reconnect the rest of my external chain. Starts to boot,
and dies with error messsages you describe during fsck. *Grumble*
8) Dissect each external case, try all combinations one at a time, turns
out that if I include the CD writer I get the above errors while
fscking. "FunnySCSI" below is the "weird" connector which is on a
SUN-3 shoe box.
[2 internal drives] -> [Computer-HD50] -> [Tape-Centronics] ->
[CDWriter-FunnySCSI] -> [Disk-Centronics]
Next I swapped the tape and disk; same effect
9) Next I bought a Centronics-Centronics cable, to remove the CDWriter
from the chain.
-> this worked fine
10) Broke SCSI spec by terminating the CD writer at the drive, leaving
an illegal stub of cable sticking out of the case [the other FunnySCSI
connector]. Connected this with one funnyscsi->centronics cable ..
-> this seems to work fine
Hopefully this helps somebody with scsi problems :)
John
On Thu, 18 Sep 1997, Walter Hafner wrote:
> Hello!
>
> I just want to make sure I don't miss something before changing my
> mainboard. Please enlighten me.
>
> I run a 486/DX2-66 (ASUS SP-3 with onboard NCR-810 SCSI
> controller). This computer runs for about 3 years now (2.0.5, 2.1.0,
> 2.1.5)
>
> Since about four weeks I keep getting SCSI resets and then the bus is
> dead. No recovery! And it's really strange because the NCR controller
> reports totally different errors before hanging. Here are the error
> reports from the last three crashes (typed in by hand, so the actual
> format may differ):
>
> -------------------------------------------------------------------------------
>
> sd1(ncr0:1:0): internal error: cmd00 != 91=(vdsp[0] >> 24)
> ncr0: timeout ccb=f19fbc00 (skip)
>
> -------------------------------------------------------------------------------
>
> ncr0:1: ERROR (a0:0) (f-28-0) (8/13) @ (260:00000000).
> script cmd=fc00001c.
> reg: da 10 80 13 47 08 01 1f 00 0f 81 28 80 00 00 00.
> ncr0: restart (fatal error).
> sd1(ncr0:1:0): command failed (9ff)@f19fbc00.
> nrc0: timeout ccb=f19fbc00 (skip)
>
> -------------------------------------------------------------------------------
>
> ncr0: SCSI phase error fixup: CCB already dequeued (0xf19fbc00)
> nrc0: timeout ccb=f19fbc00 (skip)
>
> -------------------------------------------------------------------------------
>
> I changed everything:
>
> * disconnected everything except the system drive -> still errors
> * changed cables (three different ones) -> still errors
> * changed termination (two different external ones, internal, different
> termpower sttings etc.) -> still errors
> * turned all devices to 5MB synchr. and finally to acync via
> 'ncrcontrol' -> still errors
> * finally replaced the system drive (old DEC 5200 against new IBM DAHC
> 34330) and put 2.2.1 on it -> still errors. Actually, the errors above
> are from that setup.
>
> The only thing I didn't change was the mainboard.
>
> I'd be glad if anyone can confirm my suspicion that the NCR controller
> has gone nuts. I just can't imagine why ...
>
> I'd also appreciate it very much if someone with more insight than
> myself could explain the error reports to me. I'd especially like to
> know what this 'f19fbc00' means: it shows up in all three errors (what's
> a 'ccb' anyway?)
>
> Thanks in advance!
>
> -Walter
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970918090954.1078A-100000>