[PLUG] kernel panic

[Fred Davis]

That's what I ended up doing
findsuper /dev/hda2 found alternative superblocks,
and then I ran e2fsck -b ### /dev/hda2

it restored alot of the files... enough was left so correlating it with
2-day old backups resulted in maybe 15% of /home files lost... though
there was a lot in lost+found that I had to go through by hand...

-fred

On 23 Apr 2001, Charles Fultz wrote:

> The following message is a courtesy copy of an article
> that has been posted to purdue.student-org.plug as well.
>
> Fred Davis <fdavis2@purdue.edu> writes:
>
> > single-user bootup gives same kernel panic error
> >
> > using resuce disk, can't mount /dev/hda2 at all, it says:
> > VFS: can't find an ext2 filesystem on dev 03:02
> > mount: wrong fs type, bad option, bad superblock on /dev/hda2, or too many
> > mounted file systems
>
> I realize you've probably already done this, but just checking.
> Have you tried booting from a boot/rescue floppy and then running
> % fsck - b superblock /dev/hda2
>
> Where superblock is an alternative superblock.  From the fsck manpage:
>        -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;  most  filesystems
>               have  primary  superblocks  located at blocks 8193,
>               16385, etc.  If an alternative superblock is speci­
>               fied  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.
>
> Charles Fultz
> fultz
>