From owner-freebsd-current Sun Jan 5 14:27:54 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 C47CB37B401 for ; Sun, 5 Jan 2003 14:27:52 -0800 (PST) Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 723E643E4A for ; Sun, 5 Jan 2003 14:27:52 -0800 (PST) (envelope-from rsidd@papagena.rockefeller.edu) Received: from user-0cev12d.cable.mindspring.com ([24.239.132.77] helo=bluerondo) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18VJFH-0000gt-01 for freebsd-current@freebsd.org; Sun, 05 Jan 2003 14:27:51 -0800 Received: (qmail 54762 invoked by uid 1001); 5 Jan 2003 22:27:40 -0000 Date: Sun, 5 Jan 2003 17:27:40 -0500 From: Rahul Siddharthan To: "Paul A. Mayer" Cc: freebsd-current Subject: Re: Unable to mount ext2fs partition Message-ID: <20030105222740.GA33220@papagena.rockefeller.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E18893F.6080009@fnug.net> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT i386 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 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