From owner-freebsd-security Fri Nov 30 7: 4:24 2001 Delivered-To: freebsd-security@freebsd.org Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by hub.freebsd.org (Postfix) with ESMTP id EBE7037B405 for ; Fri, 30 Nov 2001 07:04:18 -0800 (PST) Received: from list1.xs4all.nl (list1.xs4all.nl [194.109.6.52]) by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id fAUF4HCP052725 for ; Fri, 30 Nov 2001 16:04:17 +0100 (CET) Received: (from root@localhost) by list1.xs4all.nl (8.9.3/8.9.3) id QAA26013; Fri, 30 Nov 2001 16:04:16 +0100 (CET) From: "Oskar van Eeden" To: freebsd-security@freebsd.org X-Via: imploder /usr/local/lib/mail/news2mail/news2mail at list1.xs4all.nl Subject: Re: Mounting an ext2fs on FreeBSD 4.3-STABLE Date: Fri, 30 Nov 2001 16:02:37 +0100 Organization: XS4ALL Internet BV Message-ID: <9u875c$9f6$1@news1.xs4all.nl> In-Reply-To: <9u86ok$75j$1@news1.xs4all.nl> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Oopz, sorry wrong list! "Oskar van Eeden" wrote in message news:list.freebsd.security#9u86ok$75j$1@news1.xs4all.nl... > Hi there, > > I'd like to mount an ext2fs on my FreeBSD system. I recompiled my kernel > with option EXT2FS and everything seems fine. When i try to mount with > `mount -t ext2fs /ad1s2 /opt` i get the following message in > /var/log/messages: > > Nov 30 00:07:44 vaneeden /kernel: ext2fs: #ad/0x3000a: wrong magic number 0 > (expected 0xef53) > > This seems strange to me, so i tried to run e2fsck to fix this problem. The > following was prompted: > -------------------------------------------------------------------------- -- > ---------------------- > root@vaneeden:/% e2fsck /dev/ad1s2 > e2fsck 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09 > Couldn't find ext2 superblock, trying backup blocks... > e2fsck: Bad magic number in super-block while trying to open /dev/ad1s2 > > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 > -------------------------------------------------------------------------- -- > ------------------------ > > So i ran `e2fsck -b 8193 /dev/ad1s2`, but i was getting the same message. > I've read every man/doc that has something to do with ext2fs etc. _and_ I > searched the whole internet for people having this very same problem, but > there where pratically none. Can please some help me out (and for you dutch > guys, lul maar nederlands...). Mail me at oskar@vaneeden.nu. Thanks in > advance. > > (by the way: ad1: 25965MB [56272/15/63] at ata0-slave > UDMA33) > > Regards, > > Oskar van Eeden > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message