Date: Wed, 9 Dec 2009 18:55:21 +0000 From: Aditya Sarawgi <sarawgi.aditya@gmail.com> To: Mikle Krutov <nekoexmachina@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: [8.0-RELEASE] ext2fs mount fails Message-ID: <4b1fa518.9513f30a.3c39.ffffcab9@mx.google.com> In-Reply-To: <884554e60912090438h5811c06fx2f8ea8c93995c7bd@mail.gmail.com> References: <884554e60912090438h5811c06fx2f8ea8c93995c7bd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 09, 2009 at 12:38:10PM +0000, Mikle Krutov wrote: > Hello, > I'm currently migrating one of my systems from linux to fbsd, and i've > chosen the ext2 fs as most compatible one. > Problem is, i cannot mount it. > mount -t ext2fs /dev/ad8p1 /tmp/ext2/1 > mount: /dev/ad8p1 : Invalid argument > ext2fs: ad8p1: wrong magic number 0 (expected 0xef53) > > It mounts normally under linux, and i've fsck'd it. > Also, under fbsd i cannot even run fsck: > fsck_ext2fs /dev/ad8p1 > e2fsck 1.41.9 (22-Aug-2009) > /sbin/e2fsck: Superblock invalid, trying backup blocks... > /sbin/e2fsck: Bad magic number in super-block while trying to open /dev/ad8p1 > > 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 <device> > I've found the sb backups with testdisk and tried the e2fsck -b > <superblock_num> -B <block_size> <dev> - doesn't work, returns the > very same message as above. > Any suggestions? Firstly make sure that ad8p1 does infact have a ext2/3 filesytem. If it is try getting a dump by using dumpe2fs on freebsd(you need e2fsprogs from ports for this) or linux and mail me the dump. -- Aditya Sarawgi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4b1fa518.9513f30a.3c39.ffffcab9>