Quote:
Originally Posted by syg00
Probably because the firmware determined which EFI partition it will reference. Bad assumption on your part I would suggest.
I've never seen the sense in having more than one on a machine.
|
I create a snapshot of Windows on a monthly basis so that if I get a virus or MS releases some broken update (like 1809) that wipes out drivers, I can always instantly get back in the game by booting off the clone drive. It's near instant and there is no recovery or trying to fix it. It's not cheap as I have a SSD that's on standby and only used for the purpose of snapshots as often or as rarely as needed.
Over the years I found out it's the best compromise. Data is expensive and so is days of downtime.
Now I added Linux to this equation but it's there is no snapshot. I might back up critical data.
My UEFI machine will not let me add any Linux drive to its BCD configuration, MS locked it up. So during the boot cycle I have to hit F11, get the list of bootable devices and select Ubuntu. It's either that or I can go into BIOS, make the Ubuntu drive the Boot choice #1 and then configure Grub to chain the other Windows disks.
My point is, any distro should not access a drive other than where it has been told to install explicitly and put Ubuntu in another drive's EFI partition. It only did it to the clone disk since I had the foresight to remove the primary Windows 10, otherwise I would have ended up performing this procedure there as well:
https://linuxbsdos.com/2015/09/05/ho...in-windows-10/
run diskpart select Windows disk, select the EFI part and then manually delete the Ubuntu directory that should not be there.
Really not a big deal but took me a while to find it. If both disks EFI partitions are affected, the machine won't boot anymore until I remove one of them.
Took me a while to diagnose this.