Your message dated Tue, 13 Jul 2010 03:11:40 +0100
with message-id <[email protected]>
and subject line Re: Bug#586180: grub-probe tries to stat /dev/hda that doesn't
exist
has caused the Debian Bug report #586180,
regarding grub-probe tries to stat /dev/hda that doesn't exist
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.)
--
586180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586180
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Subject: grub-pc: grub-probe error when /dev/hda does not exist
Package: grub-pc
Version: 1.98+20100614-2
Severity: normal
Tags: upstream
*** Please type your report below this line ***
When installing grub-pc I now get the following error output:
Setting up grub-pc (1.98+20100614-2) ...
/usr/sbin/grub-probe: error: cannot stat `/dev/hda'.
Generating grub.cfg ...
...
Recent kernel changes made /dev/hd? dissapear, replaced by /dev/sd? for
both pata and sata HDDs, hence no /dev/hd? are created.
Additionally, in order to cope with these changes UUIDs are now used
in /etc/fstab. For Windows entries, however, which also have UUIDs in
fstab, /dev/sd? are written to grub.cfg. Confusing!
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/disk/by-uuid/aec662ba-91d0-4201-9bd1-a2e9028cbd41 / ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda5 /var ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sda6 /usr ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sda7 /mnt/hda7 ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sdb1 /home ext4 rw,relatime,barrier=1,data=ordered 0 0
*********************** END /proc/mounts
*********************** BEGIN /boot/grub/device.map
(hd0) /dev/sda
(hd1) /dev/sdb
(hd2) /dev/sdc
*********************** END /boot/grub/device.map
*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set fb87eb32-ec18-40c1-93fc-f63f60f39964
if loadfont /share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
fi
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set aec662ba-91d0-4201-9bd1-a2e9028cbd41
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, with Linux 2.6.32-5-686' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set aec662ba-91d0-4201-9bd1-a2e9028cbd41
echo 'Loading Linux 2.6.32-5-686 ...'
linux /boot/vmlinuz-2.6.32-5-686
root=UUID=aec662ba-91d0-4201-9bd1-a2e9028cbd41 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686 (recovery mode)'
--class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set aec662ba-91d0-4201-9bd1-a2e9028cbd41
echo 'Loading Linux 2.6.32-5-686 ...'
linux /boot/vmlinuz-2.6.32-5-686
root=UUID=aec662ba-91d0-4201-9bd1-a2e9028cbd41 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-3-686' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set aec662ba-91d0-4201-9bd1-a2e9028cbd41
echo 'Loading Linux 2.6.32-3-686 ...'
linux /boot/vmlinuz-2.6.32-3-686
root=UUID=aec662ba-91d0-4201-9bd1-a2e9028cbd41 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-3-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-3-686 (recovery mode)'
--class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set aec662ba-91d0-4201-9bd1-a2e9028cbd41
echo 'Loading Linux 2.6.32-3-686 ...'
linux /boot/vmlinuz-2.6.32-3-686
root=UUID=aec662ba-91d0-4201-9bd1-a2e9028cbd41 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-3-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-2-686' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set aec662ba-91d0-4201-9bd1-a2e9028cbd41
echo 'Loading Linux 2.6.32-2-686 ...'
linux /boot/vmlinuz-2.6.32-2-686
root=UUID=aec662ba-91d0-4201-9bd1-a2e9028cbd41 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-2-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-2-686 (recovery mode)'
--class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set aec662ba-91d0-4201-9bd1-a2e9028cbd41
echo 'Loading Linux 2.6.32-2-686 ...'
linux /boot/vmlinuz-2.6.32-2-686
root=UUID=aec662ba-91d0-4201-9bd1-a2e9028cbd41 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-2-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.31-1-686' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set aec662ba-91d0-4201-9bd1-a2e9028cbd41
echo 'Loading Linux 2.6.31-1-686 ...'
linux /boot/vmlinuz-2.6.31-1-686
root=UUID=aec662ba-91d0-4201-9bd1-a2e9028cbd41 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.31-1-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.31-1-686 (recovery mode)'
--class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set aec662ba-91d0-4201-9bd1-a2e9028cbd41
echo 'Loading Linux 2.6.31-1-686 ...'
linux /boot/vmlinuz-2.6.31-1-686
root=UUID=aec662ba-91d0-4201-9bd1-a2e9028cbd41 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.31-1-686
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows NT/2000/XP (on /dev/sda1)" {
insmod part_msdos
insmod fat
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 693d-1e3b
drivemap -s (hd0) ${root}
chainloader +1
}
menuentry "Microsoft Windows XP Home Edition (on /dev/sda2)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set f0fc6717fc66d77e
drivemap -s (hd0) ${root}
chainloader +1
}
### 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.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
*********************** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set
to C)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0] 1.5.32 Debian configuration
management sy
ii grub-common 1.98+20100614-2 GRand Unified Bootloader,
version
ii libc6 2.11.2-1 Embedded GNU C Library:
Shared lib
ii libdevmapper1.02.1 2:1.02.48-1 The Linux Kernel Device
Mapper use
ii ucf 3.0025 Update Configuration File:
preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
ii desktop-base 5.0.5 common files for the Debian
Deskto
-- debconf information:
grub2/kfreebsd_cmdline:
* grub2/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
grub-pc/kopt_extracted: true
grub-pc/postrm_purge_boot_grub: false
grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default: quiet
* grub-pc/install_devices: /dev/hda
--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 1.98+20100702-1
On Thu, Jun 17, 2010 at 09:04:04AM +0200, Svante Signell wrote:
> When installing grub-pc I now get the following error output:
>
> Setting up grub-pc (1.98+20100614-2) ...
> /usr/sbin/grub-probe: error: cannot stat `/dev/hda'.
> Generating grub.cfg ...
> ...
>
> Recent kernel changes made /dev/hd? dissapear, replaced by /dev/sd? for
> both pata and sata HDDs, hence no /dev/hd? are created.
[...]
> * grub-pc/install_devices: /dev/hda
Thanks for your report. This should be fixed by the changes in
1.98+20100702-1 to store by-id device names in the debconf database
rather than traditional (and unstable) device names.
--
Colin Watson [[email protected]]
--- End Message ---
