- Joined
- Mar 28, 2024
- Messages
- 7
- Motherboard
- Asus ProArt Z490-Creator 10G
- CPU
- i9 > Need full CPU model name > See Forum Rules!
- Graphics
- RX 580
I have successfully created a Sonoma bootable drive. I can boot it successfully through a USB port without any issues (meaning without any installer; I have successfully copied the EFI to the actual new Sonoma bootable drive).
When I connect the drive through my internal data port the drive would not successfully boot. I can see the drive on my boot picker and select it but it does not boot after going into a loop.
Here are the other things:
My previous bootable drive loading Big Sure loads without a problem from the internal sata drive.
The previous Big Sure drive is automatically selected on the boot picker and that previous Big Sur bootable drive boots without any problems. I conclude from that that the EFI partition on the Big Sur boot drive is correctly configured, why would it otherwise boot without a problem. (I have disconnected any other media that may have any EFI partition.)
When I try to boot the Sonoma drive from the internal Sata data port (at such internal SATA port where I connected the previous OC Big Sure bootable drive), I get icons on my boot picker different form when I boot that drive from a USB port.
This leads me to believe that when I connect my Sonoma bootable drive to the internal data port, the BIOS is loading a different EFI configuration than the one on the Sonoma bootable drive, somehow perhaps looking for my previous Big Sur EFI that may have been stored on the sytems's NVRAM (since any other media storing an EFI partition has been disconnedted).
I have disconnected any drive that has an EFI partition when I try to connect my Sonoma bootable drive from the internal SATA port. So the only EFI visible to the system is the one in my successful (from a USB connection point of view) Sonoma bootable drive.
Is it possible that my NVRAM is storing my previously loaded EFI partition trying loading that EFI instead of the EFI on the Sonoma bootable drive connected? Can you please help me shed some light on what is going on here? Do I need to flush the NVRAM (in which case I cannot return to go back to my previous Big Sur bootable drive if this Sonoma bootable drive cannot be connected to the internal Sata port)?
I spent a lot of time on this issue. I would be grateful if anyone could proved help. Thanks!
When I connect the drive through my internal data port the drive would not successfully boot. I can see the drive on my boot picker and select it but it does not boot after going into a loop.
Here are the other things:
My previous bootable drive loading Big Sure loads without a problem from the internal sata drive.
The previous Big Sure drive is automatically selected on the boot picker and that previous Big Sur bootable drive boots without any problems. I conclude from that that the EFI partition on the Big Sur boot drive is correctly configured, why would it otherwise boot without a problem. (I have disconnected any other media that may have any EFI partition.)
When I try to boot the Sonoma drive from the internal Sata data port (at such internal SATA port where I connected the previous OC Big Sure bootable drive), I get icons on my boot picker different form when I boot that drive from a USB port.
This leads me to believe that when I connect my Sonoma bootable drive to the internal data port, the BIOS is loading a different EFI configuration than the one on the Sonoma bootable drive, somehow perhaps looking for my previous Big Sur EFI that may have been stored on the sytems's NVRAM (since any other media storing an EFI partition has been disconnedted).
I have disconnected any drive that has an EFI partition when I try to connect my Sonoma bootable drive from the internal SATA port. So the only EFI visible to the system is the one in my successful (from a USB connection point of view) Sonoma bootable drive.
Is it possible that my NVRAM is storing my previously loaded EFI partition trying loading that EFI instead of the EFI on the Sonoma bootable drive connected? Can you please help me shed some light on what is going on here? Do I need to flush the NVRAM (in which case I cannot return to go back to my previous Big Sur bootable drive if this Sonoma bootable drive cannot be connected to the internal Sata port)?
I spent a lot of time on this issue. I would be grateful if anyone could proved help. Thanks!