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.
Here's the problem: I have sda, which has Windows XP on it and sdb, which has Sabayon installed on it. I installed GRUB to the MBR on sdb and switched the driver order in the BIOS. I've never had a problem making this work before, but I can't seem to boot to Windows now. Here's the menu.lst that Sabayon generated at installation time:
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /kernel-genkernel real_root=UUID=f5cba4d6-54bb-42a6-b341-6bf64fc9b4dd
# initrd /initramfs-genkernel
title Sabayon Linux x86-64 3.4 Mini Edition
kernel /kernel-genkernel-x86_64-2.6.22-sabayon dolvm2 root=/dev/ram0 ramdisk=8192 real_root=UUID=f5cba4d6-54bb-42a6-b341-6bf64fc9b4dd quiet init=/linuxrc splash=silent,theme:sabayon vga=791 CONSOLE=/dev/tty1 pci=nomsi
title Windows x86_64
One thing I don't understand is that GRUB refers to my Linux drive as hd0. I thought GRUB always referred to drives in the same order, irrespective of their order in the BIOS. Any help would be appreciated.
That is a weird layout you have. Is your windows really on the fifth partition of the second drive. If so, it shouldn't be too difficult to see why it fails to boot:
- either XP is not on that fifth partition and you need to adjust GRUB to reflect its actual location
- or it really is in the fifth partition, which by definition is not a primary but a logical partition - and windows needs to be on a primary partition if it is to boot at all. Solution: move XP to a primary partition.
I don't know what happened. Did you edit the root statements for both operating systems?
For some stupid reason, XP decided to create an extended partition at the beginning of the drive. I don't know what the deal is with that. I've done this before using 'map', but it doesn't want to work now. Perhaps, I will try to (ughhh) reinstall Windows.
The reason I switched the drive order is because Windows can overwrite the MBR on the drive. I know I could just reinstall GRUB in that case, but I also know that I've made it work with my current configuration before.
Are you sure that you left a space between the (hd) parts of the map statemenets? I remember one occasion where I didn't and XP wouldn't boot either. Little things like these are easily overlooked but they can have some nasty consequences.
I had the same problem with Sabayon with the same configuration on the hard drives finally rebooted with Knoppix 5.1.1 which often seems to work as a rescue disc. Let me know if you come up with another solution to mounting the Sabayon.