Bug #414178 “Failure to boot Windows 7 after installing Karma " : Bugs : grub-installer package : Ubuntu

Roderic Jones (rodericj) on 2009-08-17

tags:

added: grub2

Nicola Ferralis (feranick) on 2009-08-19

affects:

ubuntu → grub2 (Ubuntu)

Revision history for this message

Felix Zielcke (fzielcke) wrote on 2009-08-19: Re: [Bug 414178] [NEW] Failure to boot Windows 7 after installing Karma

#1

Am Mittwoch, den 19.08.2009, 02:22 +0000 schrieb Launchpad Bug Tracker:
>
> menu.lst had windows booting from hd(0,0) and this needed changing to
> hd(1,1) to work although I had calculated it should be hd(2,1)
>
> It is all working fine now. I wonder if Grub 2 can cope with windows 7
> booting from a second partition?
>

It can. It would be good to know how the generated grub.cfg from karmic
looked like.
os-prober should detect it and add so update-grub should add it to
grub.cfg

Revision history for this message

Roderic Jones (rodericj) wrote on 2009-08-19: Re: [Bug 414178] [NEW] Failure to boot Windows 7 after installing Karma

#2

os-prober gives:

/dev/sdc2:Windows Vista (loader):Windows:chain

fdisk -l gives:

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

Device Boot Start End Blocks Id System
/dev/sda1 1 30401 244196001 7 HPFS/NTFS
/dev/sda4 * 1 1 0 0 Empty
Partition 4 does not end on cylinder boundary.

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

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 60798 488359903+ 83 Linux
/dev/sdb2 60799 60801 24097+ 5 Extended
/dev/sdb5 60799 60801 24066 82 Linux swap / Solaris

Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005363b

Device Boot Start End Blocks Id System
/dev/sdc1 1 127482 1023999133+ b W95 FAT32
/dev/sdc2 * 127483 127495 102400 7 HPFS/NTFS

There is no grub.cfg as I have completely removed Karmic so that I
could get things working again.

I have just backed up and I will install Karmic and send you what the
grub.cfg contains later.

2009/8/19 Felix Zielcke <email address hidden>:
> Am Mittwoch, den 19.08.2009, 02:22 +0000 schrieb Launchpad Bug Tracker:
>>
>> menu.lst had windows booting from hd(0,0) and this needed changing to
>> hd(1,1) to work although I had calculated it should be hd(2,1)
>>
>> It is all working fine now. I wonder if Grub 2 can cope with windows 7
>> booting from a second partition?
>>
>
> It can. It would be good to know how the generated grub.cfg from karmic
> looked like.
> os-prober should detect it and add so update-grub should add it to
> grub.cfg
>
> --
> Failure to boot Windows 7 after installing Karma
> https://bugs.launchpad.net/bugs/414178
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Roderic Jones

Trout Cottage
Llanvihangel Crucorney
Abergavenny
Monmouthshire
NP7 7NB

Telephone 01873 890050

os-prober gives:

/dev/sdc2:Windows Vista (loader):Windows:chain

fdisk -l gives:

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

Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       30401   244196001    7  HPFS/NTFS
/dev/sda4   *           1           1           0    0  Empty
Partition 4 does not end on cylinder boundary.

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

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       60798   488359903+  83  Linux
/dev/sdb2           60799       60801       24097+   5  Extended
/dev/sdb5           60799       60801       24066   82  Linux swap / Solaris

Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005363b

Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1      127482  1023999133+   b  W95 FAT32
/dev/sdc2   *      127483      127495      102400    7  HPFS/NTFS

There is no grub.cfg as I have completely removed Karmic so that I
could get things working again.

I have just backed up and I will install Karmic and send you what the
grub.cfg contains later.

2009/8/19 Felix Zielcke <fzielcke@z-51.de>:
> Am Mittwoch, den 19.08.2009, 02:22 +0000 schrieb Launchpad Bug Tracker:
>>
>> menu.lst had windows booting from hd(0,0) and this needed changing to
>> hd(1,1) to work although I had calculated it should be hd(2,1)
>>
>> It is all working fine now. I wonder if Grub 2 can cope with windows 7
>> booting from a second partition?
>>
>
> It can. It would be good to know how the generated grub.cfg from karmic
> looked like.
> os-prober should detect it and add so update-grub should add it to
> grub.cfg
>
> --
> Failure to boot Windows 7 after installing Karma
> https://bugs.launchpad.net/bugs/414178
> You received this bug notification because you are a direct subscriber
> of the bug.
>

