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've tried using linux rescue to get into GRUB and I received a message saying "access denied". I'm installing dual operating systems on my computer, W2k & Fedora Core, on separate hard drives. Any advice? Thanks in advance.
Ok, sounds like something happened to your comp and you need to fix something.
1. typing linux rescue from cd #1 will try to mount your / onto a partition so that you can do maintenance. I don't know exactly which part you are stuck on but it should be self-explanatory from the help screens. So, perhaps you may need to explain more on this part. Like what do you see? Do you see a prompt of any sort? Is the screen black? Can you type? Any message on the screen that you are stuck on?
2. Another attempt to fix your comp without linux rescue is to go to single user mode (init 1). Ok, so you reboot your machine and GRUB shows you which kernel it's going to load within its 10 second delay. Immediately press 'e' and then pick the one that shows "kernel" and type 'e' again. Now you are shown the kernel line, go to the very end, add a space, and append the word "single" (without quotes). Now press 'b' and it will boot to single user mode.
Fedora rescue will mount your / under /mnt/sysimage. If for some reason your Grub got wiped you could try to reinstall it. To do so you first need to change root to the system root (not the one you use throught the rescue CD) You can do that by typing "chroot /mnt/sysimage". Provided you haven't got a seperate /boot partition you should now be able to invoke 'grub-install' (if not you may need to mount the /boot partition first). In order to install Grub to the MBR you should add the parameter '/dev/hda' (check the man pages if in doubt).
Thanks for the responses everyone. I apologize for being so vague. I'll try to be more specific.
Here's where I'm at...
Grub is fine & seems to be working properly. I went throught these steps (I think I found them on this web site):
"From here you can try to find out which drive grub thinks is first and which is second in the boot order. Try typing "kernel (hd" and then pressing tab:
grub> kernel (hd<tab>
You should see the possible completions that grub can find. Drive 0 (hd0) could be either C: or L: (in FC1, hda or hdb) depending on your partitions. If you post your partition layouts for both physical drives and which cables and IDE channels they are connected to, it would help us. The output should look something like this:
grub> kernel (hd
Possible disks are: hd0 hd1
grub> kernel (hd
So now add a character (0, 1, 2, whatever you want to try). Here is what I see:
grub> kernel (hd
Possible disks are: hd0 hd1
grub> kernel (hd0,<tab>
Possible partitions are:
Partition num: 0, Filesystem type vfat, partition type 0x0a
Partition num: 1, Filesystem type unknown, partition type 0x82
Partition num: 2, Filesystem type unknown, partition type 0x83
grub> kernel (hd0,0)/<tab>
foo sandbox junk.txt
Using this method, you can explore your drives using grub and see where files live and which drives contain the data you want.
The problem we are looking for is this, what looks like (hd0) in grub at boot time, might look like (hd1) in grub when the system is up and running (i.e. start grub and do the same thing from within Linux and see if the drives have been reordered). This would account for the problem you see where installing grub to the MBR is actually installing it elsewhere.
Now that you can find your Linux partitions using grub, let's try to boot your FC1 Linux installation.
Use the command 'configfile' and the tab completion to try and locate the grub.conf or menu.lst file. It should be in the 'boot' directory on your root Linux partition, or on it's own partition if you created a separate partition for boot.
grub> configfile (hd1,0)/grub/menu.lst
Press an arrow key before the timeout expires so we can examine the entries.
Highlight your FC1 entry and type 'e'. This will allow you to edit the entry and view the hard drive that it is trying to boot from. You should see some entries like this (after pressing 'e' once).
In this example, the root drive is (hd0). If this doesn't match where you found the menu.lst file, then you will want to change it. You can use tab completion to help find the vmlinuz-2.4.22-1.2115.nptl file, your kernel, and make sure that root is set to be the drive where the kernel is found. For example, if you find the menu.lst on (hd1,0) and the kernel there too, set root to (hd1,0).
Press 'e' while 'root (hd0,9)' is highlighted and edit it to read 'root (hd1,0)'. Then press enter and you'll see all the entries again. Then, since the root is now properly set, you should be able to press 'b' to boot.
Your Linux installation should now boot."
Is anyone familiar with these steps? The problem seems to be the "menu.list". It did not show up when I entered "grub> configfile (hd1,0)/grub/menu.1st" command (it responded with "file not found"). Might this be due to faulty installation or am I looking in the wrong place? From reading these directions, it should be in the same place as the kernel vmlinuz file. If it is in a different place, is there a way to find it?