SSD "No operating system found"?

AustnW

Honorable
Jun 25, 2013
128
0
10,690
So I just migrated my HDD to my SSD, but now when I try booting to the SSD I get the above error? I have a Seagate Barracuda HDD, Samsung 840 250GB SSD, and Windows 8 Pro 64-bit. Any suggestions?
 
Solution
I don't know how, or if, a GPT system differs from an MBR system in respect of the booting procedure, but a traditional BIOS and MBR system loads sector 0 of the boot device into RAM and then transfers control to it. This boot code then identifies the boot partition and loads its boot sector into RAM. The first part of sector 0 contains the initial boot code, while the end of the sector contains the partition table. Your sector 0 has no boot code, only a standard "EE" GPT partition. This means that your SSD has been set up as a data drive, not a boot drive.

The following articles appear to address your problem:

http://www.tweakhound.com/2012/11/13/how-to-fix-the-windows-bootloader/
http://support.microsoft.com/kb/927392
I also get a "Non-system disk" error and a "mbr error 1, Press any key to boot from floppy" error.

I used Samsung's Data Migration software to migrate the disk, so I'm not sure what went wrong, it said that it finished successfully.
 


But it should have worked the way I did it. I'm wondering why it hasn't.



Umm, I'm confused. I downloaded it and put it in hexadecimal, but I'm guessing you have to know how to read it ? If so, that doesn't help.
 


Just go into bios and change your boot drive order as it is still searching for your old boot drive. Set cd rom first and Samsung second.
 
Launch DMDE.

Select the desired Physical Device.

Uncheck the "Show Partitions" box and click OK.

You should see sector 0 in hexadecimal mode.

Go to Tools -> Copy Sectors

Click Device in the Source tab. First Sector should be 0. Change Number of Sectors to 1. The Last Sector should adjust itself automatically.

Choose File in the Destination tab. DMDE will select a filename of "sec_0_1.ima". Click OK.

The file should be 512 bytes in size. Could you please upload it?
 


I'm sorry, how do you change the number of sectors to 1? I can't see an option anywhere after clicking on "device" under the source tab.
 


That did not work. It just booted to my HDD.
 


Okay, it's automatic saving name is "lba_0_1.bin" so it saved as that. How do I upload it?
 
Upload it to a file sharing service, or paste it here in text form.

In the latter case you could view the file with a hex editor (eg HxD freeware).

http://mh-nexus.de/en/hxd/

Edit -> Select All
Edit -> Copy As -> Editor View

Then paste it into your next post (Ctrl-V).
 


Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001B0 00 00 00 00 00 00 00 00 2F FF 6D 48 E2 24 00 00 ......../ÿmHâ$..
000001C0 02 00 EE FF FF FF 01 00 00 00 FF FF FF FF 00 00 ..îÿÿÿ....ÿÿÿÿ..
000001D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA ..............Uª

Is what I get. Does that help?
 
I don't know how, or if, a GPT system differs from an MBR system in respect of the booting procedure, but a traditional BIOS and MBR system loads sector 0 of the boot device into RAM and then transfers control to it. This boot code then identifies the boot partition and loads its boot sector into RAM. The first part of sector 0 contains the initial boot code, while the end of the sector contains the partition table. Your sector 0 has no boot code, only a standard "EE" GPT partition. This means that your SSD has been set up as a data drive, not a boot drive.

The following articles appear to address your problem:

http://www.tweakhound.com/2012/11/13/how-to-fix-the-windows-bootloader/
http://support.microsoft.com/kb/927392
 
Solution
Sorry about going dark on this for awhile, but I (sorry to say) took the easy route and re-installed Windows. It worked fine after that. It might have been a corrupt install because there were a few other problems occurring as well. Thanks for the help though guys.