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 #167616,
regarding SCSI and IDE BIOS device numbers
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.)
--
167616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=167616
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub
Version: 0.92+cvs20020923-1
Hi
Grub sometimes gets weird BIOS drive numbers.
On one system, there are: the disks hda, hdc and sda. The BIOS settings
are: boot from SCSI then from IDE. The SCSI adapter is:
00:0a.0 SCSI storage controller: Adaptec AHA-2940/2940W / AIC-7871
which lists the SCSI drive as 0x80 and boots from it. Grub gets the
system up and running, but if guesses wrong the BIOS numbers if called
from within a running Linux system:
GRUB version 0.93 (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the
possible
completions of a device/filename. ]
grub> root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
grub> root (hd1,0)
Filesystem type is ext2fs, partition type 0xfd
grub> root (hd2,0)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd2)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd2)"... 16 sectors are
embedded.
succeeded
Running "install /boot/grub/stage1 (hd2) (hd2)1+16 p
(hd2,0)/boot/grub/stage2 /boot/grub/menu.lst"... succeeded
Done.
grub>
suedwind:/boot/grub# fdisk -l /dev/hda
Disk /dev/hda: 16 heads, 63 sectors, 39813 cylinders
Units = cylinders of 1008 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 39813 20065720+ fd Linux raid autodetect
suedwind:/boot/grub# fdisk -l /dev/hdc
Disk /dev/hdc: 16 heads, 63 sectors, 39813 cylinders
Units = cylinders of 1008 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 1 39813 20065720+ fd Linux raid autodetect
suedwind:/boot/grub# fdisk -l /dev/sda
Disk /dev/sda: 255 heads, 63 sectors, 1116 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 3 24066 83 Linux
/dev/sda2 4 34 249007+ 82 Linux swap
/dev/sda3 35 50 128520 83 Linux
/dev/sda4 51 1116 8562645 5 Extended
/dev/sda5 51 174 995998+ 83 Linux
/dev/sda6 175 547 2996091 83 Linux
/dev/sda7 548 796 2000061 83 Linux
/dev/sda8 797 1116 2570368+ 83 Linux
suedwind:/boot/grub#
as you see, sda should be (hd0), hda (hd1) and hdc (hd2). Grub names
them the other way around: hda=hd0, hdc=hd1, sda=hd2 which is wrong.
The Mainboard is an ASUS P5A-B AMD K6-III board which never ever showed
any irregularities, not even with lilo.
Cheers
Mark
--- 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 ---
