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 #434543, regarding grub can't boot because it mixes up devices 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.) -- 434543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434543 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: grub Version: 0.97-27 Severity: normal I have a new install of etch on hdc2. Grub calls that (hd1,1): hooloovoo:~# grub-install --recheck /dev/hda Probing devices to guess BIOS drives. This may take a long time. Searching for GRUB installation directory ... found: /boot/grub Installation finished. No error reported. This is the contents of the device map /boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script `grub-install'. (fd0) /dev/fd0 (hd0) /dev/hda (hd1) /dev/hdc in /boot/grub/menu.lst, the partitions to boot from are mentioned as (hd1,x): hooloovoo:~# cat /boot/grub/menu.lst | grep hd # root (hd0,0) # root (hd0,1) # kernel /vmlinuz root=/dev/hda2 ro ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=/dev/hdc2 ro ## e.g. groot=(hd0,0) # groot=(hd1,1) ## e.g. defoptions=vga=791 resume=/dev/hda5 root (hd1,1) kernel /boot/vmlinuz-2.6.18-4-486 root=/dev/hdc2 ro root (hd1,1) kernel /boot/vmlinuz-2.6.18-4-486 root=/dev/hdc2 ro single # on /dev/hdc1 root (hd1,0) map (hd0) (hd1) map (hd1) (hd0) # on /dev/hdc7 root (hd1,6) map (hd0) (hd1) map (hd1) (hd0) Despite this, grub fails to boot because it doesn't find the partition to boot from. If I hand-edit (hd1,1) to (hd0,1) before booting from the grub menu, it does boot. This means that grub is calling hdc (hd1,x) sometimes and (hd0,x) other times. Any idea what might be causing this? -- 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-4-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages grub depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libncurses5 5.5-5 Shared libraries for terminal hand grub recommends no packages. -- no debconf information
--- 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 ---
