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.
When I try to start my Fedora 3 (with LVM) I get the following error .
Filesystem type is ext2fs, partition type 0x83
kernel <version> ro root=/dev/VolGroup00/LogVol00 rhgb quit
Uncompressing Linux, Ok, booting the kernel
Red Hat nash version 4.1.18 started
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
2 logical volume(s) in volume group "VolGroup00"now active
EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=507905, block=1015810
mount: error 5 mounting none
And from there it is just haning there.
I am no expert and have no clue what I can do to repair this , I got some data on there that I realy must have.
THe problem started yesterdat, while I was working, I clicked on the bar to start my email program and I got the error that my mail program was not installed.
I then tried some other things but nothing was starting, I checked the messsage file (/var/log/ ) but nothing has been writting to this file for the last 30 minutes, Then I did something realy stupid, I rebooted
I tried to boot from FC3 DVD and the boot was mounted without a problem ( I think because this is outside LVM ) but the rest gives me problems.
Is there some tool I can run to recover from this.
It sounds like you need to check one of the logical volume's ext3 filesystem with e2fsck.
Using your installation disk, boot into rescue mode (boot: linux rescue), but don't search for or mount the linux installation.
Since you have two logical volumes, one is probably “/” and the other is probably swap. From the rescue command prompt, run:
lvm vgchange -a y
Only one of the e2fsck commands may run correctly, since one of the logical volumes may be swap. The first three lvm commands are included just in case the logical volumes are not activated in rescue mode.
I finaly got this working. I used the following steps for this :
Boot from Fedora DVD, entered rescue mode
didn't search for installed distro
lvm vgchange --ignorelockingfailure -P -a y
fdisk -l ( to find partitions )
mount /dev/hda1 /mnt/boot
fsck -f -y /dev/VolGroup00/LogVol00
This did run for 8 hours, before I finaly decided to break the fsck.
When I tried to boot, I got another error, so I wan't happy.
Desided to try again with the same procedure (found somewhere on the internet)
and it repeated the last two inodes from the first try, but did continue and was finished within 30 minutes.
Rebooted, and everything was ok. Did even say that system wasn't shutdown properly and if I wanted to do a filesystem check :-)
Thanks for WhatsHisName, as he almost dictated the same procedure, and because not mounted, could even work better.
I made my backup more up to date and a script to do this everytime I issue a shutdown command.