[PLUG] kernel panic - findsuper

Fri, 20 Apr 2001 12:38:31 -0500

Sorry, I can't help out...  But I just thought this message was funny until I
realized that supper is spelled with two p's... now it makes more sesnse and isn't as
funny.

-chuck

Fred Davis wrote:

> I booted up with a rescue disk and ran e2fsck on /dev/hda2
> it gave me:
>
> couldn't find ext2 superblock, trying backup blocks...
> e2fsck: Bad magic number in super-block while trying to open /dev/hda2
>
> The superblock could not be read or does not describe a correct ext2
> If the device is valid and it really contains an ext2 filesystem, then
> the superblock is corrupt, and you might try running e2fsck with an
> alternate superblock:
>    e2fsck -b 8193 <device>
>
> running it with the block flag produced a similar error
>
> so I ran findsuper to find the ext2 superblocks on /dev/hda2:
>
> thisoff         block   fs_blk_sz       blksz           last_mount
> 52850688        51612   1232098535      469638055       Sat Apr 10 16:23:22 1920
> 134217728       131072  440370          2               Thu Apr 19 11:50:49 2001
> 226288640       220985  -2092789546     1219469568      Sat Feb 22 11:19:24 1936
> 268435456       262144  440370          2               Thu Apr 19 11:50:49 2001
> 402653184       393216  440370          2               Thu Apr 19 11:50:49 2001
> 465716736       454801  1499841563      -360943965      Thu Nov 28 20:00:51 1907
> 536870912       524288  440370          2               Thu Apr 19 11:50:49 2001
> 671088640       655360  440370          2               Thu Apr 19 11:50:49 2001
> 729023488       711937  -40014265       -1778910256     Tue Aug 7 19:38:40 1956
> 805306368       786432  440370          2               Thu Apr 19 11:50:49 2001
> 848526848       828639  723101097       -939355573      Tue Aug 14 12:59:39 1945
> 874342400       853850  832459637       388712724       Fri Jan 6 20:42:44 1933
> 882518016       861834  2047397729      1062945554      Thu Jul 29 19:34:02 1943
> 939524096       917504  440370          2               Thu Apr 19 11:50:49 2001
> 969052672       946340  -737651068      -1888955317     Wed May 18 03:56:32 1932
> 979368448       956414  381409767       -1267183917     Tue Nov 14 19:08:22 1967
> 1073741824      1048576 440370          2               Thu Apr 19 11:50:49 2001
> 1083363840      1057972 1970300780      1685219180      Sat Aug 28 07:08:28 2027
> 1207959552      1179648 440370          2               Thu Apr 19 11:50:49 2001
> 1337263104      1305921 973078528       -1419101952     Fri Apr 21 17:54:08 1916
> 1342177280      1310720 440370          2               Thu Apr 19 11:50:49 2001
> 1351422464      1319748 1024            -1779935664     Tue Jan 23 13:37:52 2007
> 1367519744      1335468 -1677881218     -551876169      Tue Mar 11 12:12:56 1969
> 1464973312      1430638 1542208         0               Thu Aug 31 02:14:15 2000
> 1473361920      1438830 1542208         0               Thu Aug 31 02:14:15 2000
> 1476395008      1441792 440370          2               Thu Apr 19 11:50:49 2001
> 1502890496      1467666 577545965       1372031559      Wed Dec 11 07:21:07 1907
> 1580539392      1543495 -1281358443     1182999590      Thu Dec 22 10:12:58 1921
> 1610612736      1572864 440370          2               Thu Apr 19 11:50:49 2001
> 1744830464      1703936 440370          2               Thu Apr 19 11:50:49 2001
> read failed: No such file or directory
> failed on 1 at 1803755520
>
> the fs_blk_sz for block# 861834 is exactly the right size of the partition
> (if the units are in bytes), but the date on the last mount seems off,
> its an old laptop, but not that old...
>
> * what block should I run e2fsck with?
>
> * what's the difference between blk_sz and fs_blk_sz?
> * what's the significance of the blk_sz? there are lots of 2s for
> yesterday (when it all began). There are 2x 0's.. some (-)'s
> * the dates are screwy.. what does that mean?
>
> ANY help is greatly appreciated...
>
> -fred
>
> On Fri, 20 Apr 2001, Rick Redman wrote:
>
> > > [Ms-DOS Fs. Rel. 12 FAT0, check=n, conv=6, uid = 0, gid = 0, umask=022, 6 map]
> > > [me=0x2,cs=0,#f=25,fs=0,fl=0,ds=0,de=5376,data=336,se=9515,fs=0,ls=1024,
> > > rc=0,fc=4294967295]
> > > Transaction block size=512
> > > invalid sesison # or type of track
> > > Kernel panic: VFS: unable to mount root fs on 03:02
> >
> > Are you sure you didnt change your FSTAB or anything? This look like it
> > is trying to mount your root partition (which is USUALLY ext2). But instead
> > of finding an EXT2 partition it is finding a MSDOS/VFAT partition instead.
> >
> > Maybe you specified the wrong root=/dev/hd__ in lilo.conf ?
> >
> > Or maybe your hard-drive ate itself?
> >
> > -R
> >
> >
>
> ____________________________________________________
> The Purdue Linux Users' Group (PLUG) mailing list.
> For account maintenance, go to:
> plug mailing list  -  plug@csociety.purdue.edu
> http://csociety.ecn.purdue.edu/mailman/listinfo/plug