Your message dated Thu, 24 Jul 2008 13:07:46 +0200
with message-id <[EMAIL PROTECTED]>
and subject line
has caused the Debian Bug report #467501,
regarding grub uses fd prefix even if it's neither in device.map nor grub.cfg
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.)
--
467501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467501
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: grub-pc
Version: 1.96+20080219-2
Severity: important
I have installed grub-pc on my shiny new AMD64 box. After verifying it
loaded fine when chainloaded from legacy grub I typed
"upgrade-from-grub-legacy" and rebooted. I was rewarded with the grub
rescue shell.
For some reason it has decided that "prefix=(fd0)/boot/grub" rather than
"prefix=(md0)/boot/grub". If I do something along the lines of (from
memory, but I believe this was the rough gist):
root (md0)
set prefix=(md0)/boot/grub
insmod /boot/grub/boot.mod
normal
then I get the expected boot menu.
I can't see any sign of fd0 in /boot/grub so I'm not even sure how to
fix this locally myself at present.
-- Package-specific info:
*********************** BEGIN
/dev/md0 / ext3 rw,errors=remount-ro,data=ordered 0 0
/dev/md0 /dev/.static/dev ext3 rw,errors=remount-ro,data=ordered 0 0
/dev/mapper/satavg-home /home ext3 rw,data=ordered 0 0
/dev/mapper/satavg-tmp /tmp ext3 rw,data=ordered 0 0
/dev/mapper/satavg-usr /usr ext3 rw,data=ordered 0 0
/dev/mapper/satavg-var /var ext3 rw,data=ordered 0 0
*********************** END
*********************** BEGIN /boot/grub/device.map
(hd0) /dev/sda
(hd1) /dev/sdb
*********************** END /boot/grub/device.map
*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/update-grub using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
insmod lvm
set default=0
set timeout=5
set root=(md0)
if font (satavg-usr)/share/grub/unicode.pff ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
terminal gfxterm
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod png
if background_image
(satavg-usr)/share/images/desktop-base/debian-blueish-wallpaper-640x480.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_hurd ###
### END /etc/grub.d/10_hurd ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, linux 2.6.25-rc3" {
linux (md0)/boot/vmlinuz-2.6.25-rc3 root=/dev/md0 ro quiet
initrd (md0)/boot/initrd.img-2.6.25-rc3
}
menuentry "Debian GNU/Linux, linux 2.6.25-rc3 (single-user mode)" {
linux (md0)/boot/vmlinuz-2.6.25-rc3 root=/dev/md0 ro single quiet
initrd (md0)/boot/initrd.img-2.6.25-rc3
}
menuentry "Debian GNU/Linux, linux 2.6.25-rc2-git6" {
linux (md0)/boot/vmlinuz-2.6.25-rc2-git6 root=/dev/md0 ro quiet
initrd (md0)/boot/initrd.img-2.6.25-rc2-git6
}
menuentry "Debian GNU/Linux, linux 2.6.25-rc2-git6 (single-user mode)" {
linux (md0)/boot/vmlinuz-2.6.25-rc2-git6 root=/dev/md0 ro single quiet
initrd (md0)/boot/initrd.img-2.6.25-rc2-git6
}
menuentry "Debian GNU/Linux, linux 2.6.24-1-amd64" {
linux (md0)/boot/vmlinuz-2.6.24-1-amd64 root=/dev/md0 ro quiet
initrd (md0)/boot/initrd.img-2.6.24-1-amd64
}
menuentry "Debian GNU/Linux, linux 2.6.24-1-amd64 (single-user mode)" {
linux (md0)/boot/vmlinuz-2.6.24-1-amd64 root=/dev/md0 ro single quiet
initrd (md0)/boot/initrd.img-2.6.24-1-amd64
}
menuentry "Debian GNU/Linux, linux 2.6.24" {
linux (md0)/boot/vmlinuz-2.6.24 root=/dev/md0 ro quiet
initrd (md0)/boot/initrd.img-2.6.24
}
menuentry "Debian GNU/Linux, linux 2.6.24 (single-user mode)" {
linux (md0)/boot/vmlinuz-2.6.24 root=/dev/md0 ro single quiet
initrd (md0)/boot/initrd.img-2.6.24
}
menuentry "Debian GNU/Linux, linux 2.6.22-3-amd64" {
linux (md0)/boot/vmlinuz-2.6.22-3-amd64 root=/dev/md0 ro quiet
initrd (md0)/boot/initrd.img-2.6.22-3-amd64
}
menuentry "Debian GNU/Linux, linux 2.6.22-3-amd64 (single-user mode)" {
linux (md0)/boot/vmlinuz-2.6.22-3-amd64 root=/dev/md0 ro single quiet
initrd (md0)/boot/initrd.img-2.6.22-3-amd64
}
### END /etc/grub.d/10_linux ###
*********************** END /boot/grub/grub.cfg
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub-pc depends on:
ii base-files 4.0.2 Debian base system miscellaneous f
ii debconf [debconf-2.0] 1.5.19 Debian configuration management sy
ii libc6 2.7-8 GNU C Library: Shared libraries
ii liblzo1 1.08-3 data compression library (old vers
ii libncurses5 5.6+20080203-1 Shared libraries for terminal hand
grub-pc recommends no packages.
-- debconf information:
grub-pc/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
--- End Message ---
--- Begin Message ---
Version: grub2/1.96+20080704-2
Ok sorry for the noise.
I was told to make a new one, to make it more clear.
The fd prefix on a md device should be fixed and that's what this bug is about
--- End Message ---
