Bug#511473: marked as done (debian-installer: daily build seems to generate of by one partition numbers for Windows boot)
Your message dated Sun, 11 Jan 2009 12:51:05 +0100
with message-id <200901111251.06411.elendil@planet.nl>
and subject line Re: Bug#511473: debian-installer: daily build seems to generate of by one partition numbers for Windows boot
has caused the Debian Bug report #511473,
regarding debian-installer: daily build seems to generate of by one partition numbers for Windows boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
511473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511473
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Severity: normal
I downloaded the installed as a daily build yesterday (so, no idea where to
find a version number if there is one) and reinstalled one of my old systems.
This old system has an old Windows installation on /dev/hda1. I chose grub2 as
boot manager in the installer, which worked nicely until I tried to boot into
Windows which was not possible because the entry in grub.cfg said "set
root=(hd0,0)" instead of "set root=(hd0,1)". Changing this made the system boot
again.
Michael
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Sunday 11 January 2009, Michael Meskes wrote:
> I downloaded the installed as a daily build yesterday (so, no idea
> where to find a version number if there is one) and reinstalled one of
> my old systems. This old system has an old Windows installation on
> /dev/hda1. I chose grub2 as boot manager in the installer, which worked
> nicely until I tried to boot into Windows which was not possible
> because the entry in grub.cfg said "set root=(hd0,0)" instead of "set
> root=(hd0,1)". Changing this made the system boot again.
Closing as this issue is already well known. See open BRs against
grub-installer.
Cheers,
FJP
--- End Message ---
Reply to: