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 fired up GParted LiveCd and tried to make a new partition by shrinking the existing /dev/sda1 and creating another sdaX-numbered partition.
After 20 minutes I thought GParted got stuck or something bad. I cancelled the operation (oooooooooppppppppssssssss)
Now I can't get the OS (Gutsy Gibbon ver. 7.10) to run.
This is kernel 2.6.22-14. Power up shows I get past Grub, past: starting up and into the Ubuntu splash where the progress bar get to about 25% completed, and the splash is replaced by ascii text and due to
errors /dev/sda1, boot (both normal and recovery) call fsck, which runs and runs and then dies, the last message being about multiple-blocks trying to access inode number: xxxxxxxxxxxxxxx
the keyboard locks, until I so: SysReq REISUB, which causes a safe shutdown.
ubuntu@ubuntu:/home$ sudo fdisk -l
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000080
Device Boot Start End Blocks Id System
/dev/sda1 * 1 38536 309540388+ 83 Linux
/dev/sda2 38537 38913 3028252+ 5 Extended
/dev/sda5 38537 38913 3028221 82 Linux swap / Solaris
Anybody have some experience as to how to fix this?
Last edited by Mark_in_Hollywood; 04-17-2008 at 02:12 PM.
Reason: added info
In a maximised shell from a live session using the Ubuntu CD, type sudo testdisk and hit enter. And see what comes up, play with it. You can also type man testdisk and hit enter to view the testdisk manual pages if you are still "iffy".
Launch testdisk (from a livecd, for example), choose intel partition, select your drive, let it scan for partitions. If it doesn't come up with what you were looking for, go for an advanced scan.
Now here is the crux: it is going to present you with all or most of the partitions that were ever carved out of that drive - it is up to you to find out which one you are looking for. If you know, take note of the start and the end of the partition in question. Those be seen here in the second and the third columns:
Partition one in this example starts at 1 and ends at 1045.
You can restore the partition directly from testdisk although I have always just jotted the numbers down on a piece of paper and then used that info to restore through an fdisk from the terminal. If you prefer the latter option, bear in mind that testdisk counts differently from fdisk. Testdisk starts from 0, fdisk from 1 so you'll need to add 1 to the information reported by your scan.
Whatever you do, do not reformat!
This is going to be extremely difficult. If your data is important than you might need to get some pro support from some local Linux expert in a nearby computer shop.
I would rather install a new system on a new hard disk, and then recovering data from the re-partitioned drive by mounting the visible partitions. You can also create a copy of the disk with dd and parse it for file patterns, but that's going to take a lot of time and efforts. The data must be worth of it.