Mike....the previous figures were from PM5 this is the data from fdisk:
725 1106 3068383 83 Linux
The data looks correct to me., and with the data from PM5 I figured that
there should be 749 alternate superblocks and calculated the last one at
sector 6,135,809, so I ran 'e2fsck -b 6135809 sda7' and got the same error
message. If the first 21 alternate superboocks are ruined and the last one
of 749 of them is also not readable then I supppose that one could infer
that the entire file system is toast? Right?! Sigh!!!!
Alan
P.S. I keep hoping that someone will chime in with "I know how to fix that,
just......" Oh well!
-----Original Message-----
From: Mike Fieschko <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Saturday, January 08, 2000 9:54 AM
Subject: [expert] can't mount root filesystem and can't fix it
>>>> "Alan" == Alan Shoemaker <[EMAIL PROTECTED]> writes:
>
>[snip]
>
> Alan> The superblock could not be read or does not describe a
> Alan> correct ext2 filesystem. If the device is valid and it
> Alan> really contains an ext2 filesystem (and not swap or ufs or
> Alan> something else), then the superblock is corrupt, and you
> Alan> might try running e2fsk with an alternate superblock: e2fsk
> Alan> -b 8193 <device>
>
>[snip]
>
>Can you boot off a floppy and do
>
>fdisk [device]
>
>and print out (to console) the starting and ending points of the
>partition?
>
>Then quit fdisk _without_ _modifying_ _any_ _partition_.
>
>Are the values returned by this invocation of fdisk correct?
>
>--
>Mike Fieschko, West Orange, NJ, USA
>X-Mailer: XEmacs 21.1, VM 6.75 and random-sig.el
>Kernel 2.2.14-15mdk
>http://www.viconet.com/fieschko/home.htm
>Jan 8 St Severin
>
