Drive 0 assignment on my G522

Stevedg

Sorry in advance for the lengthy message ;-)

I use an esata connection to run my external HDD back up drive. (I installed a SATA to ESATA connector in an open slot & connected it to the #1 SATA port on the MB.) The esata connection and attached external HDD work fine.
If the external HDD is turned on prior to booting the PC, it gets assigned as drive 0 rather than the internal SSD. From what I have read, it may be normal behavior for UEFI to assign drive 0 to a SATA drive, rather than the internal SSD drive that actually contains the system and boot files.
I am hoping that you know of some UEFI setting that will force it to always assign drive 0 to the internal SSD.

MY REASON FOR THIS REQUEST IS THAT I WANT TO AVOID ANY POTENTIAL ISSUES THAT MAY OCCUR DURING RESTORE OF A BACKUP IMAGE USING A RECOVERY BOOT USB DRIVE (I use Shadow Protect SPX).

I tested the recovery thumb drive yesterday (without letting it actually do the restore).
When I boot from the recovery drive, since the recovery environment recognizes the BACKUP HDD as drive 0, it assigns this as the c: drive. It then assigns the destination drive (the internal SSD) as drive d: I am concerned that if I actually perform a restore, it will label the internal SSD as drive d:, which I of course want to avoid. I know that windows disk management has the ability to change the drive letter assignment (after the restore), however my gut tells me that there may be unanticipated problems with this. Therefore, I want to avoid the need for it altogether.

Your advise regarding UEFI settings or other suggestions would be greatly appreciated.
Thanks,
Steve G

PowerSpec_MikeW

@Stevedg

Nothing you can change here unfortunately. It's the port order that the UEFI BIOS detects the drives in. If it's there in a port with a higher priority it'll become 0. There shouldn't be in any issue with reassigning the drive letters in a PE environment prior to a restore. I'd need to know more about the backup software.