GRUB doesn't boot linux when I enter "boot" at its prompt

Hi everyone,

I've got a problem with Grub. Here's the situation:

I've got a dual boot system with suse linux 9.0 and win xp pro. I had to reinstall xp but when that was done, i realised that xp destroyed my MBR which previously gave me the fantastic choice between xp and suse.

So, I thought, let's try to get GRUB (running from rescue mode of the suse image cd) booting into my (still exsisting) Linux distro. I read the documentation about grub and all seem pretty easy, so I gave it a shot with the following commands in my grub prompt:

1. root (hd0,6)
2. kernel /boot/vmlinuz root=/dev/hde7
3. initrd /boot/initrd
4. boot

The entering of the boot-command (point 4) seems to be the problem and I just can't understand why, because my series of grub commands is exactly like they say in the documentation. (I even tried all the options from my grub.conf file)

After typing boot and pressing enter, grub just says nothing and exits. Bringing me back to the rescue shell from which I started grub. Of course, the suse system I intended to start, doesn't start at all. I've given it various tries, but all were negative. I just can't figure why, so I really hope someone out there, knows what to do next.

A quick overview of my partitions:

/dev/hde1 = win xp (ntfs)
/dev/hde7 = suse 9.0 (reiser fs)

(note: since the xp reinstall, my partition table has NOT changed, so that shouldn't be the problem)

Thanx a lot for any help!!

Is that the only disk in your machine?

maybe you can use the rescue mode to mkbootdisk and that will help you create a floppy that'll get you into your real linux, as opposed to the rescue mode linux. once your there, u could fix your MBR with grub

try this.............

1. root (hd4,6)
2. kernel /boot/vmlinuz root=/dev/hde7
3. initrd /boot/initrd
4. boot

/dev/hde7 and (hd0,6) don't match!!!


OR try this..........

1. root (hd4,6)
2. kernel /boot/vmlinuz root=/dev/hde7
3. initrd /boot/initrd
4. boot /dev/hde7

OR this...........
1. root (hd4,6)
2. kernel /boot/vmlinuz root=/dev/hde7
3. initrd /boot/initrd
4. boot hde7

Thanx for all the help but it still doesn't work.

I tried the root (hd4,6) but then grub says that it doesn't recognize that disk. When I think about it, it is quite logical, because since I only have one hard drive it really should be hd0. (hd4 should be the 5th harddisk, I think.)
And root (hd0,6) is recognized as my intended reiser fs partition with suse. Also the kernel loading and initrd commands proceed succesfully, but afterall it still doesn't boot when I type boot.

If you just put in root (hd0, and then use TAB completion, what options does it show?

Hi,

I've got more than one partition;for clarity i've made a screendump of my partition table:

Disk /dev/hde: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hde1 * 1 4865 39078081 7 HPFS/NTFS
/dev/hde2 4866 9729 39070080 f Win95 Ext'd (LBA)
/dev/hde5 4866 6501 13141138+ c Win95 FAT32 (LBA)
/dev/hde6 6502 6613 899608+ 82 Linux swap
/dev/hde7 6614 9728 25021206 83 Linux

as you can see, I need hde7.

What is the wording of the error? Is your initrd symlink simply "initrd"? Or is it "initrd.img"? Are you able to mount your partition under Suse to look at? Go to your /boot partition and write down the exact name of your kernel and initrd. Then try booting the actual file instead of the symlinks.

thanx,

but already tried the full names of kernel and initrd. Nevertheless I just noted a few strange things in the log:

can't locate module block major <numbers>

Could have something to do with it? But what does it mean exactly? I'm stuck, again

To be sure, your drive lettering is strange but if that worked before then it should work again. Also, you stated at first that you where using the MBR before so that also should work again. I think you are over complicating your list of commands when restoring the grub.
If indeed the / ( root ) is located at /dev/hde7 , note: this can be verified with the command: rdev
here are the commands you need..........

grub
root (hd0,6)
setup (hd0)
quit
reboot

Fantastic!!!

those commands were exactly what I needed. Everything works like it used to do. Thank you!

Cool!

Now take a look at the /boot/grub/menu.lst file and tell us what you were doing wrong, cuz it had all of us beat

Originally posted by homey To be sure, your drive lettering is strange but if that worked before then it should work again.

Likely a raid-enabled motherboard (or SATA). The ATA controllers start at a,b,c,d, but raid controllers usually start at e.

vectordrake and mark_nl

Only just come across this thread.

What was the answer?

I would have thought that the homey solution using the root command has worked

therefore my tutorial on grub on detected drives needs no update for raid.


Am I right?