From `dmesg`:

md: kicking non-fresh <device> from array!

This is using MD-RAID1.  Appears GRUB is opting to load grub.cfg, kernel
and initial ramdisk off of this device, rather than the still operational
mirror.  The result is without manual intervention an older kernel
potentially gets loaded and causes problems.

I must argue this qualifies as "critical" since an older kernel might
have security holes or other problems.  For now I'll leave this as
"important" since I'm unsure how many are effected by this.

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 1110934@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
ftpmaster@ftp-master.debian.org.

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

reopen 1069264
assign 1069264 src:grub2
quit

Most/all relatively recent bugs attached to "grub" are likely applicable
to "grub2".  In this case the bug almost certainly applies to all
versions of GRUB, though it has only been confirmed on a recent one.

I also suspect #1069264 deserves elevated severity, though I'm unsure how
high.

found 1069264 2.06-13+deb12u1
quit

Upon some further checking, it appears bugs #710901 and #1069264 are
duplicates.  These do point to an interesting issue though.

The existance of these is indicating there is no place for GRUB
runtime-common bugs.  #710901 was attached to grub-pc, yet the bug isn't
limited to grub-pc (also effects OF and EFI).

I'll let the maintainers do the merge action as I'm unsure of how this
should be correctly handled.