-- 
Roderic Jones

Trout Cottage
Llanvihangel Crucorney
Abergavenny
Monmouthshire
NP7 7NB

Telephone 01873 890050

Revision history for this message

Roderic Jones (rodericj) wrote on 2009-08-19:

#3

Download full text (15.2 KiB)

Karmic has now been installed but grub (legacy) shows only Jaunty and Windows!!!

os-prober now gives:

/dev/sdc2:Windows Vista (loader):Windows:chain
/dev/sdc5:Ubuntu karmic (development branch) (9.10):Ubuntu:linux

######################################################################################

fdisk -l now gives:

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

Device Boot Start End Blocks Id System
/dev/sda1 1 30401 244196001 7 HPFS/NTFS
/dev/sda4 * 1 1 0 0 Empty
Partition 4 does not end on cylinder boundary.

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

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 60798 488359903+ 83 Linux
/dev/sdb2 60799 60801 24097+ 5 Extended
/dev/sdb5 60799 60801 24066 82 Linux swap / Solaris

Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005363b

Device Boot Start End Blocks Id System
/dev/sdc1 1 127482 1023999133+ b W95 FAT32
/dev/sdc2 * 127483 127495 102400 7 HPFS/NTFS
/dev/sdc3 127496 182401 441032445 5 Extended
/dev/sdc5 127496 180921 429144313+ 83 Linux
/dev/sdc6 180922 182401 11888068+ 82 Linux swap / Solaris

##############################################################################################

grub.cfg is:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set default=0
set root=(hd2,5)
search --no-floppy --fs-uuid --set 434ff787-9951-4019-9e90-c102f8595239
if loadfont /usr/share/grub/ascii.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output.gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
  fi
