From owner-freebsd-questions@FreeBSD.ORG Tue Apr 27 04:14:04 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F91816A4CE for ; Tue, 27 Apr 2004 04:14:04 -0700 (PDT) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EB3843D45 for ; Tue, 27 Apr 2004 04:14:04 -0700 (PDT) (envelope-from andy_park@nospammail.net) Received: from server2.messagingengine.com (server2.internal [10.202.2.133]) by mail.messagingengine.com (Postfix) with ESMTP id 632DFAB096C; Tue, 27 Apr 2004 07:14:02 -0400 (EDT) Received: by server2.messagingengine.com (Postfix, from userid 99) id 8D696827D2; Tue, 27 Apr 2004 07:14:02 -0400 (EDT) Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.3 (F2.71; T1.001; A1.51; B2.12; Q2.03) From: andy_park@nospammail.net To: freebsd-questions@freebsd.org Date: Tue, 27 Apr 2004 04:14:02 -0700 X-Sasl-Enc: EFQ0xCVgjFoqHgc7ULSYDw 1083064442 Message-Id: <1083064442.29080.185185414@webmail.messagingengine.com> cc: kris@obsecurity.org Subject: RE: Auto-mounting ext2 slices X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2004 11:14:04 -0000 -- Original message -- No, there's also a fsck_ext2fs. This is necessary for fsck to have any hope of being able to clean the filesystem automatically (it doesn't know about weirdly named binaries like e2fsck :-), although you may need to copy it into /sbin since /usr isn't mounted by the time fsck runs. Kris -- End of original message -- Right, so I copied fsck_ext2fs (which I had already, in /usr/local/sbin) to /sbin, and hard-reset the system, but the boot still halts at the point it tries to mount the ext2 slice. I get a warning that says the slice is not clean, followed by a 'no permissions' error. The other oddity is that simply trying 'fsck /dev/ad1s5' doesn't work (it complains about the magic number being incorrect), although the man page for fsck_ext2fs suggests that fsck should be able to invoke fsck_ext2fs. Does this mean the slice has a corrupt superblock? I also have a follow-up question. Is there a way to mark a slice 'dirty' without crashing or hard-resetting the OS? It would considerably ease my testing. Thanks, Andy Park -- http://www.fastmail.fm - Email service worth paying for. Try it for free