Bad Superblock problem

[ac_dispatcher]

OK I messed up big time. Here is the skinny if anyone has something else I can try please help.

 

fstab

 

/dev/hda1 - /mnt/windows <fat32>

/dev/hda2 - / <reiserfs>

/dev/hda3 - swap

/dev/hda5 -/mnt/data (22GB) <ext3>

/dev/hda6 - /mnt/linux (DistroHo partition) <ext3>

 

OK here is what I tried to do. Boot to windows and started up Partition Magic. Tried to:

 

delete /dev/hda4

expand the logical drive (hda4) to incompass the freespace (hda4)

enlarge hda5 to addon the 500mg of hda4

create hda7 for swap

 

Set it all up and hit "OK"

 

AN ERROR HAPPENED

 

When I first booted hda4 was gone and their was free space in the front of hda5. hda5 said unknown file format. I was able via a MDK disk1 to reset hda4 as it was (primary partion). But /dev/hda5 still lists itself as unknown file format.

 

When I boot to a MDK disk it lists it as ext2 (its ext3). When I try to mount it:

arora acdispatcher # mount -t ext3 /dev/hda5 /mnt/data 
mount: wrong fs type, bad option, bad superblock on /dev/hda5,
      or too many mounted file systems

 

OK next we try:

arora acdispatcher # e2fsck /dev/hda5
e2fsck 1.35 (28-Feb-2004)
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/hda5

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>

 

 

OK now Im real worried

 

Did I say that my backup is corrupt too?

 

go go google:

http://edseek.com/archives/2004/02/25/ext3...block-recovery/

http://forums.scotsnewsletter.com/index.ph...topic=503&st=50

 

They gave me good ideas. Here is what I tried:

 

arora acdispatcher # mke2fs -n /dev/hda5
mke2fs 1.35 (28-Feb-2004)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
2709120 inodes, 5407872 blocks
270393 blocks (5.00%) reserved for the super user
First data block=0
166 block groups
32768 blocks per group, 32768 fragments per group
16320 inodes per group
Superblock backups stored on blocks: 
       32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
       4096000

 

Ok got some backup superblocks (I think)

 

so we try:

arora acdispatcher # e2fsck -b 32768 /dev/hda5
e2fsck 1.35 (28-Feb-2004)
e2fsck: Bad magic number in super-block while trying to open /dev/hda5

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 did that for all the above block numbers. Im stuck. Ive tried Partgui, QTparted, Partition Magic wont even come up anymore.

 

Then in terminal I found this:

 

arora acdispatcher # partgui
Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Warning: Unable to align partition properly.  This probably means that another partitioning tool generated an incorrect partition table, because it didn't have the correct BIOS geometry.  It is safe to ignore,but ignoring may cause (fixable) problems with some boot loaders.

 

Lovely wish I knew that prior to mucking around with the partitions.

 

The data is there. I just need to get to it.

 

At last resort I did this:

dd if=/dev/hda5 of=/path/to/network/drive

 

With my network this will take a while. Even then this is reaching for straws.

 

Does anyone have any other ideas?

[ac_dispatcher]

OK the dd didnt work. Over file size limit.

 

What about formatting hda5 so it all looks nice

 

then try a data recovery?

Edited November 9, 2004 by ac_dispatcher