From owner-freebsd-questions@FreeBSD.ORG Sat Sep 10 22:10:03 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 446F316A424 for ; Sat, 10 Sep 2005 22:10:03 +0000 (GMT) (envelope-from zettel@acm.org) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A8EF43DB9 for ; Sat, 10 Sep 2005 22:08:32 +0000 (GMT) (envelope-from zettel@acm.org) Received: from [192.168.0.3] (pcp0011427575pcs.sothfd01.mi.comcast.net[69.246.103.241]) by comcast.net (sccrmhc13) with ESMTP id <20050910220831013004ru55e>; Sat, 10 Sep 2005 22:08:32 +0000 From: Leonard Zettel To: Jan Grant Date: Sat, 10 Sep 2005 10:08:56 +0000 User-Agent: KMail/1.8 References: <200509091210.09717.zettel@acm.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509101008.56555.zettel@acm.org> Cc: freebsd-questions@freebsd.org Subject: Re: What is fsck trying to tell me? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: zettel@acm.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Sep 2005 22:10:03 -0000 On Saturday 10 September 2005 11:20 am, Jan Grant wrote: > On Fri, 9 Sep 2005, Leonard Zettel wrote: > > When I issue the followinf command: > > > > mount /dev/ad1s1c /mnt > > > > I get the response > > WARNING: R/W mount of /mnt denied. filesystem is not clean - run fsck > > mount: /dev/ad1s1c: Operation not premitted > > > > Then when I try > > > > fsck /dev/ad1s1c > > > > I get > > fsck: exec fsck_unused for /dev/ad1s1c in sbin: /usr/sbin: No such > > file or directory > > > > BTW, mount -f /dev/ad1s1c /mnt > > > > gets me what I expect, but the hassle leading up to it has > > me scared to death. Now what? punt? > > You're using the default "whole slice" partition, ad1s1c. My guess is, > you're using the default disklabel for that slice. If you look at that > disklabel, > > # disklabel ad1s1 > > you'll see a line like this: > > c: 156301425 0 unused 0 0 # "raw" part, don't edit > Well, sort of..... If I knew what I were doing, I'd be dangerous.... So thanks to all, you gave me enough clues to work things through. Turns out the drive had one FreeBSD slice and a bunch of unused space. fsk on ad1s1a cleared tings up. -LenZ- > Now, fsck uses external helper utilities to check the consistency of > various types of filesystem. If the filesystem has an entry in > /etc/fstab, it'll pull the type from there if you specify the mount > point. If you specify the device, it looks like fsck is using the > disklabel rather than actually "tasting" the partition to determine what > fsck to use. > > You can fix this by disklabelling your device and fixing the type of > partition "c": this should be ok. You can probably also tell fsck > explicitly what type of filesystem to check, or just invoke the > appropriate fsck_ufs directly.