Sign in with
Sign up | Sign in
Your question
Solved

master ide dont boot after taking out slave

Last response: in Storage
Share
January 17, 2014 3:19:23 AM

Hallo, ohk I got 2 old ide hdds, installed windows 8.1 on tthe biggest one and finnaly got smaller one installed as slave, now I removed slave since im selling it but now windows wont boot, both was on cable select with main windows hdd on black and slaave on gray, my main hdd shows in bios and is set to boot first but since I took out my slave wich I formated in windows, windows wont boot. I change jumper to master vhanged cables changed all ide options in bios, still no boot... help
January 17, 2014 3:37:36 AM

Is your main HardDrive an IDE or S-ATA drive?

Try going into the BIOS and find your hard drive settings.. I can't remember what it's called but it'll probably be on the lines of 'Hard drive boot mode' (again i can't remember the actual name.

But it'll either have SATA, or IDE as it's settings. Change it from one to the other, might solve your problem.
m
0
l
January 17, 2014 3:58:36 AM

Tried al this options in bios, I have a biostar g41d3+ mobo intel core 2 duo e8600 cpu, 4gig ddr3 ram al my parts are two weeks old except harddrive and hardrive booted fine just now that I took the slave out it wont boot it shows in bios but wont boot.
m
0
l
Related resources
January 17, 2014 4:07:07 AM

Hdd specs, 160 gig, lba mode supported, block mod 16 sectors, pio mode 4, async dma multiword dma 2, smart support. Also enabled and disabled al these but put them back on auto.
m
0
l
January 17, 2014 4:13:07 AM

"Windows 7 stores it's boot files on a utility partition at the front of the drive. What seems to have happened is that when you installed a second copy on the Samsung SSD the installer retained the boot files on the Intel SSD. That is, the boot files for both installations were on the Intel SSD." Altho I have windows 8.1 is this possibly what happen to me, althoui doubt itsince I installed window on main drive and only later added slave so I doubt it, if so how can I fix it?
m
0
l

Best solution

a b G Storage
January 17, 2014 5:03:38 AM

This is what happens when install or upgrade a windows installation to a new drive, while the old drive with the previous install is still hooked up. Windows (for the exact reason I dont know) will use the boot manager from thr previous install on the old drive. You do the install, then if you removethr old drive, you remove the boot manager too. The only way to fix it is to do a repair install.
Share
a c 379 G Storage
January 17, 2014 5:13:46 AM

jitpublisher said:
This is what happens when install or upgrade a windows installation to a new drive, while the old drive with the previous install is still hooked up. Windows (for the exact reason I dont know) will use the boot manager from thr previous install on the old drive. You do the install, then if you removethr old drive, you remove the boot manager too. The only way to fix it is to do a repair install.


This is why I always recommend that only one drive is attached when installing a windows OS, then connect the remaining drives after the OS is installed. This forces windows to put all files onto a single drive and creates less headaches in the future.

m
0
l
!