"Theodore Y. Ts'o" wrote:
>
> Date: Tue, 19 Jan 1999 13:28:42 -0600
> From: "Thomas E. Dodd /CSDC" <ted@cypress.com>
>
> Yes :) The fs is hosed now. And 2.0.36 won'r mount it either.
>
> Well, have you checked the partition table to make sure it's still sane?
> And can you do e2fsck -b 8193 with the CPU backed out?
Partition table is fine.
With either CPU fsck fails.
I tried the frist 10 superblocks (1,8193,16385,24577,...,81921)
all report not ext2fs.
Well if the partition table is fine, then the filesystem is probably
toast. You can *try* recovering by doing a "mke2fs -S" on the
partition, but this is really a last-ditch try. (Read the man page for
the appropriate warnings.) Make sure the partition table is exactly as
it was when the filesystem was originally defined before running the
mke2fs -S, since otherwise this mke2fs command can damage a lot of data,
perhaps beyond repair.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/