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.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Trying to burn an image I made a mistake and burned 'boot.iso' on a fat partition where i have all my mp3s.
(dd if=boot.iso of=/dev/hda1)
now I can't mount the partition I receive the following message: "wrong fs type, bad option, bad superblock on /dev/hda1, or too many mounted filesystems"
The boot.iso is 18MB, so I'm shure that there is a way to recover the rest of the data of the partition (9,5 GB).
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.