From owner-freebsd-current Wed Feb 10 08:18:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17401 for freebsd-current-outgoing; Wed, 10 Feb 1999 08:18:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17396 for ; Wed, 10 Feb 1999 08:18:44 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.1/8.9.1) id LAA10090 for current@freebsd.org; Wed, 10 Feb 1999 11:14:38 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199902101614.LAA10090@misha.cisco.com> Subject: Re: Syncing Disks In-Reply-To: from "T.D. Brace" at "Feb 10, 1999 09:41:01 am" To: current@FreeBSD.ORG Date: Wed, 10 Feb 1999 11:14:38 -0500 (EST) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > the disks. This went fine, but when he exited from single user mode, > it again hangs on syncing disks. This is a brand new machine, worked > great for about 6 weeks - and this is the second machine to do this since > the first of the year. I had a similar problem when I upgraded to the December's 3.0 current from February _96_ 3.0 current. Even after a clean shutdown, the root filesystem would need TWO consecutive fsck-s to become mountable -- always. I ended up backing up and remaking the FS, after which the problem went away. This was all very painfull, because the machine is 486SX25 :) IDE disk -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message