Your message dated Sat, 16 Aug 2025 15:55:37 -0400 (EDT)
with message-id <[email protected]>
and subject line Bug#1110934: Removed package(s) from unstable
has caused the Debian Bug report #439903,
regarding update kernel in encrypted root on lvm -> wrong menu.lst
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.)


-- 
439903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439903
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub
Version: 0.97-27

I don't know if its the kernel installation scripts fault or some grub scripts, 
so please forgive me if I'm wrong with my suggestion to blame grub.

After the last update/upgrade to a new kernel the system didn't want to boot 
because after the upgrade the menu.lst wasn't updated the right way.
the old entry was:
---
title           Debian GNU/Linux, kernel 2.6.18-4-686
root            (hd0,0)
kernel          /vmlinuz-2.6.18-4-686 root=/dev/mapper/c533-root ro
initrd          /initrd.img-2.6.18-4-686
---
the new one was updated to:
---
title           Debian GNU/Linux, kernel 2.6.18-5-686
root            (hd1,0)
kernel          /vmlinuz-2.6.18-5-686 root=/dev/mapper/c533-root ro
initrd          /initrd.img-2.6.18-5-686
---

after changing the root device to (hd0,0) everything works now.

I've installed debian 4.0 onto a scsi harddisk /dev/sda and used the debian 
installer to automatically make and format all partitions with encryption.
this results in:
/dev/sda1 to be a 250MB ext3 boot partition (/boot)
/dev/sda2 to be a ~8GB extended partition
/dev/sda5 to be a ~8GB encrypted luks lvm partition (dm-0) holding root (dm-1) 
and swap (dm-2)

additionally there is an unused ide drive (2GB, /dev/hda) with two partitions 
(swap (hda1) and some old debian installation in one partition (hda2))
The bios is configured to boot the SCSI harddisk. After boot up /dev/hda is 
suspended via hdparm (-Y).

I don't know why it's updated to the wrong root device but I think it's because 
the SCSI hdd is detected as second HDD now where it was detected correctly as 
the first one while installation...

#cat /boot/grub/device.map
(hd0)   /dev/hda
(hd1)   /dev/sda

no hardware changes since installation...

best regards
Michael Heide


--- End Message ---
--- Begin Message ---
Apologies; this wasn't sent as part of the dak rm action. I'm doing 
this by hand. Since this was manual, this opens the chance for me taking 
action by mistake.

I got the list of bugs via UDD, and am closing via -close on BCC. I spot 
checked about 10 of the bugs, and they're all src:grub. The COUNT 
matches the tracker page, so I'm sending this. 

If I have closed a bug that's not about bin:grub or src:grub, please do 
re-open the bug.

   paultag


We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

      grub |    0.97-84 | source
grub-legacy |    0.97-84 | amd64, i386

------------------- Reason -------------------
ROM; dead upstream, replaced by grub2
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected].

The full log for this bug can be viewed at https://bugs.debian.org/1110934

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Paul Tagliamonte (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to