Recently I bought a 950 Pro M.2 SSD. I cloned the OS over from my OCZ Vertex 4, everything worked fine, until I restarted the PC. Now, every time I turn the PC on, it throws me the "no boot device" message. I turn it off and on again, and it works fine. This happens every time. Anybody have any idea how to fix this?
PC Specs can be seen on my profile.
Thanks!
Have you checked into the bios/uefi to see on what position in the boot order your M.2 is?
I have, I even disabled every boot device that isn't the 950.
Could the cloning process have missed the Master Boot Record?
Possible, I used the Samsung data migration utility. Wouldn't this cause it to flat out not work at all, though?
That I don't know, since I've never actually cloned anything before. Though I have had issues with where the MBR goes missing and the BIOS can't boot directly, but a utility could get you back into the OS just fine.
If it is the case, it should be easy to restore the MBR provided you have your operating system disc or usb image. What version of windows do you run?
If that had happened the system would not boot at all but he states it does at least sometimes:
I wonder what happens if you warm(re)start the PC (a.k.a. the reset button) I have the feeling either the motherboard or the SSD itselve has trouble initializing after a coldstart.
1 Like
Hmm, good point. In fact, I do have issues with my MSI laptop with my mSATA drive, like that. Where cold starts result in no boot drive being found, but a simple ALT CTRL DEL to reboot the system will load the OS just fine.
Deffinitely a initialisation problem. If the bios/uefi has the option you can try and disable "fasboot" or "skip memory test" which will expand the time in the bios and if its the SSD whos not yet ready under normal "fast" init conditions it should thank for the extra time.
If there is no such option to extend initialisation time, just do the coldboot, enter bios/uefi wait a bit and than exit without saving changes... that also should give enough time for the SSD to start.
If these "tests" not work, its likely the systemboard that has problems, which brings me to - also checking for a bios/uefi update could be worthwhile - as the vendor probably heard of the problem already - and SSDs could have a firmware upgrade available as well.
1 Like
I'm using windows 10 Pro.
I haven't yet. I'm going to try that when I get home.