Your message dated Fri, 7 Nov 2008 16:09:50 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#504752: grub2: fails to detect free space for
embedding core on GPT labeled disks
has caused the Debian Bug report #504752,
regarding grub2: fails to detect free space for embedding core on GPT labeled
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 [EMAIL PROTECTED]
immediately.)
--
504752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504752
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: grub2
Version: 1.96+20080724-11
Severity: important
grub2 fails to detect free space for embedding it's core.img when necessary
(e.g. lvm-root) when being confronted with a GPT disklabel.
With this layout (output from "parted -l")
Model: Areca raid10-PV (scsi)
Disk /dev/sdc: 200GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8225kB 32.0GB 32.0GB
'grub-install /dev/sdc' returns with
grub-setup: error: Core image is too big for embedding, but this is required
when
the root device is on a RAID array or LVM volume.
I explicitly made that partition start one sector later than default, because
GPT partitions apparently start at "17.4kB" compared to the "32.2kB" for msdos
when created with parted/gnu-fdisk, and the "17.4kB" might be a bit too few
space for the ~25-30KiB the core.img takes with the needed modules included.
When using a msdos disklabel:
Model: Areca raid10-PV (scsi)
Disk /dev/sdc: 200GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 32.0GB 32.0GB primary
everything works fine.
Given that multi-terabyte disks will be available very soon (and you easily
reach this limit with RAID even today) and the flexibility a LV-root offers, I
tagged this as important.
best regards,
Michael
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub2 depends on:
ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii grub-pc 1.96+20080724-11 GRand Unified Bootloader, version
grub2 recommends no packages.
grub2 suggests no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
On Thu, Nov 06, 2008 at 09:48:33PM +0100, Michael Renner wrote:
> Package: grub2
> Version: 1.96+20080724-11
> Severity: important
>
> grub2 fails to detect free space for embedding it's core.img when necessary
> (e.g. lvm-root) when being confronted with a GPT disklabel.
Post-MBR area is occupied with GPT Metadata and can't be used, see
http://en.wikipedia.org/wiki/GUID_Partition_Table
If you want embedding (and it's pretty reasonable that you do) elsewhere in
an unused area of the disk, create a BIOS Boot partition. GRUB detects and
uses it when available.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
--- End Message ---
