Your message dated Thu, 24 Jul 2008 09:00:55 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Grub fails to find /boot/boot/grub/device.map
has caused the Debian Bug report #477304,
regarding Grub fails to find /boot/boot/grub/device.map
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.)
--
477304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477304
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: grub
Version: 0.97-36
Severity: important
During the runing of the postinst script for a recent kernel upgrade, grub
failed to find `/boot/boot/grub/device.map'. Instead it complained:
grub-probe: error: Cannot open `/boot/grub/device.map'
On a system with a separate /boot partition (such as this one), I
would have thought that device.map should live in /boot/boot/grub
along with menu.lst and friends. Downgrading to grub 0.97-35 did not
help, but downgradingto grub 0.97-27 in stable did.
Here is the output from the failed kernel postinst with grub 0.97-36
(note that grub install dir is correctly found at /boot/boot/grub, but
that grub-probe looks for /boot/grub/device.map):
% sudo aptitude install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following partially installed packages will be configured:
linux-image-2.6.24-1-686-bigmem
0 packages upgraded, 0 newly installed, 0 to remove and 31 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Setting up linux-image-2.6.24-1-686-bigmem (2.6.24-6) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.24-5 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.24-5 was configured last, according to dpkg)
Running postinst hook script update-grub.
Searching for GRUB installation directory ... found: /boot/boot/grub
grub-probe: error: Cannot open `/boot/grub/device.map'
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.24-1-686-bigmem (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-2.6.24-1-686-bigmem
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up linux-image-2.6.24-1-686-bigmem (2.6.24-6) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.24-5 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.24-5 was configured last, according to dpkg)
Running postinst hook script update-grub.
Searching for GRUB installation directory ... found: /boot/boot/grub
grub-probe: error: Cannot open `/boot/grub/device.map'
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.24-1-686-bigmem (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-2.6.24-1-686-bigmem
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub depends on:
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libncurses5 5.6+20080419-1 Shared libraries for terminal hand
grub recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I just tried it out now myself in VMware
grub-legacy boot fine with a seperate /boot partion with just /grub (for it)
and not /boot/boot/grub (real)
During the runing of the postinst script for a recent kernel upgrade, grub
failed to find `/boot/boot/grub/device.map'. Instead it complained:
grub-probe: error: Cannot open `/boot/grub/device.map'
On a system with a separate /boot partition (such as this one), I
would have thought that device.map should live in /boot/boot/grub
along with menu.lst and friends.
Seems like Robert and I didn't read correctly.
Did you move device.map from /boot/grub to /boot/boot/grub ?
Well then it's your own fault.
device.map is only used on grub-install but grub itself doestn't access it on boot
I close this bug.
If anyone is able to tell us how to reproduce this /boot/boot problem, please
feel free to reopen it.
But for me it looks like grub-legacy is able to boot fine with just /grub/ (for it) and not /boot/grub/
--- End Message ---