fi
set timeout=10
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-5-generic" {
set root=(hd2,5)
search --no-floppy --fs-uuid --set 434ff787-9951-4019-9e90-c102f8595239
linux /boot/vmlinuz-2.6.31-5-generic
root=UUID=434ff787-9951-4019-9e90-c102f8595239 ro quiet splash
initrd /boot/initrd.img-2.6.31-5-generic
}
menuentry "Ubuntu, Linux 2.6.31-5-generic (recovery mode)" {
set root=(hd2,5)
search --no-floppy --fs-uuid --set 434ff787-9951-4019-9e90-c102f8595239
linux /boot/vmlinuz-2.6.31-5-generic
root=UUID=434ff787-9951-4019-9e90-c102f8595239 ro single
...

Karmic has now been installed but grub (legacy) shows only Jaunty and Windows!!!

os-prober now gives:

/dev/sdc2:Windows Vista (loader):Windows:chain
/dev/sdc5:Ubuntu karmic (development branch) (9.10):Ubuntu:linux

######################################################################################

fdisk -l now gives:

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

Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       30401   244196001    7  HPFS/NTFS
/dev/sda4   *           1           1           0    0  Empty
Partition 4 does not end on cylinder boundary.

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

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       60798   488359903+  83  Linux
/dev/sdb2           60799       60801       24097+   5  Extended
/dev/sdb5           60799       60801       24066   82  Linux swap / Solaris

Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005363b

Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1      127482  1023999133+   b  W95 FAT32
/dev/sdc2   *      127483      127495      102400    7  HPFS/NTFS
/dev/sdc3          127496      182401   441032445    5  Extended
/dev/sdc5          127496      180921   429144313+  83  Linux
/dev/sdc6          180922      182401    11888068+  82  Linux swap / Solaris

##############################################################################################

grub.cfg is:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set default=0
set root=(hd2,5)
search --no-floppy --fs-uuid --set 434ff787-9951-4019-9e90-c102f8595239
if loadfont /usr/share/grub/ascii.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output.gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
  fi
fi
set timeout=10
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-5-generic" {
	set root=(hd2,5)
	search --no-floppy --fs-uuid --set 434ff787-9951-4019-9e90-c102f8595239
	linux	/boot/vmlinuz-2.6.31-5-generic
root=UUID=434ff787-9951-4019-9e90-c102f8595239 ro   quiet splash
	initrd	/boot/initrd.img-2.6.31-5-generic
}
menuentry "Ubuntu, Linux 2.6.31-5-generic (recovery mode)" {
	set root=(hd2,5)
	search --no-floppy --fs-uuid --set 434ff787-9951-4019-9e90-c102f8595239
	linux	/boot/vmlinuz-2.6.31-5-generic
root=UUID=434ff787-9951-4019-9e90-c102f8595239 ro single
	initrd	/boot/initrd.img-2.6.31-5-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
	linux	/boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
	linux	/boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_otheros ###

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
menuentry "Ubuntu 9.04, kernel 2.6.28-15-generic (on /dev/sdb1)" {
	set root=(hd1,1)
	search --no-floppy --fs-uuid --set 255f43dd-b711-4fcf-8056-3f0c64f9500c
	linux /boot/vmlinuz-2.6.28-15-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro quiet splash
	initrd /boot/initrd.img-2.6.28-15-generic
}

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
menuentry "Ubuntu 9.04, kernel 2.6.28-15-generic (recovery mode) (on
/dev/sdb1)" {
	set root=(hd1,1)
	search --no-floppy --fs-uuid --set 255f43dd-b711-4fcf-8056-3f0c64f9500c
	linux /boot/vmlinuz-2.6.28-15-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro single
	initrd /boot/initrd.img-2.6.28-15-generic
}

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
menuentry "Ubuntu 9.04, kernel 2.6.28-14-generic (on /dev/sdb1)" {
	set root=(hd1,1)
	search --no-floppy --fs-uuid --set 255f43dd-b711-4fcf-8056-3f0c64f9500c
	linux /boot/vmlinuz-2.6.28-14-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro quiet splash
	initrd /boot/initrd.img-2.6.28-14-generic
}

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
menuentry "Ubuntu 9.04, kernel 2.6.28-14-generic (recovery mode) (on
/dev/sdb1)" {
	set root=(hd1,1)
	search --no-floppy --fs-uuid --set 255f43dd-b711-4fcf-8056-3f0c64f9500c
	linux /boot/vmlinuz-2.6.28-14-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro single
	initrd /boot/initrd.img-2.6.28-14-generic
}

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
menuentry "Ubuntu 9.04, kernel 2.6.28-11-generic (on /dev/sdb1)" {
	set root=(hd1,1)
	search --no-floppy --fs-uuid --set 255f43dd-b711-4fcf-8056-3f0c64f9500c
	linux /boot/vmlinuz-2.6.28-11-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro quiet splash
	initrd /boot/initrd.img-2.6.28-11-generic
}

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
menuentry "Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode) (on
/dev/sdb1)" {
	set root=(hd1,1)
	search --no-floppy --fs-uuid --set 255f43dd-b711-4fcf-8056-3f0c64f9500c
	linux /boot/vmlinuz-2.6.28-11-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro single
	initrd /boot/initrd.img-2.6.28-11-generic
}

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
menuentry "Ubuntu 9.04, memtest86+ (on /dev/sdb1)" {
	set root=(hd1,1)
	search --no-floppy --fs-uuid --set 255f43dd-b711-4fcf-8056-3f0c64f9500c
	linux /boot/memtest86+.bin
}

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sdc2
menuentry "Windows Vista (loader)" {
	set root=(hd2,2)
	search --no-floppy --fs-uuid --set 9eac9199ac916c91
	chainloader +1
}
### END /etc/grub.d/30_otheros ###

### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###

#########################################################################################################

menu.lst is:

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default		0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout		10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title		Windows 95/98/NT/2000
# root		(hd0,0)
# makeactive
# chainloader	+1
#
# title		Linux
# root		(hd0,1)
# kernel	/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=255f43dd-b711-4fcf-8056-3f0c64f9500c

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
##      lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
##      indomU=true
##      indomU=false
# indomU=detect

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title		Ubuntu 9.04, kernel 2.6.28-15-generic
uuid		255f43dd-b711-4fcf-8056-3f0c64f9500c
kernel		/boot/vmlinuz-2.6.28-15-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro quiet splash
initrd		/boot/initrd.img-2.6.28-15-generic
quiet

