Jump to content

"Reboot and Select proper Boot device..."

Go to solution Solved by ohitsluca,

Raid is a different storage structure than what your original drive was using, ACHI, most likely.

 

Because it is a different storage structure, windows is unable to find the boot drive because it does not have the raid drivers.

 

When you change to Raid, you will need to reinstall windows and install the raid drivers during the install to be able to boot into windows.

 

if you switch back to achi, you should be able to boot into windows.

 

I never change from AHCI to Raid. I planned to, but didn't ever get that far lol.

But, I did figure it out. It was a 1TB internal hard drive I was going to be replacing with the SSD's. I had never plugged it in, and Windows must have needed that drive as well in order to boot. 

For reference: Original setup was a 128gb SSD as my boot drive, 1TB internal as data. New setup was 128gb SSD as boot, 2x256GB SSD's (to be used as data). Plugging in the original 1TB internal allowed me to boot. Thanks all.

So I bought a Corsair 750D and 2x Samsung 840 EVO's today, changed all my existing hardware (including my boot drive, a 128gb Samsung 830 SSD) over to the new case and installed the 2 new SSD's. Upon booting I received the error message in the title. I checked all of my BIOS settings and sata power/data cables and everything seems fine. I unplugged the 2 new SSD's and tried again, and I still get the same error message. I'm not really sure what the problem could be. Any ideas?

Link to comment
https://linustechtips.com/topic/114993-reboot-and-select-proper-boot-device/
Share on other sites

Link to post
Share on other sites

And you installed windows on the new drives right? lol

                                                                                                                                                                | 5820k+EK supremacy nickel+acetal white 4.5Ghz | X99 Deluxe | Enthoo Luxe | 2x gtx780+komod NV full cover block | Corsair AX1200i | WD blue 500gb |

                                                                                                                                                                                 Kingston V300 120gb | Samsung 840 Evo 500gb| Bitspower D5 vario+Res combo | primochill advanced LRT tubing (Solid White) |

                                                                                                                                                       | Alphacool Nexxos MONSTA dual 120mm Black Ice nemesis GTX360 triple 120mm | Noctua NF-F12 X4 | Bitspower true silver 1/2ID 3/4 OD compressions (various angles) |

Link to post
Share on other sites

is the drive with windows selected as the primary boot drive?

Spoiler

Corsair 400C- Intel i7 6700- Gigabyte Gaming 6- GTX 1080 Founders Ed. - Intel 530 120GB + 2xWD 1TB + Adata 610 256GB- 16GB 2400MHz G.Skill- Evga G2 650 PSU- Corsair H110- ASUS PB278Q- Dell u2412m- Logitech G710+ - Logitech g700 - Sennheiser PC350 SE/598se


Is it just me or is Grammar slowly becoming extinct on LTT? 

 

Link to post
Share on other sites

what operating system?

 

Did you previous have a hard drive attached to your original setup?

 

Are you running raid?

 

here is what I understand of your original and new setup, is this correct?

 

original

1x samsung 830 (boot)

 

New

1x samsung 830 (boot)

2x samsung 840 evo (data?) (raid 0?)

 

So I bought a Corsair 750D and 2x Samsung 840 EVO's today, changed all my existing hardware (including my boot drive, a 128gb Samsung 830 SSD) over to the new case and installed the 2 new SSD's. Upon booting I received the error message in the title. I checked all of my BIOS settings and sata power/data cables and everything seems fine. I unplugged the 2 new SSD's and tried again, and I still get the same error message. I'm not really sure what the problem could be. Any ideas?

Use the quote or multiquote, for faster responses \/ \/

Link to post
Share on other sites

And you installed windows on the new drives right? lol

 

I haven't done anything with the new drives other than plug them in (and then unplugged lol)

 

is the drive with windows selected as the primary boot drive?

 

Yes. 

 

what operating system?

 

Did you previous have a hard drive attached to your original setup?

 

Are you running raid?

 

here is what I understand of your original and new setup, is this correct?

 

original

1x samsung 830 (boot)

 

New

1x samsung 830 (boot)

