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 #333058,
regarding Debian sarge install, grub fatal error with sata drive...
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.)
--
333058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=333058
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: Debian Sarge
Procedure: Install on system with sata drive.
Issue: install has fatal error upon grub install.
Searches on the web have brought various related incidents, however
there is no true resolution for this issue. I have done the following:
Installed Debian in expert mode at least ten times with the same exact
failure each time with attempting different approaches.
I have entered the partition in each of the grub format (hd2,1) /dev/sda
etc... Each time the install of grub gets to 50% and then brings up a
fatal error window.
Alt f4 and Alt f3 each show little tidbits of info, yet none of it has
helped to resolve this issue.
Alt f3 says that grub/stage1 can not be read
Alt f4 says that grub-install (with each of the attempted partition
notation formats from above) failed
I have additional ide drives on the system in primary master and
secondary master positions. I have shutdown the system and unplugged the
ide cables to make this system only have the sata and still had this issue.
I have tried finishing without configuring grub and couldn't get back in
with the grub parameters that were recommended. kernel (hd2,0) /vmlinuz
root=/dev/sda4
I have tried (hd2,1), /dev/sda /dev/sda1 (hd0,1) and eve let the system
place grub in the mbr which also failed! I have also tried using
partition types of ext2 ext3 and even jfs for the /boot partition. None
of these changes have helped
I have attempted to force this to go and have had no resolve.
I have read of others removing the ide drives from the picture. I have
also read of one guy who reinstalled with being careful of his syntax
and found that if he entered the syntax correctly the first time it
would fly, yet one typo and changes could not be made after that without
an entire fresh install attempt.
This is most certainly a bug as most every other install I have ever
done has placed Grub most simply.
I have installed Sarge on one other system with a sata drive, so this is
not just about sata drives. Both of these systems are running on Elite
Group Motherboards, although different models. I assume that this could
be related to translation of the bios?
Please help?
Thanks in advance and sorry for this being an issue that has been
reported before. The difference is that there is not a solid result to
be tried in dealing with this issue. I will try any test or answer any
questions to aid in fixing this issue.
Jon
--- 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 ---
