From owner-freebsd-questions@FreeBSD.ORG Fri Jan 15 20:33:47 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13DEA1065697 for ; Fri, 15 Jan 2010 20:33:47 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout027.mac.com (asmtpout027.mac.com [17.148.16.102]) by mx1.freebsd.org (Postfix) with ESMTP id 01D038FC08 for ; Fri, 15 Jan 2010 20:33:46 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from cswiger1.apple.com ([17.227.140.124]) by asmtp027.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KWB00C7Y2G7LD30@asmtp027.mac.com> for freebsd-questions@freebsd.org; Fri, 15 Jan 2010 12:33:44 -0800 (PST) From: Chuck Swiger In-reply-to: <757579.431.qm@web52107.mail.re2.yahoo.com> Date: Fri, 15 Jan 2010 12:33:43 -0800 Message-id: <5DC1FB5E-CDA6-4FB9-BB0F-F576A9F9768F@mac.com> References: <757579.431.qm@web52107.mail.re2.yahoo.com> To: gahn X-Mailer: Apple Mail (2.1077) Cc: freebsd general questions Subject: Re: fsck failed to sync inodes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2010 20:33:47 -0000 Hi-- On Jan 15, 2010, at 12:27 PM, gahn wrote: > I booted the system into single user mode and tried to clean up one of my corrupted file system: > > fsck -y /dev/ad1s1f > > but in the end, the file system is still dirty. anything else I can do to salvage the data? You're not providing enough details to give specific advice. If this filesystem is already mounted as /usr (which is the default mountpoint for an "f" partition), you might try booting from CD and running fsck from there to ensure that you are not trying to fsck a mounted filesystem. If your hard drive is failing and fsck cannot fix issues because it can't write the changes to disk, you should attempt to copy the entire drive onto a replacement drive and fsck that instead. Regards, -- -Chuck