On Tue, 5/5/2026 10:55 PM, Lawrence D?Oliveiro wrote:
On Tue, 5 May 2026 18:52:56 -0400, Paul wrote:
Summary: You can get there. It's the usual amount of annoyance.
Would be a lot simpler if you had done a file copy onto a new volume.
The ?amount of annoyance? is only ?usual? if you don?t know any better
...
You also do these things when you move a UEFI boot drive to
a Legacy machine. That's what it is about. The OP asked about
it, and I demonstrated it can be fixed.
The actual backup and restore was trivial. I tested that.
The UEFI NVMe image booted just fine on the UEFI 1TB HDD.
Both were tested on the same computer, and they both worked.
They just were not plugged in at the same time (I unplugged
the NVMe module, before attempting to boot up the 1TB
prepared HDD).
It is when you move a UEFI-prepared storage device to a
Legacy machine (Optiplex 780 E8400), you have to fix up GRUB for that.
When I first plugged it in, I got a flashing underline, implying
nothing bootable was being found. On another situation (my VM setup),
that situation shows "No boot materials found" when there is that
sort of mismatch. While Boot Repair fixes some things, there
are bound to be the odd combination that has rough edges. And
I've used the "side by side" install methods multiple
times, and also on more than one platform. I was using that,
as a means to get UEFI certificates injected for Windows
(something that now comes with manual commands so you
don't have to do that any more).
Paul
--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)