Your message dated Fri, 6 Dec 2013 13:00:16 +0000
with message-id <20131206130016.gj16...@riva.ucam.org>
and subject line Re: Bug#679817: grub-common: broken chainloader entry in
grub.cfg for windows systems in GPT partitioned disks
has caused the Debian Bug report #679817,
regarding grub-common: broken chainloader entry in grub.cfg for windows systems
in GPT partitioned disks
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 ow...@bugs.debian.org
immediately.)
--
679817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-common
Version: 1.99-22.1
Severity: normal
Dear Maintainer,
Everytime grub-update is ran then a new grub.cfg is generated. However, the
windows entry is broken for systems using GPT partitions.
It is not possible to boot to windows from grub boot menu, unless the generated
grub.cfg is manually fixed.
The script responsible for generating the boot options for others OSs is
/etc/grub.d/30_os-prober (which is part of this package).
I'm using grub-efi on a clean wheezy install.
The resulting entry in grub.cfg is the following:
menuentry "Windows 7 (loader) (on /dev/sda3)" --class windows --class os {
insmod part_gpt
insmod ntfs
set root='(hd0,gpt3)'
search --no-floppy --fs-uuid --set=root 1A62308062305F11
chainloader +1
}
The expected entry in grub.cfg would be (and this one works):
menuentry "Windows 7 (loader) (on /dev/sda3)" --class windows --class os {
insmod part_gpt
insmod ntfs
insmod fat
insmod chain
set root='(hd0,gpt3)'
search --no-floppy --fs-uuid --set=root 1A62308062305F11
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
There is still the issue of the recovery partition, which I suspect the efi
file to be:
/EFI/Microsoft/Boot/bootmgr.efi
But I haven't tested this one yet.
Thanks
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-common depends on:
ii gettext-base 0.18.1.1-9
ii libc6 2.13-33
ii libdevmapper1.02.1 2:1.02.74-4
ii libfreetype6 2.4.9-1
ii libfuse2 2.9.0-2
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages grub-common recommends:
ii os-prober 1.53
Versions of packages grub-common suggests:
ii desktop-base 6.0.7
pn grub-emu <none>
pn multiboot-doc <none>
pn xorriso <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 1.99-27.1
Control: fixed -1 1.99-27+deb7u1
On Sun, Jul 01, 2012 at 08:25:15PM +0100, Ghost Shell wrote:
> Everytime grub-update is ran then a new grub.cfg is generated.
> However, the windows entry is broken for systems using GPT partitions.
> It is not possible to boot to windows from grub boot menu, unless the
> generated grub.cfg is manually fixed.
Sorry for my delay in responding to this bug. This was fixed just
before the wheezy release:
grub2 (1.99-27.1) unstable; urgency=medium
* NMU
* Add entries for Windows Boot Manager found via UEFI in
os-prober. Closes: #698914 before the Wheezy release.
-- Steve McIntyre <93...@debian.org> Fri, 26 Apr 2013 23:53:34 +0100
Thanks,
--
Colin Watson [cjwat...@debian.org]
--- End Message ---
