From owner-freebsd-current Mon Jan 6 0:53:20 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EBF737B401 for ; Mon, 6 Jan 2003 00:53:18 -0800 (PST) Received: from disk.fnug.net (213.237.71.107.adsl.amb.worldonline.dk [213.237.71.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id A280C43E4A for ; Mon, 6 Jan 2003 00:53:07 -0800 (PST) (envelope-from paul@fnug.net) Received: from fnug.net (unknown [192.168.0.100]) by disk.fnug.net (Postfix) with ESMTP id A702C4497; Mon, 6 Jan 2003 09:52:55 +0059 (CET) Message-ID: <3E194386.8070004@fnug.net> Date: Mon, 06 Jan 2003 09:51:18 +0100 From: "Paul A. Mayer" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rahul Siddharthan , freebsd-current Subject: Re: Unable to mount ext2fs partition References: <20030105222740.GA33220@papagena.rockefeller.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Rahul, The mount capability has to be included as a kernel option in a custom build kernel. I forget exactly what it's called (I'm writing in another OS on the system, so I can't check it right now), but I think it's something like this: option EXT2FS Have you included that in your kernel build? /Paul Rahul Siddharthan wrote: > Paul A. Mayer wrote: > >>I had to install the e2fstools port before I could access my e2fs >>partitions after installing -current. Thereafter everything has been >>fine. No problems with the disk, etc. > > > Hm, didn't know about this port.. but it still doesn't include a > mount program, and I still can't mount the partition even after > installing the port. > > I don't want to fsck it and risk screwing it up: it's a "real" > linux system (ie, a dual-boot machine) and the linux continues to boot > perfectly nicely. > > But here's what I get with an e2fsck -n : > > # e2fsck -n /dev/ad0s2 > e2fsck 1.27 (8-Mar-2002) > The filesystem size (according to the superblock) is 714892 blocks > The physical size of the device is 0 blocks > Either the superblock or the partition table is likely to be corrupt! > Abort? no > > /dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks > > So what does that mean? Any way to fix it? > > >>The only thing that is a problem >>is if your e2fs partion(s) are mounted and your system crashes > > > Not a problem for me (it's likely to be mounted read-only anyway, > and I can always boot into linux to fix it if it's dirty) > > - Rahul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message