2x samsung 840 evo (data?) (raid 0?)

Yeah that's exactly right. I hadn't even set up the new drives as RAID 0, though that was my intention. All I did was plug them in and when I got the error upon booting, I removed them thinking they were the problem. I did have a 1TB internal data drive previously, could that be the issue? 

Link to post
Share on other sites

Raid is a different storage structure than what your original drive was using, ACHI, most likely.

 

Because it is a different storage structure, windows is unable to find the boot drive because it does not have the raid drivers.

 

When you change to Raid, you will need to reinstall windows and install the raid drivers during the install to be able to boot into windows.

 

if you switch back to achi, you should be able to boot into windows.

 
I haven't done anything with the new drives other than plug them in (and then unplugged lol)

 

 

Yes. 
 

Yeah that's exactly right. I hadn't even set up the new drives as RAID 0, though that was my intention. All I did was plug them in and when I got the error upon booting, I removed them thinking they were the problem. I did have a 1TB internal data drive previously, could that be the issue? 

Use the quote or multiquote, for faster responses \/ \/

Link to post
Share on other sites

All I know when ever I have done stuff with my boot drive or reset the cmos and I get that message it's because my os drive isn't selected as the primary boot. 

Spoiler

Corsair 400C- Intel i7 6700- Gigabyte Gaming 6- GTX 1080 Founders Ed. - Intel 530 120GB + 2xWD 1TB + Adata 610 256GB- 16GB 2400MHz G.Skill- Evga G2 650 PSU- Corsair H110- ASUS PB278Q- Dell u2412m- Logitech G710+ - Logitech g700 - Sennheiser PC350 SE/598se


Is it just me or is Grammar slowly becoming extinct on LTT? 

 

Link to post
Share on other sites

 I haven't done anything with the new drives other than plug them in (and then unplugged lol)

....so you don't have an OS on them?

                                                                                                                                                                | 5820k+EK supremacy nickel+acetal white 4.5Ghz | X99 Deluxe | Enthoo Luxe | 2x gtx780+komod NV full cover block | Corsair AX1200i | WD blue 500gb |

                                                                                                                                                                                 Kingston V300 120gb | Samsung 840 Evo 500gb| Bitspower D5 vario+Res combo | primochill advanced LRT tubing (Solid White) |

                                                                                                                                                       | Alphacool Nexxos MONSTA dual 120mm Black Ice nemesis GTX360 triple 120mm | Noctua NF-F12 X4 | Bitspower true silver 1/2ID 3/4 OD compressions (various angles) |

Link to post
Share on other sites

 

I haven't done anything with the new drives other than plug them in (and then unplugged lol)

 

 

Yes. 

 

Yeah that's exactly right. I hadn't even set up the new drives as RAID 0, though that was my intention. All I did was plug them in and when I got the error upon booting, I removed them thinking they were the problem. I did have a 1TB internal data drive previously, could that be the issue? 

Its because they don't have an OS on it thats why it gets stuck at this error because it has nothing to boot from. You would need to install the OS to get rid of this error. :)

Hello and Welcome to LTT Forum!


If you are a new member, please read the rules located in "Forum News and Info". Thanks!  :)


Linus Tech Tips Forum Code of Conduct           FAQ           Privacy Policy & Legal Disclaimer

Link to post
Share on other sites

Raid is a different storage structure than what your original drive was using, ACHI, most likely.

 

Because it is a different storage structure, windows is unable to find the boot drive because it does not have the raid drivers.

 

When you change to Raid, you will need to reinstall windows and install the raid drivers during the install to be able to boot into windows.

 

if you switch back to achi, you should be able to boot into windows.

 

I never change from AHCI to Raid. I planned to, but didn't ever get that far lol.

But, I did figure it out. It was a 1TB internal hard drive I was going to be replacing with the SSD's. I had never plugged it in, and Windows must have needed that drive as well in order to boot. 

For reference: Original setup was a 128gb SSD as my boot drive, 1TB internal as data. New setup was 128gb SSD as boot, 2x256GB SSD's (to be used as data). Plugging in the original 1TB internal allowed me to boot. Thanks all.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×