title		Ubuntu 9.04, kernel 2.6.28-15-generic (recovery mode)
uuid		255f43dd-b711-4fcf-8056-3f0c64f9500c
kernel		/boot/vmlinuz-2.6.28-15-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro  single
initrd		/boot/initrd.img-2.6.28-15-generic

title		Ubuntu 9.04, kernel 2.6.28-14-generic
uuid		255f43dd-b711-4fcf-8056-3f0c64f9500c
kernel		/boot/vmlinuz-2.6.28-14-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro quiet splash
initrd		/boot/initrd.img-2.6.28-14-generic
quiet

title		Ubuntu 9.04, kernel 2.6.28-14-generic (recovery mode)
uuid		255f43dd-b711-4fcf-8056-3f0c64f9500c
kernel		/boot/vmlinuz-2.6.28-14-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro  single
initrd		/boot/initrd.img-2.6.28-14-generic

title		Ubuntu 9.04, kernel 2.6.28-11-generic
uuid		255f43dd-b711-4fcf-8056-3f0c64f9500c
kernel		/boot/vmlinuz-2.6.28-11-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro quiet splash
initrd		/boot/initrd.img-2.6.28-11-generic
quiet

title		Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid		255f43dd-b711-4fcf-8056-3f0c64f9500c
kernel		/boot/vmlinuz-2.6.28-11-generic
root=UUID=255f43dd-b711-4fcf-8056-3f0c64f9500c ro  single
initrd		/boot/initrd.img-2.6.28-11-generic

title		Ubuntu 9.04, memtest86+
uuid		255f43dd-b711-4fcf-8056-3f0c64f9500c
kernel		/boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title		Other operating systems:
root

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title		Windows Vista (loader)
rootnoverify	(hd1,1)
savedefault
makeactive
chainloader	+1

###################################################################################

I hope this helps.

Best wishes

Roderic Jones

2009/8/19 Roderic Jones <rodericj@gmail.com>:
> os-prober gives:
>
> /dev/sdc2:Windows Vista (loader):Windows:chain
>
> fdisk -l gives:
>
> Disk /dev/sda: 250.0 GB, 250059350016 bytes
> 255 heads, 63 sectors/track, 30401 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0xeee5a48c
>
>   Device Boot      Start         End      Blocks   Id  System
> /dev/sda1               1       30401   244196001    7  HPFS/NTFS
> /dev/sda4   *           1           1           0    0  Empty
> Partition 4 does not end on cylinder boundary.
>
> Disk /dev/sdb: 500.1 GB, 500107862016 bytes
> 255 heads, 63 sectors/track, 60801 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x6434ac01
>
>   Device Boot      Start         End      Blocks   Id  System
> /dev/sdb1   *           1       60798   488359903+  83  Linux
> /dev/sdb2           60799       60801       24097+   5  Extended
> /dev/sdb5           60799       60801       24066   82  Linux swap / Solaris
>
> Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
> 255 heads, 63 sectors/track, 182401 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x0005363b
>
>   Device Boot      Start         End      Blocks   Id  System
> /dev/sdc1               1      127482  1023999133+   b  W95 FAT32
> /dev/sdc2   *      127483      127495      102400    7  HPFS/NTFS
>
> There is no grub.cfg as I have completely removed Karmic so that I
> could get things working again.
>
> I have just backed up and I will install Karmic and send you what the
> grub.cfg contains later.
>
> 2009/8/19 Felix Zielcke <fzielcke@z-51.de>:
>> Am Mittwoch, den 19.08.2009, 02:22 +0000 schrieb Launchpad Bug Tracker:
>>>
>>> menu.lst had windows booting from hd(0,0) and this needed changing to
>>> hd(1,1) to work although I had calculated it should be hd(2,1)
>>>
>>> It is all working fine now. I wonder if Grub 2 can cope with windows 7
>>> booting from a second partition?
>>>
>>
>> It can. It would be good to know how the generated grub.cfg from karmic
>> looked like.
>> os-prober should detect it and add so update-grub should add it to
>> grub.cfg
>>
>> --
>> Failure to boot Windows 7 after installing Karma
>> https://bugs.launchpad.net/bugs/414178
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
>
> --
> Roderic Jones
>
> Trout Cottage
> Llanvihangel Crucorney
> Abergavenny
> Monmouthshire
> NP7 7NB
>
> Telephone 01873 890050
>

