Bug#477304: Grub fails to find /boot/boot/grub/device.map
On Wed, Jul 23, 2008 at 11:25 PM, Felix Zielcke <[EMAIL PROTECTED]> wrote: > Please see #475296 > > This bug is about /boot/boot problem, which doestn't happen with grub2 > Only with grub-legacy. Yes, my message was totally offtopic for this bug report. Sorry for the noise. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477304: Grub fails to find /boot/boot/grub/device.map
From: "Teodor" <[EMAIL PROTECTED]> At the configuration question I've answered "no" for the chainloading from grub-legacy. I've rebooted the machine to see if it works and the surprise was that the boot menu was the same, that is from grub-legacy instead of grub2 (with xen options too). The only explanation is that I should have run "grub-install (hd0)" to *really* switch to grub2, but why the menu.lst from grub-legacy was not removed on purge? Please see #475296 This bug is about /boot/boot problem, which doestn't happen with grub2 Only with grub-legacy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477304: Grub fails to find /boot/boot/grub/device.map
On Wed, Jul 23, 2008 at 3:52 AM, Nick Hastings <[EMAIL PROTECTED]> wrote: > Please note that I think it is vitally important to include a > README.Debian file that includes at least the following instructions > > 1. grub-install "(hd0)" > 2. update-grub > > It seems that if the above steps aren't taken the user will be left with > an unbootable system. Should I file a bug report for this? I've just switched to grub2 from grub on my workstation. To be precise, I've installed grub2 (which depends on grub-pc) and purged all the packages related to grub (grub-set-default, grub-splashimages and maybe others). At the configuration question I've answered "no" for the chainloading from grub-legacy. I've rebooted the machine to see if it works and the surprise was that the boot menu was the same, that is from grub-legacy instead of grub2 (with xen options too). The only explanation is that I should have run "grub-install (hd0)" to *really* switch to grub2, but why the menu.lst from grub-legacy was not removed on purge? The second step "update-grub" is already executed automatically at postinstall and it creates the grub.cfg file. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477304: Grub fails to find /boot/boot/grub/device.map
From: "Nick Hastings" <[EMAIL PROTECTED]> Well, I was very suspicious that it had left my system in an unbootable state, with nothing in /usr/share/doc/grub-common to indicate how to make it bootable ... no README.Debian etc Yeah the documentation for grub2 isn't that good as for grub-legacy but it still works the same grub-install copys everything it needs to /boot/grub/ and update-grub generates grub.cfg Ok done and it works: thanks for the new boot loader. Well don't thank me for grub2. I just started to help :) Good that it's now fixed for you. But the real problem is still not fixed. I think it's more grub-legacy then grub-probe what needs a fix for this /boot/boot problem. grub2 doestn't have this problem as you now know, too. It seems that if the above steps aren't taken the user will be left with an unbootable system. Should I file a bug report for this? As I said above it stil works the same as on grub-legacy grub2 is still not the default. Debian installer only asks in expert mode to install it, and then it takes care of it. But yes as already said above, more documentation about this wouldn't be that bad As you can see on the bug reports for grub2 there are already a few for missing documentation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477304: Grub fails to find /boot/boot/grub/device.map
Hi, * Felix Zielcke <[EMAIL PROTECTED]> [080723 05:04]: > Hello, > > From: "Nick Hastings" <[EMAIL PROTECTED]> > >> Seems to be no errors but it seems that /boot/boot/ is being completely >> ignored. Please see the results of the install, linux-image reconfigure >> and file listing under /boot below. > > I used grub-legacy long ago, and I think I never used it with a /boot > partition. But I did use grub2 with a seperate /boot partition. It > works fine with just /grub instead of /boot/grub Well, I was very suspicious that it had left my system in an unbootable state, with nothing in /usr/share/doc/grub-common to indicate how to make it bootable ... no README.Debian etc >> I think I will downgrade to the old grub > > Please don't, please try grub2 :) If you call grub-install then the > *.img and *.mod files get copied to /boot/grub/ which it needs. Ok done and it works: thanks for the new boot loader. Please note that I think it is vitally important to include a README.Debian file that includes at least the following instructions 1. grub-install "(hd0)" 2. update-grub It seems that if the above steps aren't taken the user will be left with an unbootable system. Should I file a bug report for this? Thanks again, Nick. signature.asc Description: Digital signature
Bug#477304: Grub fails to find /boot/boot/grub/device.map
Hello, From: "Nick Hastings" <[EMAIL PROTECTED]> Seems to be no errors but it seems that /boot/boot/ is being completely ignored. Please see the results of the install, linux-image reconfigure and file listing under /boot below. I used grub-legacy long ago, and I think I never used it with a /boot partition. But I did use grub2 with a seperate /boot partition. It works fine with just /grub instead of /boot/grub I think I will downgrade to the old grub Please don't, please try grub2 :) If you call grub-install then the *.img and *.mod files get copied to /boot/grub/ which it needs. You can delete /boot/boot and reboot. It will work fine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477304: Debian bug #477304 Grub fails to find /boot/boot/grub/device.map
Hi,
* Felix Zielcke <[EMAIL PROTECTED]> [080720 21:27]:
> Is this still an issue? Can you please try it with grub-pc
> 1.96+20080704-2 currently in testing/unstable
Seems to be no errors but it seems that /boot/boot/ is being completely
ignored. Please see the results of the install, linux-image reconfigure
and file listing under /boot below.
$ sudo aptitude install grub-pc
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following NEW packages will be installed:
grub-pc
The following packages will be REMOVED:
grub{a}
0 packages upgraded, 1 newly installed, 1 to remove and 138 not
upgraded.
Need to get 1101kB of archives. After unpacking 2044kB will be used.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
Get:1 http://hat.kek.jp lenny/main grub-pc 1.96+20080704-2 [1101kB]
Fetched 1101kB in 4s (255kB/s)
Preconfiguring packages ...
(Reading database ... 318733 files and directories currently installed.)
Removing grub ...
Processing triggers for man-db ...
Selecting previously deselected package grub-pc.
(Reading database ... 318685 files and directories currently installed.)
Unpacking grub-pc (from .../grub-pc_1.96+20080704-2_i386.deb) ...
Processing triggers for man-db ...
Setting up grub-pc (1.96+20080704-2) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
$ sudo dpkg-reconfigure linux-image-2.6.24-1-686-bigmem
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
Running postinst hook script update-grub.
Updating /boot/grub/grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.24-1-686-bigmem
Found initrd image: /boot/initrd.img-2.6.24-1-686-bigmem
Found memtest86+ image: /boot/memtest86+.bin
done
$ tree -Dt /boot
/boot
|-- [Jul 22 8:42] grub
| |-- [Jul 22 8:42] grub.cfg
| |-- [Jul 22 8:42] device.map
| |-- [Jul 22 8:41] ascii.pff
| -- [Jul 22 8:41] debian-blueish-wallpaper-640x480.png
|-- [Jul 22 8:42] initrd.img-2.6.24-1-686-bigmem
|-- [Jun 26 10:12] initrd.img-2.6.24-1-686-bigmem.bak
|-- [May 8 13:50] System.map-2.6.24-1-686-bigmem
|-- [May 8 13:50] config-2.6.24-1-686-bigmem
|-- [May 8 13:49] vmlinuz-2.6.24-1-686-bigmem
|-- [Apr 24 4:24] memtest86+.bin
|-- [Dec 16 2005] boot
| -- [Jul 22 8:48] grub
| |-- [Jun 17 16:41] menu.lst
| |-- [Jun 17 16:41] menu.lst~
| |-- [Apr 23 12:32] stage2
| |-- [Apr 23 12:32] default
| |-- [Apr 23 12:32] e2fs_stage1_5
| |-- [Apr 23 12:32] fat_stage1_5
| |-- [Apr 23 12:32] jfs_stage1_5
| |-- [Apr 23 12:32] minix_stage1_5
| |-- [Apr 23 12:32] reiserfs_stage1_5
| |-- [Apr 23 12:32] stage1
| |-- [Apr 23 12:32] xfs_stage1_5
| -- [Nov 28 2005] device.map
-- [Jan 21 2004] lost+found [error opening dir]
I think I will down grade to the old grub: I can currently afford the
time potentially needed to recover a possibly unbootable machine.
Cheers,
Nick.
signature.asc
Description: Digital signature
Bug#477304: Debian bug #477304 Grub fails to find /boot/boot/grub/device.map
Is this still an issue? Can you please try it with grub-pc 1.96+20080704-2 currently in testing/unstable -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#477304: Grub fails to find /boot/boot/grub/device.map
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
