From owner-freebsd-bugs Thu Mar 2 14:39:39 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA11896 for bugs-outgoing; Thu, 2 Mar 1995 14:39:39 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id OAA11890 for ; Thu, 2 Mar 1995 14:39:35 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id RAA07315; Thu, 2 Mar 1995 17:37:16 -0500 From: Peter Dufault Message-Id: <199503022237.RAA07315@hda.com> Subject: Re: odd ncr behavior To: rcarter@geli.com (Russell L. Carter) Date: Thu, 2 Mar 1995 17:37:15 -0500 (EST) Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <199503021929.LAA05786@geli.clusternet> from "Russell L. Carter" at Mar 2, 95 11:29:52 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 928 Sender: bugs-owner@FreeBSD.org Precedence: bulk Russell L. Carter writes: > > Is this my drive croaking (my bug), or is it the system? > The following stuff arrives in dmesg (but not > /var/log/messages), when /etc/daily reaches > the line > > fsck -n | grep -v '^\*\* Phase' > > If I run 'fsck -p' I get what looks to be normal > output, at least nothing seems out of the ordinary. > And oddly, it seems to turn up after the system has > been idle for a few hours, like when /etc/daily is run > at 0200. I can load the system heavily for 12 hours > at a time with nary a complaint. asc:04 ascq:01 is "Logical unit is in process of coming ready". I don't know why it isn't ready. I don't know that it will help you, but it would make sense to delay a little bit after that error before retrying. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267