Windows 10: PC Starts but will not boot into Windows

The USB thing was to make its data recoverable. I should have stated that. Glad to hear that it's unnecessary, because it's already backed up.

I'm getting out of my depth here. When the "bad" drive is mounted in the USB enclosure, what does Disk Management say about the drive?

 

Hi

"When the "bad" drive is mounted in the USB enclosure, what does Disk Management say about the drive?"

It sees it as a GoFlex (the name of the enclosure) healty etc and all the data is accessible.

cheers

Daniel

 

Hi,

Keep only that drive connected, check in BIOS what SATA port it is connected to and when not 0, open the case and hook it up to that.
Back in BIOS make that the first boot device.

If all that works fine you can then connect the second drive to SATA port 1 and how that goes.

Cheers, *Wink

 

Hi

how can I tell which port is 0 or 1 etc, is it just trial and error?

regards

Daniel

 

Hi,

It is usually marked on the MB's pcb or it is shown in your pc's manual.
Often the ports are arranged in numerical order so if you don't have any of the above info then trial and error is the only way out.

Cheers, *Wink

 

Hi

thanks, I worked it out, the OS drive is on Sata 0 and the PC boots fine when
that is the only drive, when I attach the 2nd drive it is on Sata 1 and the startup
dialogue find both drives but the PC does not boot, it hangs on the Press DEL for Bios Setup,
but will not go to Bios Setup.

Both drives have passed Seatools tests, the 2nd drive was in a USB enclosure
for the test.

So at least we have confirmed that we are on 0 and 1.

Regards

Daniel

 

Hi

no flags in Device Manager, but the drive is not attached to the MB.

I believe that if there is a power issue the PC would turn off.

I am reluctant to test on another PC, that is out family main PC and I do not
want any problems with that one.

cheers

Daniel

 

Start computer and Press Del to Boot into Setup (Bios) go to Integrated Peripherals, or Advanced tab. Look for SATA controllers. If you only have one drive attached (ie) plugged into SATA port 1 on the motherboard, and you get the message Can't find any device, then using your arrow and Enter keys, Disable any SATA controller that are not being used. If you are trying to use the Secondary drive, make sure the SATA controller/port that the drives data cable is plugged into is Enabled in the Bios, Save and Exit, then boot back to the Bios to see that the HDD is listed there in the Main window.

 

Hi,

So, when the second drive is inside the machine and hooked up to SATA port 1, the machine hangs. Correct.
With that same drive in its USB enclosure it does work or... ?

This is quite odd I must say.

Cheers, *Wink

 

Hi

yes it works in that it passes seatools and all the data is accessible, however I have to hot plug it,
if I try to boot with the drive in the enclosure it does not boot up, it hangs in the same place.

Regards

Daniel

 

Hi

the OS drive that allows a boot up is on Port 0, I swapped the cables to the proper port, the "bad" drive
attaches to Port 1, but does not allow boot up.

I cannot find any mention of Sata controllers in the BIOS, the only mention of Sata properties is
to allow Hot Plug of the individual ports.

This machine is a dumbed down BIOS version (ASUS words) for people who would send it out for repairs,
I asked for the code to get into the full BIOS but was told there was none.
regards

Daniel

 

Hi,

So, regardless of whether its in the enclosure or inside the PC it does not work.
It's a wild guess but it could be a cold joint somewhere on the SATA to pcb board interface.
Would you happen to have access to another machine to test the drive in ?
A friend or family member, whatever ?

Cheers, *Wink

 

Sounds like the drive has a problem with its partition table that the bios does not like and causes the bios to hang.

 

Hi

can this be repaired, format or reset partition table?

cheers

Daniel

 

Hi

Possibly so.
Why not put that back in the enclosure, boot the machine without it attached and plug it in after the user is logged in.

After that we can run some tools on it and hopefully put this to bed.

Cheers, *Wink