From owner-freebsd-hardware  Mon Mar 31 19:43:05 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA05233
          for hardware-outgoing; Mon, 31 Mar 1997 19:43:05 -0800 (PST)
Received: from dfw-ix16.ix.netcom.com (dfw-ix16.ix.netcom.com [206.214.98.16])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA05196;
          Mon, 31 Mar 1997 19:42:53 -0800 (PST)
Received: (from smap@localhost)
          by dfw-ix16.ix.netcom.com (8.8.4/8.8.4)
	  id VAA28794; Mon, 31 Mar 1997 21:42:09 -0600 (CST)
Received: from wck-ca7-10.ix.netcom.com(204.31.231.42) by dfw-ix16.ix.netcom.com via smap (V1.3)
	id sma028667; Mon Mar 31 21:41:34 1997
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id TAA03903; Mon, 31 Mar 1997 19:40:32 -0800 (PST)
Date: Mon, 31 Mar 1997 19:40:32 -0800 (PST)
Message-Id: <199704010340.TAA03903@silvia.HIP.Berkeley.EDU>
To: chuckr@glue.umd.edu
CC: freebsd-hardware@freebsd.org, scsi@freebsd.org
Reply-to: scsi@freebsd.org
In-reply-to: <Pine.OSF.3.95q.970331212813.1995A-100000@fiber.eng.umd.edu> (message from Chuck Robey on Mon, 31 Mar 1997 21:30:01 -0500 (EST))
Subject: Re: Hard disk problems
From: asami@vader.cs.berkeley.edu (Satoshi Asami)
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

[crossposted to SCSI, with reply set to there]

 * [I sent this message to hackers, where it got no response, so maybe I
 * should have sent it here.  Apologies to those who will have seen it
 * twice.]

I don't read hackers because the noise level is so high. ;)

 * I was wondering if someone can explain the error message I'm suddenly
 * seeing on bootup of one of my systems.  It hangs with the message:
 * 
 * ncr0: SCSI phase error fixup: CCB already dequeued (0xf2467200)
 * ncr0 timeout ccb=f2466600 skip
 * ncr0 timeout ccb=f2466800 skip
 * ncr0 timeout ccb=f2466a00 skip
 * ncr0 timeout ccb=f2467200 skip
 * (hangs here)

I have seen something very similar on my system.  The Micropolis
3243WT (which I got as a replacement to an older 3243W) doesn't boot 3
out of 4 times with "ncr0 timeout" messages (I don't get the "already
dequeued" part, though).  The other two disks (Atlas I and II) don't
have this problem.  Also, removing the CDROM (the only narrow device
in the system) alleviated the symptoms somewhat (booted 3 out of 4
times).

 * I need to know what it means, and if there's any way to recover from it
 * without having to lose the whole disk (my boot disk, darn it!)  I get this
 * error on the system after it does the full fsck (successfully), and the
 * system has (in total) 2 - 2G disks (this is the first one), 1 - 200 meg
 * disk, and one cdrom, all scsi, all hooked to one ncr 825 controller
 * (Tyan).

Well, when I moved the Micropolis to an Adaptec 2940UW, everything
started working again. ;)

Satoshi