From owner-freebsd-scsi Tue Apr 1 15:19:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA11740 for freebsd-scsi-outgoing; Tue, 1 Apr 1997 15:19:05 -0800 (PST) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA11734 for ; Tue, 1 Apr 1997 15:19:01 -0800 (PST) Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.103.24]) by po1.glue.umd.edu (8.8.5/8.8.5) with ESMTP id SAA26444 for ; Tue, 1 Apr 1997 18:18:44 -0500 (EST) Received: from localhost (chuckr@localhost) by skipper.eng.umd.edu (8.8.5/8.6.4) with SMTP id SAA30171 for ; Tue, 1 Apr 1997 18:18:42 -0500 (EST) X-Authentication-Warning: skipper.eng.umd.edu: chuckr owned process doing -bs Date: Tue, 1 Apr 1997 18:18:41 -0500 (EST) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: scsi@freebsd.org Subject: Re: Hard disk problems In-Reply-To: <199704010340.TAA03903@silvia.HIP.Berkeley.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 31 Mar 1997, Satoshi Asami wrote: > [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. ;) Oh, you're saying it's more likely to be a drive/controller problem than a drive problem? Makes me wish I had an extra controller handy. Did, couple months ago, but I sent it to a friend (I hate seeing hardware go to waste). I was hoping maybe Justin would comment, but maybe he's busy. Hmm, well, I guess I have to go looking through the SCSI sources for some kinda tip as to what's causing it. The system has been in operating shape now for 3 months. Check out http://www/aprilfools.com. Trust me, do it today. It's only an April fools gag today :-) > > Satoshi > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------