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.
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.
actually, coming to think of it, i didnt even format it, i just deleted the partition....which should hopefully make it a lot easier to fix
i just need to fix the file allocation table some how if that make's it easier to help me
You may have to delete all the partitions that are causing mischief before rebuiding the partition table.
It is common for a partitioning program to evade its responsibility when confronted with something that is illogical to it. Fdisk is the most robust tool I know but I tend to use cfdisk the moment the disk is cleared.
If the partition had been merely deleted, you wouldn't have a problem. Testdisk is the best solution for things like that.
The message from cfdisk could be a problem. Last time I looked at the code, you get that because the sig bytes for the disk are gone.
If this is the case neither cfdisk nor fdisk will open it.