From owner-freebsd-stable@FreeBSD.ORG Fri Aug 8 07:49:46 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CDBB37B401 for ; Fri, 8 Aug 2003 07:49:44 -0700 (PDT) Received: from c011.snv.cp.net (h002.c011.snv.cp.net [209.228.34.215]) by mx1.FreeBSD.org (Postfix) with SMTP id 4D4EE43FDD for ; Fri, 8 Aug 2003 07:49:43 -0700 (PDT) (envelope-from doug@allensystemconsultants.com) Received: (cpmta 15599 invoked from network); 8 Aug 2003 07:49:42 -0700 Received: from 209.228.34.221 (HELO mail.allensystemconsultants.com.criticalpath.net) by smtp.allensystemconsultants.com (209.228.34.215) with SMTP; 8 Aug 2003 07:49:42 -0700 X-Sent: 8 Aug 2003 14:49:42 GMT Received: from [209.175.240.50] by mail.allensystemconsultants.com with HTTP; Fri, 08 Aug 2003 07:49:42 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 To: freebsd-stable@freebsd.org From: doug@allensystemconsultants.com X-Sent-From: doug@allensystemconsultants.com Date: Fri, 08 Aug 2003 07:49:42 -0700 (PDT) X-Mailer: Web Mail 5.5.0-3_sol28 Message-Id: <20030808074942.21306.h008.c011.wm@mail.allensystemconsultants.com.criticalpath.net> Subject: boot with dirty filesystem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2003 14:49:46 -0000 I have a small problem. I've had a machine go down and it came back up with dirty filesystem on /var and /usr. fsck has solved the problem with /var, after 10 times through. fsck seems unable to resolve the inconsistencies with /usr however. fsck is running for the 15th time right now. It looks to me like a probable bad sector on the disk. My question is there a way to force the machine to boot with a dirty filesystem, so that I can pull data from /etc to move to a new disk? Barring that, is there still a procedure to force the system to boot, update the inodes with whatever information it can find, and mark the other files as unreadable? Thanks in advance. Doug Allen