Grub Error 15

I get GRUB error 15 when I try to boot into windows.

According to http://www.uruk.org/orig-grub/errors.html,
15 : "Error while parsing number"
This error is returned if GRUB was expecting to read a number and encountered bad data.

How do I fix this? Windows install is on SDA, another install is on SDC, and Suse is installed on SDB,

device.map:
(hd0) /dev/sda
(hd2) /dev/sdc
(hd1) /dev/sdb

menu.lst:
# Modified by YaST2. Last modification on Fri May 23 00:26:33 CDT 2008
default 0
timeout 8
gfxmenu (hd1,1)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: windows 1###
title Microsoft Windows Vista
rootnoverify (hd1,1)
chainloader +1

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.3 - 2.6.22.17-0.1
root (hd1,1)
kernel /boot/vmlinuz-2.6.22.17-0.1-default root=/dev/disk/by-id/scsi-SATA_ST3500630AS_9QG3F9PA-part2 vga=0x31a resume=/dev/sdb1 splash=silent showopts
initrd /boot/initrd-2.6.22.17-0.1-default

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 10.3 - 2.6.22.17-0.1
root (hd1,1)
kernel /boot/vmlinuz-2.6.22.17-0.1-default root=/dev/disk/by-id/scsi-SATA_ST3500630AS_9QG3F9PA-part2 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3
initrd /boot/initrd-2.6.22.17-0.1-default

grub.conf:
setup --stage2=/boot/grub/stage2 (hd0) (hd1,1)
quit

Looks like this:

###Don't change this comment - YaST2 identifier: Original name: windows 1###
title Microsoft Windows Vista
rootnoverify (hd1,1)
chainloader +1[/b]

Is missing something. Last line should be like

chainloader (hd0,0)+1[/b]

If vista is on the first partition of the first drive

Swerdna

Looks like this:

Is missing something. Last line should be like

If vista is on the first partition of the first drive

Swerdna
[/b]

I did that, now I'm getting this. http://img459.imageshack.us/my.php?i...any0076nj3.jpg It just stays there, nothing happens.

I see you've had this problem since November 07. Has it ever worked vista-suse multiboot?

Also please open a console, su to get root powers and then enter fdisk -l. Post back here what you get.

Also are you running a notebook with a utility partition on the internal drive?

That's three things please

Swerdna

I see you've had this problem since November 07. Has it ever worked vista-suse multiboot?

Also please open a console, su to get root powers and then enter fdisk -l. Post back here what you get.

Also are you running a notebook with a utility partition on the internal drive?

That's three things please

Swerdna
[/b]

Yeah. It was working A-OK before. Although earlier today I reinstalled suse (on same hard drive) and now I have these problems. I'm running on a desktop computer.

linux:/home/chris # fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x70841fad

Device Boot Start End Blocks Id System
/dev/sda1 * 1 60802 488384512 7 HPFS/NTFS

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x70841faa

Device Boot Start End Blocks Id System
/dev/sdb1 1 262 2104483+ 82 Linux swap / Solar
/dev/sdb2 263 2873 20972857+ 83 Linux
/dev/sdb3 2874 60801 465306660 83 Linux

Disk /dev/sdc: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x64061985

Device Boot Start End Blocks Id System
/dev/sdc1 1 91202 732571648 7 HPFS/NTFS

Your fdisk results show two NTFS partitions. What is dev/sdc1 used for? Assuming the first then, /dev/sda1 -> (hd0,0)

So try changing grub entry to:

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,0)
chainloader (hd0,0)+1

I boot Windows XP with same entry. Another possibility is that the windows MBR has been destroyed, and needs to be repaired first. Like swerdna asked, do you have a vista recovery or utility partition?

Your fdisk results show two NTFS partitions. What is dev/sdc1 used for? Assuming the first then, /dev/sda1 -> (hd0,0)

So try changing grub entry to:

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,0)
chainloader (hd0,0)+1

I boot Windows XP with same entry. Another possibility is that the windows MBR has been destroyed, and needs to be repaired first. Like swerdna asked, do you have a vista recovery or utility partition?
[/b]

sda and sdc contain vista installs. sda is an older install and sdc was one i was mainly using.

Also I will try that. Hang on.

Didn't fix it. Same thing as before. rootnoverify (hd0,0) chainloader (hd0,0)+1 appears on the screen and it just stays there for eternity.

sda and sdc contain vista installs. sda is an older install and sdc was one i was mainly using.

Also I will try that. Hang on.
[/b]

Watching from afar:
There's the key: "sdc was the one I was mainly using". How did you boot sdc's vista? Explain it with too many words so there's no ambiguity.
Back to you Dean

1) You haven't answered the question about whether you have windows recovery partition installed. If not, do you have Windows installation DVD? I think you may need to restore the MBR. More info on how to do that here.

2) When did it all stop working? After installing suse? More details please.

3) Also, what happens when you try to chainload the other windows installation on /dev/sdc1? Edit menu.lst like this:

title Windows
rootnoverify (hd2,0)
makeactive
chainloader (hd2,0)+1

Not sure if the 'makeactive' is required. (Won't do any harm though). Seen it with other vista boot examples.

Stay by my side gurus, I think I'm going to need help here...