On 26/11/2021 04.50, James Knott wrote:
On 2021-11-25 9:39 p.m., Carlos E. R. wrote:
That's the one. On BIOS it lists disks, but on UEFI it lists "bootable oses", not partitions, that have entries in the EFI partition(s).
No, even when I set for UEFI only, I still only see drives
Weird.
I don't know when UEFI machines started, but 10 years ago it would be a primitive form, if any.
There was an update in 2013.
Well, you have to add Windows there. Look at the entries in your old disk EFI partition.
The old disk was legacy, not UEFI.
Ah! I forgot that. Sure, you need to install Windows using UEFI. Or ask in a Windows forum how to migrate a Windows install from traditional booting to UEFI booting, whether that is possible. It might.
I guess I'll have to forget about UEFI on this computer. :-(
I don't know. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 2021-11-26 3:04 a.m., Carlos E. R. wrote:
Sure, you need to install Windows using UEFI. Or ask in a Windows forum how to migrate a Windows install from traditional booting to UEFI booting, whether that is possible. It might.
I've decided to go back to legacy and am copying over the old disk right now. tnx anyway.
On 2021-11-26 9:33 a.m., James Knott wrote:
On 2021-11-26 3:04 a.m., Carlos E. R. wrote:
Sure, you need to install Windows using UEFI. Or ask in a Windows forum how to migrate a Windows install from traditional booting to UEFI booting, whether that is possible. It might.
I've decided to go back to legacy and am copying over the old disk right now.
tnx anyway.
I have gone back to the original config and copied the partitions to the new drive. However, a new problem has appeared. Since the drives were identified by device ID, it wouldn't boot until I changed fstab to use the uew IDs. Now, it chokes during boot up with a message "A start job is running for /dev/disk/by-ide...", which lists the original partition. However, I can boot with recovery mode. Where is this old device-id coming from? The partition it's choking on is the swap partition. I tried recreating it, but it still chokes. tnx jk
James Knott composed on 2021-11-28 10:44 (UTC-0500):
I have gone back to the original config and copied the partitions to the new drive. However, a new problem has appeared. Since the drives were identified by device ID, it wouldn't boot until I changed fstab to use the uew IDs. Now, it chokes during boot up with a message "A start job is running for /dev/disk/by-ide...", which lists the original partition. However, I can boot with recovery mode. Where is this old device-id coming from? The partition it's choking on is the swap partition. I tried recreating it, but it still chokes.
Is the one it's choking on the same UUID as in Grub's resume= line? To find out, try changing it to noresume at the Grub menu using the E key. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2021-11-28 1:32 p.m., Felix Miata wrote:
Is the one it's choking on the same UUID as in Grub's resume= line? To find out, try changing it to noresume at the Grub menu using the E key.
That's it. How do I make it stick? Next boot it does the same thing again.
Never mind. Found it in Boot Loader configuration. On 2021-11-28 1:38 p.m., James Knott wrote:
On 2021-11-28 1:32 p.m., Felix Miata wrote:
Is the one it's choking on the same UUID as in Grub's resume= line? To find out, try changing it to noresume at the Grub menu using the E key.
That's it. How do I make it stick? Next boot it does the same thing again.
participants (3)
-
Carlos E. R. -
Felix Miata -
James Knott