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.
So I am trying to use grub to rewrite my MBR and reboot to linux. (I had previously been sharing disks between linux and Windows and got a corrupted disk.)
I have a partition / and a separate /boot partition.
I have grub in /boot/grub.
I don't have a recovery disk so I boot linux from the CDRom, using linux rescue, and it sets an image up in /mnt/sysimage.
Using grub, I can find stage 1 like this;
Then I do this, as instructed by the grub manual;
What setup actually runs is this;
install /grub/stage1 d (hd0) /grub/stage2 p /grub/grub.conf
This looks good to me - I have a link from menu.lst to grub.conf.
However, if I cycle the power now and try it without the linux CD, I see grub startup, it gives me a menu, I pick a version of linux, and it says;
The kernel command looks right, but why, oh why, is it setting root to (hd1,1) ? Could it be something in my device.map? Or /etc/fstab? I don't know how to diagnose this problem beyond recognizing that it's not using the root that I set prior to running setup in grub.
I have tried the same install command (that setup creates) but without the 'd' argument, I get the same result when I reboot (still looking for (hd1,1)).
I have tried setting up device.map (in boot/grub) with either of
these two lines (obviously not both at the same time)
PLEASE HELP! Any insight would be greatly appreciated!!!
Last edited by chrisrose21044; 09-28-2003 at 02:28 PM.
Just as an update, I finally solved this problem on my own.
My device.map was wrong (after I had switched the drives around) and I had forgotten that grub-install uses that file. After I fixed device.mmap, and reran grub-install, I was able to get grub to boot. Yay! (Big sigh, much relief.)