Your message dated Sun, 31 May 2009 07:46:27 +0200
with message-id <1243748787.3397.0.ca...@fz.local>
and subject line Re: Bug#531191: grub-pc update: system unbootable
has caused the Debian Bug report #531191,
regarding grub-pc update: system unbootable
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.)
--
531191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-pc
Version: 1.96+20090523-1
Severity: critical
Justification: breaks the whole system
Since last update my system is unbootable.
At start after the bios:
Error:the symbol 'grub_machine_fini' not found
Then, I have a grub-rescue prompt
This error becomes after a grub-install. If I downgrade to
grub-pc/testing, a grub-install command make my system bootable.
I think that this problem is different of #530927 #530357
because I've modified /etc/default/grub without any change.
The only way I can boot on this grub install on /dev/sdb is with
another grub from another linux on /dev/sda. If I make a chainloader
from this old grub, the grub on /dev/sdb works. In fact the problem
becomes when I want to boot directly from bios to /dev/sdb.
reagrds
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/sdb1 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sdb2 /home ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/sdb3 /mnt/musik ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/sdb6 /mnt/video ext4 rw,noatime,barrier=1,data=ordered 0 0
*********************** END /proc/mounts
*********************** BEGIN /boot/grub/device.map
(hd0) /dev/hda
(hd1) /dev/sda
(hd2) /dev/sdb
*********************** 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 and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=8
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
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
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
insmod png
if background_image /boot/grub/moreblue-orbit-grub.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, linux 2.6.29-2-amd64" {
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
linux /boot/vmlinuz-2.6.29-2-amd64 root=/dev/sdb1 ro vga=795
initrd /boot/initrd.img-2.6.29-2-amd64
}
menuentry "Debian GNU/Linux, linux 2.6.29-2-amd64 (recovery mode)" {
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
linux /boot/vmlinuz-2.6.29-2-amd64 root=/dev/sdb1 ro single vga=795
initrd /boot/initrd.img-2.6.29-2-amd64
}
menuentry "Debian GNU/Linux, linux 2.6.26-2-amd64" {
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
linux /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb1 ro vga=795
initrd /boot/initrd.img-2.6.26-2-amd64
}
menuentry "Debian GNU/Linux, linux 2.6.26-2-amd64 (recovery mode)" {
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
linux /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb1 ro single vga=795
initrd /boot/initrd.img-2.6.26-2-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/29_gentoo ###
menuentry "Gentoo GNU/Linux x86_64 (on /dev/sda2)" {
set root=(hd1,2)
linux /boot/kernel-genkernel-x86_64-2.6.29-gentoo-r5-libre
root=/dev/ram0 real_root=/dev/sda2 rootfstype=ext4 init=/linuxrc udev doscsi
video=intelfb:mode=1440x900...@60
initrd /boot/initramfs-genkernel-x86_64-2.6.29-gentoo-r5-libre
}
### END /etc/grub.d/29_gentoo ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###
*********************** END /boot/grub/grub.cfg
*** /tmp/reportbug-grub-pc-20090530-4565-mhqSX_
Subject: grub-pc update: system unbootable
Package: grub-pc
Version: 1.96+20090523-1
Justification: breaks the whole system
Severity: critical
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/sdb1 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sdb2 /home ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/sdb3 /mnt/musik ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/sdb6 /mnt/video ext4 rw,noatime,barrier=1,data=ordered 0 0
*********************** END /proc/mounts
*********************** BEGIN /boot/grub/device.map
(hd0) /dev/hda
(hd1) /dev/sda
(hd2) /dev/sdb
*********************** 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 and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=8
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
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
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
insmod png
if background_image /boot/grub/moreblue-orbit-grub.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, linux 2.6.29-2-amd64" {
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
linux /boot/vmlinuz-2.6.29-2-amd64 root=/dev/sdb1 ro vga=795
initrd /boot/initrd.img-2.6.29-2-amd64
}
menuentry "Debian GNU/Linux, linux 2.6.29-2-amd64 (recovery mode)" {
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
linux /boot/vmlinuz-2.6.29-2-amd64 root=/dev/sdb1 ro single vga=795
initrd /boot/initrd.img-2.6.29-2-amd64
}
menuentry "Debian GNU/Linux, linux 2.6.26-2-amd64" {
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
linux /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb1 ro vga=795
initrd /boot/initrd.img-2.6.26-2-amd64
}
menuentry "Debian GNU/Linux, linux 2.6.26-2-amd64 (recovery mode)" {
set root=(hd2,1)
search --fs-uuid --set b9ff094c-15ef-4c4a-a513-62b0178f0b00
linux /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sdb1 ro single vga=795
initrd /boot/initrd.img-2.6.26-2-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/29_gentoo ###
menuentry "Gentoo GNU/Linux x86_64 (on /dev/sda2)" {
set root=(hd1,2)
linux /boot/kernel-genkernel-x86_64-2.6.29-gentoo-r5-libre
root=/dev/ram0 real_root=/dev/sda2 rootfstype=ext4 init=/linuxrc udev doscsi
video=intelfb:mode=1440x900...@60
initrd /boot/initramfs-genkernel-x86_64-2.6.29-gentoo-r5-libre
}
### END /etc/grub.d/29_gentoo ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###
*********************** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (998, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy
ii grub-common 1.96+20090523-1 GRand Unified Bootloader, version
ii libc6 2.9-12 GNU C Library: Shared libraries
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
ii desktop-base 5.0.5 common files for the Debian Deskto
ii genisoimage 9:1.1.9-1 Creates ISO-9660 CD-ROM filesystem
pn os-prober <none> (no description available)
-- debconf information:
* grub-pc/install_devices: /dev/sdb
* grub-pc/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (998, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy
ii grub-common 1.96+20090523-1 GRand Unified Bootloader, version
ii libc6 2.9-12 GNU C Library: Shared libraries
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
ii desktop-base 5.0.5 common files for the Debian Deskto
ii genisoimage 9:1.1.9-1 Creates ISO-9660 CD-ROM filesystem
pn os-prober <none> (no description available)
-- debconf information:
* grub-pc/install_devices: /dev/sdb
* grub-pc/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
--- End Message ---
--- Begin Message ---
Am Samstag, den 30.05.2009, 23:28 +0200 schrieb steph:
> Thanks for your answer.
> I'm sorry because the problem came from my bios config.
> The thing that made me thinking that was a bug is that was working
> with grub 1.96+20090317-1 and not with the last update.
> Please accept my apologies.
> Is it possible to delete my bug report?
No, bug reports can't be deleted just closed and then after 28 days they
get hidden in the archives.
--
Felix Zielcke
--- End Message ---
