Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
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 and esata drive that I mounted to linux using an esata-usb cable. I see that sdb is available usning dmesg but the 3 partitions sdb1, sdb2 and sdb3 are not available. Disk /dev/sdb doesn't contain a valid partition table
When I tried to mount I get an error that the superblock is corrupted. I tried to run fsck -p /dev/sdb on the HD and I get this:
Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem ( and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Next I tried to get the superblocks with mkfs -n /dev/sdb and it fails - so I do not know the bacup superblocks.
I tried to run e2fsck using these standard superblock numbers but these commands also fail. so at this stage, I am unable to access these partitions - I know I had 3 partitions - one for linux and one for swap and third for data. Is there any way I can savlage the data partitions.
Thanks a lot for any assistance anyone can provide.
You say the drive in not showing up, but, in you initial post you indicated that you were able to run fdisk against it, albeit with a erroneous result. Testdisk can be run against the raw disk just like you did with fdisk. It does not have to show up as a mounted partition (if that's what you mean?).
On Windows: I tried testdisk on windows.The drive is not showing up on the windows platform.
On linux I see sdb but not the sdb1, sdb2 and sdb3 partitions. fdisk on linux does not show the partitions - hence the error on linux