Your message dated Wed, 06 Jan 2010 14:31:33 +0100
with message-id <[email protected]>
and subject line Re: Bug#561294: core.img is unusually large, grub-pc fails to
install grub mbr.
has caused the Debian Bug report #561294,
regarding core.img is unusually large, grub-pc fails to install grub mbr.
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.)
--
561294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561294
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-pc
Version: 1.97+experimental.20091213-1
Severity: important
I get the following warning and error when I attempt to install or update grub:
/usr/sbin/grub-setup: warn: Your core.img is unusually large. It won't fit in
the embedding area.
/usr/sbin/grub-setup: error: Embedding is not possible, but this is required
when the root device is on a RAID array or LVM volume.
my / (root,boot) partition is a lvm volume, as is my swap. When I first
installed the OS (debian sid) a month and a half ago, everything including
grub-pc installed. And the machine would boot, albeit with grub taking several
seconds to actually show the boot menu (it would briefly flash to the grub
rescue cli).
sdf and sdg both have a single dos/pc style partition which are combined into
a md-raid1 volume, which is "exported" as a LVM2 volume group, which is where
/, /home, and swap live (as well as several KVM vm volumes).
I hessitate to reboot this machine as it hosts my firewall, a couple public
websites, and asterisk to handle my home phone. If grub failed, it would take
all my services down, including my internet for an unknown length of time.
The rest of the disks are unrelated, and make up a 5x1TB raid5 volume.
I asked about this on #[email protected] and one person said it might
be related to compiler options used, which bloat the size of the grub driver
modules.
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/mapper/vg0-root / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/vg0-home /home ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/md1 /mnt/boris/data xfs
rw,noatime,nodiratime,swalloc,attr2,largeio,nobarrier,allocsize=524288k,logbufs=8,sunit=1024,swidth=4096,noquota
0 0
*********************** END /proc/mounts
*********************** BEGIN /boot/grub/device.map
(fd0) /dev/fd0
(hd0) /dev/sda
(hd1) /dev/sdb
(hd2) /dev/sdc
(hd3) /dev/sdd
(hd4) /dev/sde
(hd5) /dev/sdf
(hd6) /dev/sdg
*********************** END /boot/grub/device.map
*********************** BEGIN /boot/grub/grub.cfg
#
# 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 ###
load_env
set default=4
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
insmod raid
insmod mdraid
insmod lvm
insmod ext2
set root=(vg0-root)
search --no-floppy --fs-uuid --set 50fd76c2-10cc-48d6-8461-da6fba2f916e
if loadfont /usr/share/grub/unicode.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 locale_dir=/boot/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set gfxpayload=keep
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, with Linux 2.6.31-1-amd64" {
insmod raid
insmod mdraid
insmod lvm
insmod ext2
set root=(vg0-root)
search --no-floppy --fs-uuid --set 50fd76c2-10cc-48d6-8461-da6fba2f916e
linux /boot/vmlinuz-2.6.31-1-amd64 root=/dev/mapper/vg0-root ro quiet
initrd /boot/initrd.img-2.6.31-1-amd64
}
menuentry "Debian GNU/Linux, with Linux 2.6.31-1-amd64 (recovery mode)" {
insmod raid
insmod mdraid
insmod lvm
insmod ext2
set root=(vg0-root)
search --no-floppy --fs-uuid --set 50fd76c2-10cc-48d6-8461-da6fba2f916e
linux /boot/vmlinuz-2.6.31-1-amd64 root=/dev/mapper/vg0-root ro
single
initrd /boot/initrd.img-2.6.31-1-amd64
}
menuentry "Debian GNU/Linux, with Linux 2.6.26-2-amd64" {
insmod raid
insmod mdraid
insmod lvm
insmod ext2
set root=(vg0-root)
search --no-floppy --fs-uuid --set 50fd76c2-10cc-48d6-8461-da6fba2f916e
linux /boot/vmlinuz-2.6.26-2-amd64 root=/dev/mapper/vg0-root ro quiet
initrd /boot/initrd.img-2.6.26-2-amd64
}
menuentry "Debian GNU/Linux, with Linux 2.6.26-2-amd64 (recovery mode)" {
insmod raid
insmod mdraid
insmod lvm
insmod ext2
set root=(vg0-root)
search --no-floppy --fs-uuid --set 50fd76c2-10cc-48d6-8461-da6fba2f916e
linux /boot/vmlinuz-2.6.26-2-amd64 root=/dev/mapper/vg0-root ro
single
initrd /boot/initrd.img-2.6.26-2-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
#menuentry "Xen 3.4 / Debian GNU/Linux, with Linux 2.6.31-1-amd64" {
# insmod raid
# insmod mdraid
# insmod lvm
# insmod ext2
# set root=(vg0-root)
# search --no-floppy --fs-uuid --set 50fd76c2-10cc-48d6-8461-da6fba2f916e
# multiboot /boot/xen-3.4-amd64.gz
# module /boot/vmlinuz-2.6.31-1-amd64 root=/dev/mapper/vg0-root ro
console=tty0
# module /boot/initrd.img-2.6.31-1-amd64
#}
#
#menuentry "Xen 3.4 / Debian GNU/Linux, with Linux 2.6.31-1-amd64 (recovery
mode)" {
# insmod raid
# insmod mdraid
# insmod lvm
# insmod ext2
# set root=(vg0-root)
# search --no-floppy --fs-uuid --set 50fd76c2-10cc-48d6-8461-da6fba2f916e
# multiboot /boot/xen-3.4-amd64.gz
# module /boot/vmlinuz-2.6.31-1-amd64 root=/dev/mapper/vg0-root ro
single console=tty0
# module /boot/initrd.img-2.6.31-1-amd64
#}
### END /etc/grub.d/40_custom ###
*********************** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-pc depends on:
ii debconf [de 1.5.28 Debian configuration management sy
ii grub-common 1.97+experimental.20091213-1 GRand Unified Bootloader, version
ii libc6 2.10.2-2 GNU C Library: Shared libraries
ii ucf 3.0025 Update Configuration File: preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
pn desktop-base <none> (no description available)
-- debconf information:
grub2/kfreebsd_cmdline:
* grub2/linux_cmdline:
grub-pc/chainload_from_menu.lst: true
grub-pc/kopt_extracted: false
* grub-pc/install_devices: /dev/sdf, /dev/sdg
grub-pc/postrm_purge_boot_grub: false
grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default: quiet
--- End Message ---
--- Begin Message ---
Am Mittwoch, den 06.01.2010, 14:01 +0100 schrieb Markus Neviadomski:
> This Bug should be closed. Its similar to the newer bug 562953, which
> was resolved. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562953
>
> Ive installed yesterday the latest grub2 version 1.98~20100101-1, and
> all was fine!
>
> Thanks,
> Markus
Thanks. Closing now.
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
--- End Message ---
