Your message dated Sat, 16 Aug 2025 15:55:37 -0400 (EDT)
with message-id <20250816195432.ga3783...@dc.cant.vote>
and subject line Bug#1110934: Removed package(s) from unstable
has caused the Debian Bug report #282127,
regarding grub-install fails with "mismatched or corrupt version of
stage1/stage2"
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 ow...@bugs.debian.org
immediately.)
--
282127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub
Version: 0.95+cvs20040624-10
SYSTEM DETAILS:
laxmi:/boot# fdisk -l
Disk /dev/hda: 4310 MB, 4310433792 bytes
255 heads, 63 sectors/track, 524 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 6 48163+ 83 Linux
/dev/hda2 7 37 249007+ 82 Linux swap / Solaris
/dev/hda3 * 38 524 3911827+ 83 Linux
laxmi:/boot# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/hda3 / xfs defaults 0 1
/dev/hda2 none swap sw 0 0
proc /proc proc defaults 0 0
/dev/fd0 /floppy auto user,noauto 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0
/dev/hda1 /boot ext3 defaults 0 2
laxmi:/boot# uname -a
Linux laxmi 2.6.6 #1 Mon Jun 28 18:01:43 EST 2004 i686 GNU/Linux
PROBLEM DESCRIPTION:
--------------------
grub-install fails while trying to convert this system over from lilo.
the exact same problem has occured on 2 other systems that i have tried to
install grub on in the last few days.
laxmi:/boot# grub-install --no-floppy --recheck --grub-shell='/sbin/grub
--read-only' /dev/hda
Probing devices to guess BIOS drives. This may take a long time.
Due to a bug in xfs_freeze, the following command might produce a segmentation
fault when /boot/grub is not in an XFS filesystem. This error is harmless and
can be ignored.
xfs_freeze: specified file ["/boot/grub"] is not on an XFS filesystem
GNU GRUB version 0.95 (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 0x83
grub> setup --stage2=/boot/grub/stage2 --prefix=/grub (hd0)
Checking if "/grub/stage1" exists... yes
Checking if "/grub/stage2" exists... yes
Checking if "/grub/e2fs_stage1_5" exists... yes
Running "embed /grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
Running "install --stage2=/boot/grub/stage2 /grub/stage1 (hd0) (hd0)1+16 p
(hd0,0)/grub/stage2 /grub/menu.lst"... failed
Error 6: Mismatched or corrupt version of stage1/stage2
grub> quit
BTW, specificying "--root-directory=/boot" doesn't help....gets it even more
wrong, in fact (notice what it does with "stage2=/boot/boot/...").
laxmi:/boot# grub-install --no-floppy --recheck --root-directory=/boot
--grub-shell='/sbin/grub --read-only' /dev/hda
Probing devices to guess BIOS drives. This may take a long time.
Due to a bug in xfs_freeze, the following command might produce a segmentation
fault when /boot/boot/grub is not in an XFS filesystem. This error is harmless
and
can be ignored.
xfs_freeze: specified file ["/boot/boot/grub"] is not on an XFS filesystem
GNU GRUB version 0.95 (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 0x83
grub> setup --stage2=/boot/boot/grub/stage2 --prefix=/boot/grub (hd0)
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 (hd0)"... 16 sectors are embedded.
succeeded
Running "install --stage2=/boot/boot/grub/stage2 /boot/grub/stage1 (hd0)
(hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/grub/menu.lst"... failed
Error 6: Mismatched or corrupt version of stage1/stage2
grub> quit
--
craig sanders <c...@taz.net.au> (part time cyborg)
--- 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 1110...@bugs.debian.org.
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
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Paul Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
