Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i have made an image of a friends usb pen drive(their collage thesis is on it). it currently gives a message about a bad superblock when trying to mount the image or the pendrive. i used "dd if=/dev/sda of=usbdrive" to make the image.
as i understand, the superblock means the filesystem (pen drive is fat32). is it possible to overwrite these superblocks and mount the image i made? or is there any way to recover the files on it?
mount -o loop /path/to/usbdrive /mount/point/of/your/choice
and see if the files are under /mount/point/of/your/choice after that ("usbdrive" is now the image file, not the stick itself).
I think "superblock" means the beginning of the partition where the filesystem information is stored (partition table etc.) and that FAT32 actually should have two places where partition table is written, so that if the other one gets corrupted, the other one can be used instead. Don't know about that, but it sounds bad if the stick doesn't mount. Usually they either work or are completely trashed (I had one of my usb sticks, 512MB, simply cause an error while normally software-ejecting it, and now it shows 8MB, there's nothing and you can't actually write on it..)
thank you, ive tried to mount as you have said, but i just get that bad superblock error. i dont really care about the drive itself, id say its broken, im more interested in the data on it. i just thought if it was the partition tables that are corrupt i might be able to overwrite my image with some generic partition table to be able to mount it.
Yeah, that sounds like the partition table (at least).
Note: your image is a faithful copy of the damaged partitions.
Best bet... try the dd command on the explicit partition (/dev/sda5) with the data on it. (USB sticks usually are preformatted with a single logical partition occupying the entire drive.)
Since what you really want is to recover the thesis, right, you can always grep through the dev for the thesis text the old fashioned way. Or use recovery software... you have a backup, so how about fsck run on the drive. Or use one of the many Linux Forensics software collections.