From: David Wright <deb...@lionunicorn.co.uk>
Date: Sun, 27 Oct 2024 09:56:45 -0500
> That earlier installation is presumably the bookworm that
> wrote (hd0,gpt2)/boot/grub/grub.cfg with the Grub deb12u1,
> which I pointed out in my first post, but wasn't confirmed
> by your follow-up.
Yes, the multiple details have confused me.
> I don't know anything about nativedisk or the distinctions between
> various types of driver.
The only documantation I've found is here.
https://www.gnu.org/software/grub/manual/grub/grub.html#nativedisk
"firmware disk drivers" means drivers in the machine BIOS?
"native ones" means drivers in Grub?
"native disk drives" appears to be a typo. I read it as "native disk drivers".
Grub2 documentation needs work.
> OTO you could just let os-prober run when you build Grub and let it
> do the job for you. Is there any reason why you don't want to run
> os-prober? Sorry, I'm repeating myself.
A search of "os-prober security" finds several pages. os-prober is
disabled by default in Archlinux and other respected distributions.
For interest, I enabled os-prober again in /etc/default/grub and ran
grub-install /dev/sda. lsblk reports the USB connected /dev/sdc6
where Void is installed. Nevertheless the only stanza in
/boot/grub/grub.cfg for Void is from my entry in
/etc/grub.d/40_custom. Os-prober tried and failed.
A bug in os-prober? A problem with the HDD? A problem with the
SATA-USB2 adapter? A bug in grub2?
An interesting observation is that the USB-connected Void system boots
with no snags when selected directly in the BIOS. To me, that
suggests a problem in grub2 or os-prober.
Rather than spend more time investigating, will put the HDD in the
target machine and work there. Remove some of the complications.
Regards, ... P.
--
VoIP: +1 604 670 0140
work: https://en.wikibooks.org/wiki/User:PeterEasthope
