Bug#441888: marked as done (linux-image-2.6.18-5-686: upgrade overwrites /boot/grub/menu.lst)
Your message dated Wed, 12 Sep 2007 13:38:34 +0300
with message-id <46E7C1AA.60104@yaakovnet.net>
and subject line Please close this bug report
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: linux-image-2.6.18-5-686
Version: 2.6.18.dfsg.1-13etch2
Severity: normal
A kernel upgrade from security.debian.org overwrote my
/boot/grub/menu.lst file --- making my other linux partitions
unaccessible. As it happened, the new kernel did not boot correctly
because of an unrelated minor problem --- and hence my whole PC became
unbootable.
Note: During system installation, the installer correctly discovers
other linux partitions and includes them into the new
/boot/grub/menu.lst file. The same functionality should be included
into kernel upgrades. Not beeing an expert, I don't know where that
code is located.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-5-686 depends on:
ii coreutils 5.97-5.3 The GNU core utilities
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii initramfs-tools [linux-initra 0.85h tools for generating an initramfs
ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.18-5-686 recommends:
ii libc6-i686 2.3.6.ds1-13etch2 GNU C Library: Shared libraries [i
-- debconf information:
linux-image-2.6.18-5-686/postinst/create-kimage-link-2.6.18-5-686: true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.18-5-686/postinst/old-system-map-link-2.6.18-5-686: true
linux-image-2.6.18-5-686/preinst/elilo-initrd-2.6.18-5-686: true
linux-image-2.6.18-5-686/postinst/bootloader-test-error-2.6.18-5-686:
linux-image-2.6.18-5-686/prerm/removing-running-kernel-2.6.18-5-686: true
linux-image-2.6.18-5-686/postinst/depmod-error-initrd-2.6.18-5-686: false
linux-image-2.6.18-5-686/postinst/depmod-error-2.6.18-5-686: false
* linux-image-2.6.18-5-686/preinst/already-running-this-2.6.18-5-686:
linux-image-2.6.18-5-686/preinst/bootloader-initrd-2.6.18-5-686: true
linux-image-2.6.18-5-686/postinst/old-dir-initrd-link-2.6.18-5-686: true
linux-image-2.6.18-5-686/postinst/old-initrd-link-2.6.18-5-686: true
linux-image-2.6.18-5-686/preinst/failed-to-move-modules-2.6.18-5-686:
linux-image-2.6.18-5-686/preinst/initrd-2.6.18-5-686:
linux-image-2.6.18-5-686/preinst/lilo-has-ramdisk:
linux-image-2.6.18-5-686/preinst/abort-install-2.6.18-5-686:
linux-image-2.6.18-5-686/postinst/kimage-is-a-directory:
linux-image-2.6.18-5-686/preinst/abort-overwrite-2.6.18-5-686:
linux-image-2.6.18-5-686/prerm/would-invalidate-boot-loader-2.6.18-5-686: true
linux-image-2.6.18-5-686/postinst/bootloader-error-2.6.18-5-686:
linux-image-2.6.18-5-686/preinst/lilo-initrd-2.6.18-5-686: true
linux-image-2.6.18-5-686/preinst/overwriting-modules-2.6.18-5-686: true
--- End Message ---
--- Begin Message ---
Reason: I tried the same installation procedure again
(with minor modifications), and now the
/boot/grub/menu.lst file is changed correctly:
my other linux partitions are still bootable.
I guess the reason is as follows: In the first attempt,
I edited the /boot/grub/menu.lst file before upgrading;
quite likely I removed some patterns that the upgrade
script looks for to modify the file correctly. Hence, the
upgrade was not able to extract the current information
and created a new /boot/grub/menu.lst file.
In the second attempt, I did not edit this file before
the upgrade and the upgrade worked correctly.
Hence, I guess it's my mistake.
Best regards,
Yaakov
--- End Message ---
Reply to: