Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
You should be able to recover most of your data from one of your redundant superblocks. Usually if the superblock has been corrupted, I use
/sbin/fsck.ext3 -b8192 /dev/hdX
to use the backup superblock starting at byte 8192. Evidently this one has been overwritten here, so if you can find the address of a redundant superblock that you havent already wiped, you can pass that option to fsck. Hope this helps.
@balfred: The only (slight!) chance I'd see in this situation
is to boot into DOS, and try to use something like Nortons
Disk-Doctor ... but even then, you'd have at best a coherent
list of allocated blocks, never being able to retrieve the file's
names.... sorry to say that, but your chances would have
been better if you had erased the partition using fdisk.