On 4/18/07, Constant Brouerius van Nidek <[EMAIL PROTECTED]> wrote:
On Thursday 19 April 2007, Carlos E. R. wrote:
> The Thursday 2007-04-19 at 00:37 +0700, Constant Brouerius van Nidek wrote:
> > I tried to mount this partition on /mnt but got following info:
> >
> >     # mount /dev/hdd2 /mnt
> > mount: wrong fs type, bad option, bad superblock on /dev/hdd2,
> >        missing codepage or other error
> >        In some cases useful info is found in syslog - try
> >        dmesg | tail  or so
>
> What filesystem was it? Have you fsck-ed it?
>
> --
> Cheers,
Dear   Carlos,
It is an ext3 filesystem. Think it would be best to make a copy of the disc
and I have to find out how to make a raw copy of the partition which I can
not mount.
When I used e2fsck it told:

Filesystem revision too high while trying to open /dev/hdd2
The filesystem revision is apparently too high for this version of e2fsck.
(Or the filesystem superblock is corrupt)


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>

e2fsck -b 8193 it tells me:

Bad magic number in super-block while trying to open /dev/hdd2

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>

What does the 8193 represent?  If it is a block group number, then
finding the block groups with suberblocks can be a bit of a challenge.

If I recall correctly ext2 breaks a disk into block groups.
Originally (1995 or so) every block group had a copy of the
superblock.

This became unreasonable on big disks, so they implemented a rather
unusual distribution.

Number the block groups  1,2,3, etc.  If the block group number is a
power of 3, 5, or 7, then it gets a superblock.  If not, it does not.

ie. Block groups 1,3,5,7,9,25,27,49,81,125,... have a superblock, the
rest don't.

I had not seen a algorithm like that before, but it puts a lot of
superblock copies towards the front of the disk, but also has them
distributed across the partition.  Especially if you have a lot of
corruption at the front of the partition you may need to know the
above to find superblocks further into the partition.

Greg
--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to