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.
After reading a How-To on LVM, I suspect I made a big mistake when adding a new HDD and Fedora install to a working Slack 10 system.
I booted from the Fedora bootable CD burned from ISO and the install ran fine. The existing system is a Slack install to a smaller 4GB HDD (hda). I installed the Fedora Core 3 onto a clean 10GB drive (hdb) and decided, rather than screw something up when asked to install GRUB, I said no assuming I would simply add boot instructions to my existing /etc/lilo.conf after install.
So, Fedora finished and I ran #fdisk /dev/hdb to see how files were laid down:
Disk /dev/hdb: 10.2 GB, 10248118272 bytes
255 heads, 63 sectors/track, 1245 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 13 104391 83 Linux
/dev/hdb2 14 1245 9896040 8e Linux LVM
It seems the default Fedora install uses LVM. I can't seem to mount this filesystem (if there is such a mount of it), so obviously can't modify lilo for a second OS boot.
Is this possible or must I reinstall Fedora selecting either a GRUB installer or more native filesystem than using a Logical Volume Manager? I would actually like to keep LVM intact if it isn't too much for a newbie
I believe the problem to be in my lilo.conf definition.
Based on feedback I get from successful Slack boot, /dev/hdb1 is ext3, not reiserfs, so I changed the lilo.conf to reflect this.
Also, I was missing a line related to initrd, so added that as well. I'm offsite, so don't have the exact syntax, but I have modified fstab to:
/dev/hdb1 /mnt/fc3 ext3 defaults 0 0
Selecting the Fedora boot now properly attempts the load of the fc3 kernel, but I still get kernel panic after the kernel discovers a mounted 'volume' called "VolGroup00". I have gotten further with the initrd instruction, but it still bails with something about not being able to mount a file system. I will post the specifics, later, but I suspect it has something to do with mounting the filesystems WITHIN the LVM volume group.