Ext3 users - Feb 2002 - ext3fs: Bad super block

I've got this poor ext3-partition which I can't access. I have tried a
lot
of things but it doesn't seem to solve the problem. I've got quite
important
files on that particular partition.

I can't even get the block groups from my /dev/hda3 with dumpe2fs!

It all happened after a crash. GRUB wouldn't give me the graphical UI. I
decided I had to get my dosbootdisk and do an fdisk /mbr to load windows,
so I could get some help on recovering the hopefulle not lost data.

Does anyone have a suggestion for how to save those important files?

Lincoln (who hopes to be able to get some sleep tonight!)





________________________________________
Denne mail er scannet for virus med eTrust EZ Armor - Markedets bedste
sikkerhedsprodukt!
Hent din egen version gratis! Klik http://www.provideit.dk/sol/

Få din egen webmail på http://www.sol.dk - gratis og med dig overalt!

On 18:09 19 Feb 2002, lincoln@sol.dk <lincoln@sol.dk> wrote:
| I've got this poor ext3-partition which I can't access. I have tried a
lot
| of things but it doesn't seem to solve the problem. I've got quite
important
| files on that particular partition.

Have you tried getting at one of the backup superblocks with the -b
option to fsck? From "man e2fsck":

      -b superblock
              Instead of using  the  normal  superblock,  use  an
              alternative  superblock  specified  by  superblock.
              This option  is  normally  used  when  the  primary
              superblock has been corrupted.  The location of the
              backup superblock is dependent on the  filesystem's
              blocksize.   For  filesystems with 1k blocksizes, a
              backup superblock can be found at block  8193;  for
              filesystems with 2k blocksizes, at block 16384; and
              for 4k blocksizes, at block 32768.

              Additional backup superblocks can be determined  by
              using  the  mke2fs  program  using the -n option to
              print out where the superblocks were created.   The
              -b  option  to mke2fs, which specifies blocksize of
              the filesystem must be specified in order  for  the
              superblock  locations  that  are  printed out to be
              accurate.

              If an alternative superblock is specified  and  the
              filesystem  is  not  opened  read-only, e2fsck will
              make sure that the primary  superblock  is  updated
              appropriately  upon  completion  of  the filesystem
              check.

I know you have ext3, but ext3 is just ext2 on steroids.

Cheers,
--
Cameron Simpson, DoD#743        cs@zip.com.au    http://www.zip.com.au/~cs/

Stay the patient course
Of little worth is your ire
The network is down
- Haiku Error Messages
http://www.salonmagazine.com/21st/chal/1998/02/10chal2.html