FedoraThis forum is for the discussion of the Fedora Project.
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.
My laptop died, appeared to be a problem with the motherboard or CPU. Decided to get a new computer rather than fix it. I had just installed Fedora 11 days before the laptop died.
Here's the problem: I pulled the ~120GG hard drive out and put it into an external case, thinking I could just quickly and easily grab all my files. Not so; I can't see anything of what I would like to recover.
The drive is recognized as a 210MB drive, with config and img files, and a lost&found folder that has nothing in it. Something's fishy as the hard drive is much larger than 210MB.
Running fsck, and fsck.ext4 on the device returns the following error:
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>
which would seem obvious to me as F11 uses ext4, not ext2.
I'm guessing the 210MB harddrive should have more partitions on it along with all the data I need. Any ideas on getting to those partitions?
F11 uses ext3 by default. You can double check the filesystem type using file -s on the device node of the partition. For example...
file -s /dev/sda1
This would return something along the lines of /dev/sda1: Linux rev 1.0 ext3 filesystem data.
jhwilliams has a good point about seeing the partition table using fdisk. It should give you a better idea of how the drive is laid out. I prefer using the command fdisk -l /dev/xxx, where xxx is the device name (sda, sdb, etc.).
Fedora's default is to wrap up all filesystems into LVM volumes. This has a lot of advantages, until you run into a hard disk problem and are confronted with LVM directly - it is much more complex even to mount a partition that belonged to an LVM volume. If you don't replace or add/remove hard disks a lot, then it can be easier to avoid LVM and go for the old-fashioned fstab scheme.
Good point, I had forgotten the default use of LVM. I have been going with a more customized installation since around FC6. machorse70 should still be able to use fdisk to view the partitions and their types. If it is using LVM you'll see an ID of '8e' and System of 'Linux LVM' when you print out or list the partition table. After that you can use some of the LVM tools to get a good picture of the drive and mount (see man lvm). These commands can be a little daunting for the uninitiated. Post back if we're heading in the right direction and I'm sure the community can help further.