Windows doesn't start

English Install/Boot/Login
1

I hope someone can help me.

I’am new to OpenSuse and Linux.

I installed OpenSuse 10.3 on my laptop (Acer Aspire 9814WKMI) with Vista SP1.

The problem is that when I start the PC I get the Bootmenu and when I choose Windows I get the following lines:

root noverify (hd1,5)
chainloader (hd0,1)+1

and then nothing happens.

I do ctrl+alt+del and I restart and choose OpenSuse and Suse works fine.

Folowing is the outcome of fdisk and the Grub menu.lst

cp318151-b:~ # fdisk -l

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x4c656c9e

Device Boot Start End Blocks Id System
/dev/sda1 1 764 6136798+ 12 Compaq diagnostics
/dev/sda2 * 765 7646 55279664 7 HPFS/NTFS
/dev/sda3 7647 14594 55802504 7 HPFS/NTFS

Disk /dev/sdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8f9c798a

Device Boot Start End Blocks Id System
/dev/sdc1 1 10199 81922096+ 7 HPFS/NTFS
/dev/sdc2 10200 15102 39383347 7 HPFS/NTFS
/dev/sdc3 20399 30402 80350116 7 HPFS/NTFS
/dev/sdc4 15103 20398 42540120 f W95 Ext’d (LBA)
/dev/sdc5 15103 15364 2104483+ 82 Linux swap / Solaris
/dev/sdc6 15365 17398 16338073+ 83 Linux
/dev/sdc7 17399 20398 24097468+ 83 Linux

Partition table entries are not in disk order

Grub menu.lst:

Modified by YaST2. Last modification on Thu Jun 12 23:57:59 CEST 2008

default 2
timeout 8
gfxmenu (hd1,5)/boot/message

###Don’t change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.3 - 2.6.22.17-0.1
root (hd1,5)
kernel /boot/vmlinuz-2.6.22.17-0.1-default root=/dev/disk/by-id/usb-WD_2500JB_External_57442D5743414E4B36343931303737-0:0-part6 vga=0x317 resume=/dev/sdc5 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,5)
kernel /boot/vmlinuz-2.6.22.17-0.1-default root=/dev/disk/by-id/usb-WD_2500JB_External_57442D5743414E4B36343931303737-0:0-part6 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

###Don’t change this comment - YaST2 identifier: Original name: windows 1###
title windows 1
rootnoverify (hd1,5)
chainloader (hd0,1)+1

###Don’t change this comment - YaST2 identifier: Original name: Vendor diagnostic###
title Vendor diagnostic
rootnoverify (hd1,5)
chainloader (hd0,0)+1

###Don’t change this comment - YaST2 identifier: Original name: windows 2###
title windows 2
rootnoverify (hd1,5)
chainloader (hd0,2)+1

###Don’t change this comment - YaST2 identifier: Original name: windows 3###
title windows 3
rootnoverify (hd1,5)
chainloader (hd1,0)+1

###Don’t change this comment - YaST2 identifier: Original name: windows 4###
title windows 4
rootnoverify (hd1,5)
chainloader (hd1,1)+1

###Don’t change this comment - YaST2 identifier: Original name: windows 5###
title windows 5
rootnoverify (hd1,5)
chainloader (hd1,2)+1

Thanks in advance for your help.

Michel

2

This one is the real windows

/dev/sda2 * 765 7646 55279664 7 HPFS/NTFS

and it’s indicated here:

title windows 1
rootnoverify (hd1,5)
chainloader (hd0,1)+1

But the situation is complicated by the utility partition at sda1 *
I’ve been looking for this situation to come up with interest. Don’t know the answer just yet. At least the asterisk indicates it’s the boot partition for windows.
Try this version first:

title Windows Vista
rootnoverify (hd0,1)
chainloader (hd0,1)+1

Then if that doesn’t work try this:

title Windows Vista
hide (hd0,0)
rootnoverify (hd0,1)
chainloader (hd0,1)+1

Then if that doesn’t work try this:

title Windows Vista
rootnoverify (hd0,1)
chainloader (hd0,1)+1
makeactive

Then if that doesn’t work try this:

title Windows Vista
hide (hd0,0)
rootnoverify (hd0,1)
chainloader (hd0,1)+1
makeactive

Sorry, I read somewhere where this fixed the utility partition problem but I can’t find it since the forums merged and it’s got something to do with makeactive and hode/unhide, so all I can suggest is the permutations, unless someone who remembers comes along.

To edit the file menu.lst at /booot/grub/menu.lst is difficult because of special permissions on it.

Open a console and back it up. First enter su to get root paowers. Then this command will back it up:

cp /boot/grub/menu.lst /boot/grub/menu.lst.bak

Then you can open it in a text editor with either of these commands:
for KDE use

kwrite /boot/grub/menu.lst

for Gnome use

gedit /boot/grub/menu.lst

Then you can edit in the changes. Save, exit and reboot to try each variant until one works (I hope).*

3

Your first suggestion did the trick right away.

I changed rootnoverify (hd1,5) to rootnoverify (hd0,1) and it works fine now. My wife will be happy.

If I select windows it boots up normal.

Thank you for your help.

Michel

4

Well that was the simplest one of all. I thought there was a complication from the Compaq utility partition; maybe there’s not.

Glad it’s working

5

me too having the same problem…i have Xp but…

the error is

rootNoverify(hd1,1)
chainloader (hd0,0)+1

iam very new to linux…so please help me i need a detailed guidence!!

please

6

Hi

This looks like you installed Suse with the root partition as the second partition on the second drive and like you have (perhaps) xp on the firsat partition on the first drive. You can try this:
Change to this:

rootnoverify (hd0,0)
chainloader (hd0,0)+1

Note the space between fy and (hd
Note not capital N in …ootNov… but …ootnov…

If that doesn’t work then please execute these two command in a console and copy/paste the results back here. I would then perhaps ask questions after looking at your post:

  • sudo /sbin/fdisk -l
  • sudo cat /boot/grub/menu.lst