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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
There is a file called "/boot/grub/menu.lst". This is the file grub reads to give you a boot menu. If the file exists, with entries in it:
kernel <path to kernel i.e. /boot/kernel-2.6.8>
initrd <path to initrd i.e. /boot/initrd-2.6.8>
If grub can't read /boot/grub/menu.lst there is a problem. You can edit the boot parameters in the grub command prompt by typing them at the prompt. When you have typed them all in(hit enter in between boot parameters), hit "b" and it should boot. If you don't know exactly what to put in the boot parameters, type "root" and hit tab. All the grub partitions that are bootable will show up. You pick the one you want. Then type "kernel", tab and the list of kernels will show up. Pick the one you want to boot with. Then do initrd. When you are done, hit "b".
/dev/hda1 * 1 13 104391 83 linux
/dev/hda2 14 9729 78843990 8e Linux LVM
/dev/mapper/VolGroup00-LogVol00 does not have any corresponding BIOS drive
grub-install /dev/hda1 /dev/mapper/VolGroup00-LogVol00 does not have any corresponding BIOS drive
I'm not sure why /dev/mapper is involved here at all, unless it's trying to tell you that it can't find grub-install because /mnt/sysimage is empty. What happens if you do a ls /mnt/sysimagebefore you do the chroot? If the sysimage directory is empty, try a lvchange -a to activate your logical volumes.
The comment about BIOS drive makes me wonder if you have a BIOS setting problem. You might want to check that your IDE mode is set (in your BIOS) to "compatable" rather than "enhanced," since Fedora sometimes has problems with "enhanced" mode.
When you get the grub> prompt, you could try to do the install by hand:
The point is to see if the problem is in the HDs boot sector. If you can boot from a floppy, then I'd suggest looking at your BIOS "virus protection" settings, which may be interfering with GRUB changing the information in the boot sector. (Not, actually, too likely, since you do get the GRUB prompt, whic implies that GRUB was, in fact, installed on the HD.) But a sucessful floppy boot will validate the install.
Oh, you should do the chroot before you make the floppy, so you get the settings for your installiation, not the rescue disk's settings.
Edit: Have to go walk the dog now, back in a hour or so.
Last edited by PTrenholme; 03-09-2006 at 11:55 AM.
mount cant find /media/floppy in etc/fstab or etc/mtab
Sorry, I've been assuming that you were installing a Fedora system, since you mentioned a Fedora thread in your first post. Fedora (by default) defines /media/floppy and adds an automount line to /etc/fstab, so I assumed all of that was set-up in my comments.
Edit: If jomen's comment wasn't clear, you need to do (as root)
# mkdir /media
# mkdir /media/floppy
# mount /dev/fd0 /media/floppy # The -t ext2 won't hurt, but isn't necessary
You can, of course, replace /media with any other directory (/mnt is often used), and /floppy by, again, anything you want to call it. Just be sure to use whatever you chose in all the commands.
Last edited by PTrenholme; 03-09-2006 at 01:13 PM.