-- 
Roderic Jones

Trout Cottage
Llanvihangel Crucorney
Abergavenny
Monmouthshire
NP7 7NB

Telephone 01873 890050

Revision history for this message

Felix Zielcke (fzielcke) wrote on 2009-08-20: Re: [Bug 414178] [NEW] Failure to boot Windows 7 after installing Karma

#4

Am Mittwoch, den 19.08.2009, 20:19 +0000 schrieb Roderic Jones:
> Karmic has now been installed but grub (legacy) shows only Jaunty and
> Windows!!!
>

grub.cfg looks good.
So just make sure you load grub2 instead of grub-legacy.
Maybe the installer put it on a different disk
or just use grub-install /dev/sda from karmic so grub-legacy gets
replaced with grub2 in MBR.

Revision history for this message

Roderic Jones (rodericj) wrote on 2009-08-20: Re: [Bug 414178] [NEW] Failure to boot Windows 7 after installing Karma

#5

I am afraid this does not work. Grub Legacy will boot to Windows or Jaunty.

Running Karmic from the live CD - it is not possible to mount the
Karmic partition.

It is possible to run Karmic using the Super-Grub disc - this shows
the Grub2 menu and then boots into Karmic.

Runiing grub-install /dev/sda appears to be satisfactory , the three
HDs are listed correctly, but on re-booting the grub legacy menu
appears.

I hope this helps - I would suggest that Karmic is supplied with
Grub-Legacy until these problems are sorted out.

I note that the Windows 7 partitions (three of them) are causing
problems with windows as well, there are many reports on the Internet.
For some reason grub2 does not seem to able to permanently alter the
MBR.

Best wishes

Rod Jones

2009/8/20 Felix Zielcke <email address hidden>:
> Am Mittwoch, den 19.08.2009, 20:19 +0000 schrieb Roderic Jones:
>> Karmic has now been installed but grub (legacy) shows only Jaunty and
>> Windows!!!
>>
>
> grub.cfg looks good.
> So just make sure you load grub2 instead of grub-legacy.
> Maybe the installer put it on a different disk
> or just use grub-install /dev/sda from karmic so grub-legacy gets
> replaced with grub2 in MBR.
>
> --
> Failure to boot Windows 7 after installing Karma
> https://bugs.launchpad.net/bugs/414178
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Roderic Jones

Trout Cottage
Llanvihangel Crucorney
Abergavenny
Monmouthshire
NP7 7NB

Telephone 01873 890050

Revision history for this message

Roderic Jones (rodericj) wrote on 2009-08-22:

#6

Dear Felix,

I have more information. It occurred to me that karmic might not be
booting because its partition started beyond 1TB. I deleted the 1TB
partition at the start of sdc and installed karmic on that space and
it would still only boot windows 7 (on sda) and Jaunty (on sdb) using
grub legacy.

I have ediied the bios to change the hard disc boot order.

sda 1st - Grub legacy boots jaunty or windows 7
sdc 1st - Boots direct to windows 7 - this disk contains Karmic and
the extra windows 7 partition
sdb 1st - Boots grub 2 and windows 7, Karmic or Jaunty

It seems to me that the grub installer is writing the MBR to the wrong disk

I hope this helps. I enclose the output of fdisk-l

Best wishes

Rod Jones

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

Device Boot Start End Blocks Id System
/dev/sda1 1 30401 244196001 7 HPFS/NTFS
/dev/sda4 * 1 1 0 0 Empty
Partition 4 does not end on cylinder boundary.

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

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 60798 488359903+ 83 Linux
/dev/sdb2 60799 60801 24097+ 5 Extended
/dev/sdb5 60799 60801 24066 82 Linux swap / Solaris

Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005363b

Device Boot Start End Blocks Id System
/dev/sdc1 1 127480 1023983068+ 83 Linux
/dev/sdc2 * 127483 127495 102400 7 HPFS/NTFS
/dev/sdc3 127496 182401 441032445 b W95 FAT32
/dev/sdc4 127481 127482 16065 5 Extended
/dev/sdc5 127481 127482 16033+ 82 Linux swap / Solaris

