Strange win 10 boot runaway to another drive

Ideasmiths

Arch-Supremacy Member
Joined
May 9, 2001
Messages
22,653
Reaction score
4,912
Been DIY for decades and 1st time encounter this weird behaviour. I have a Samsung 970Evo plus 1TB recently bought, fresh installed win10 on a gigabyte Z370N wifi itx motherboard. The previous boot device a 970EVO plus 500GB was moved to another slot and reformatted. Both are GPT

So for 3 weeks plus everything boot normally till yesterday suddenly this happened.

EkdbmwU.png


so I tried to take out the 500GB NVme and win10 complain no boot device. Bios set to boot from 1TB

Take out 1TB cannot boot as 500GB is an empty device.

Put both back normal place, bios shows "window boot manager 500GB" and the 1TB option.

Somehow the boot sector osmosis from the 1TB to the 500GB by itself......
 

Koenig168

Arch-Supremacy Member
Joined
Nov 4, 2007
Messages
10,079
Reaction score
1,770
reformatting does not remove the boot loader partition. You need to re-partition the whole SSD to do so.
 

jtjt00

Arch-Supremacy Member
Joined
Jan 1, 2000
Messages
17,700
Reaction score
526
When you installed OS on Samsung 970Evo plus 1TB and the previous SSD still connected, the setup procedure search and update the old boot partition instead of creating new one on your new SSD. As a result, you need the old SSD to boot your rig.

Should disconnect all drives before doing OS setup.
 

Cocoon33

Junior Member
Joined
Mar 16, 2018
Messages
23
Reaction score
0
Detach the old 500 GBs, then reinstall Os on the new1TBs as boot drive. Attach the old one & reformat as a normal drive.
 

gld998

High Supremacy Member
Joined
Feb 21, 2008
Messages
38,447
Reaction score
2,345
Been DIY for decades and 1st time encounter this weird behaviour. I have a Samsung 970Evo plus 1TB recently bought, fresh installed win10 on a gigabyte Z370N wifi itx motherboard. The previous boot device a 970EVO plus 500GB was moved to another slot and reformatted. Both are GPT

So for 3 weeks plus everything boot normally till yesterday suddenly this happened.

EkdbmwU.png


so I tried to take out the 500GB NVme and win10 complain no boot device. Bios set to boot from 1TB

Take out 1TB cannot boot as 500GB is an empty device.

Put both back normal place, bios shows "window boot manager 500GB" and the 1TB option.

Somehow the boot sector osmosis from the 1TB to the 500GB by itself......

Happen to me on Windows 7 setup. Yes u need to disconnect all old drives/500Gb before installation.

Need to reinstall OS and reformat. pls disconnect all the other drives.
 

Ideasmiths

Arch-Supremacy Member
Joined
May 9, 2001
Messages
22,653
Reaction score
4,912
Happen to me on Windows 7 setup. Yes u need to disconnect all old drives/500Gb before installation.

Need to reinstall OS and reformat. pls disconnect all the other drives.

Thats the strange thing, I disconnected all, only inserted the 1TB and did clean install...later inserted the 500GB and copied all the old files over then reformat clean.....

I googled and having extra drives cause this issue....but that's why my case so weird...
 

Cocoon33

Junior Member
Joined
Mar 16, 2018
Messages
23
Reaction score
0
Thats the strange thing, I disconnected all, only inserted the 1TB and did clean install...later inserted the 500GB and copied all the old files over then reformat clean.....

I googled and having extra drives cause this issue....but that's why my case so weird...
Enter the bios to check the new 1 TB is the first boot drive, the old one is secondary.
 

Ideasmiths

Arch-Supremacy Member
Joined
May 9, 2001
Messages
22,653
Reaction score
4,912
anything to do with bios??

Enter the bios to check the new 1 TB is the first boot drive, the old one is secondary.

After the fresh installed 3 weeks ago, my bios all along I set Boot Manager - 1TB, then 2nd is 1TB .

Then suddenly as mentioned, failed to boot, so when I go into bios see Boot Manager - 500GB show up (no Boot Manager - 1TB), it's as though the boot magically osmosis over without my intervention (i'm on Win 10 November version).

If I try bios set to 1TB (ie disable window boot manger), it does no boot.

Summary: The strange case here is window boot sectors migrated without my action. From a complete good SSD to a formatted 500GB
 

Phen8210

High Supremacy Member
Joined
Jul 29, 2011
Messages
29,028
Reaction score
8,286
Here is the problem, you installed the OS on C but the EFI is in D.
The EFI contains the instruction to boot from the drive.

I never heard of this issue where the EFI and OS partition automatically shift to another drive upon connecting them.

Are both SATA drives?? Try swapping the SATA ports so that your Boot drive is read as Disk 0 instead of 1. Probably got to do with motherboard.


Also, try migrating them back
https://www.easyuefi.com/faq/en-US/Move-EFI-System-Partition.html
 
Last edited:

cscs3

Arch-Supremacy Member
Joined
Jun 4, 2000
Messages
21,732
Reaction score
133
anything to do with bios??

There is dont need to disc drive. You need the bios to setup which is the first disk then the 2nd. As you have a 99M boot partion there at first drive, hardware will look for this partition first snd boot base on you boot configuration during windows installation.

Also, it seem you do not have a active partition. Suggest 1st you setup which id the first disk via bios, then consider to setup without the 99M boot partition (also call boot manager).
 

m0n0n0ke

Arch-Supremacy Member
Joined
Mar 30, 2003
Messages
24,284
Reaction score
3,372
OT. ..ts bought your 970 evo plus from? Any good deals going on?
 
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts. Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
Top