2009/8/20 Felix Zielcke <email address hidden>:
> Am Mittwoch, den 19.08.2009, 20:19 +0000 schrieb Roderic Jones:
>> Karmic has now been installed but grub (legacy) shows only Jaunty and
>> Windows!!!
>>
>
> grub.cfg looks good.
> So just make sure you load grub2 instead of grub-legacy.
> Maybe the installer put it on a different disk
> or just use grub-install /dev/sda from karmic so grub-legacy gets
> replaced with grub2 in MBR.
>
> --
> Failure to boot Windows 7 after installing Karma
> https://bugs.launchpad.net/bugs/414178
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Roderic Jones

Trout Cottage
Llanvihangel Crucorney
Abergavenny
Monmouthshire
NP7 7NB

Telephone 01873 890050

Dear Felix,

I have more information. It occurred to me that karmic might not be
booting because its partition started beyond 1TB. I deleted the 1TB
partition at the start of sdc and installed karmic on that space and
it would still only boot windows 7 (on sda) and Jaunty (on sdb) using
grub legacy.

I have ediied the bios to change the hard disc boot order.

sda 1st - Grub legacy boots jaunty or windows 7
sdc 1st - Boots direct to windows 7 - this disk contains Karmic and
the extra windows 7 partition
sdb 1st - Boots grub 2 and windows 7, Karmic or Jaunty

It seems to me that the grub installer is writing the MBR to the wrong disk

I hope this helps. I enclose the output of fdisk-l

Best wishes

Rod Jones

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

Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       30401   244196001    7  HPFS/NTFS
/dev/sda4   *           1           1           0    0  Empty
Partition 4 does not end on cylinder boundary.

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

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       60798   488359903+  83  Linux
/dev/sdb2           60799       60801       24097+   5  Extended
/dev/sdb5           60799       60801       24066   82  Linux swap / Solaris

Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005363b

Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1      127480  1023983068+  83  Linux
/dev/sdc2   *      127483      127495      102400    7  HPFS/NTFS
/dev/sdc3          127496      182401   441032445    b  W95 FAT32
/dev/sdc4          127481      127482       16065    5  Extended
/dev/sdc5          127481      127482       16033+  82  Linux swap / Solaris

2009/8/20 Felix Zielcke <fzielcke@z-51.de>:
> Am Mittwoch, den 19.08.2009, 20:19 +0000 schrieb Roderic Jones:
>> Karmic has now been installed but grub (legacy) shows only Jaunty and
>> Windows!!!
>>
>
> grub.cfg looks good.
> So just make sure you load grub2 instead of grub-legacy.
> Maybe the installer put it on a different disk
> or just use grub-install /dev/sda from karmic so grub-legacy gets
> replaced with grub2 in MBR.
>
> --
> Failure to boot Windows 7 after installing Karma
> https://bugs.launchpad.net/bugs/414178
> You received this bug notification because you are a direct subscriber
> of the bug.
>

-- 
Roderic Jones

Trout Cottage
Llanvihangel Crucorney
Abergavenny
Monmouthshire
NP7 7NB

Telephone 01873 890050

Felix Zielcke (fzielcke) on 2009-08-22

affects:

grub2 (Ubuntu) → grub-installer (Ubuntu)

Revision history for this message

Roderic Jones (rodericj) wrote on 2009-09-03:

#7

I have tried alpha 5 and the situation is worse. sda (windows 7) boots to grub legacy and gives a choice of Jaunty or windows.

sdb boots to grub2 - karmic no choice

sdc boots to grub2 - karmic no choice.

There is something seriously wrong with the grub installer.

Revision history for this message

apt-ghetto (apt-ghetto) wrote on 2017-03-11:

#8

Thank you for reporting this bug to Ubuntu. Karmic Koala reached EOL on April 30, 2011.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Changed in grub-installer (Ubuntu):
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-05-11:

#9

[Expired for grub-installer (Ubuntu) because there has been no activity for 60 days.]

Changed in grub-installer (Ubuntu):
status:	Incomplete → Expired

Ubuntu
grub-installer package

Failure to boot Windows 7 after installing Karma

Bug Description

Other bug subscribers

Remote bug watches

Ubuntugrub-installer package

Failure to boot Windows 7 after installing Karma

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
grub-installer package