PDA

View Full Version : Cant boot from new ssd after having cloned from original ssd and then wiped original



fixxi.net
02-07-2016, 09:27 PM
G752VT UEFI - GPT , SSD disk 950 Pro samsung.

Can't boot Windows 10 (primary OS ) after it was cloned from original one, and then the original was ssd was wiped / deleted ( using disk part )
The disk was cloned via EaseUS, and the whole disk was cloned including the Recovery Partition and the OS.
I get the Win10 blue boot error : "The boot configuration data file is missing some required information ". Screehshot http://oi67.tinypic.com/16ia5js.jpg

bcdboot C:\Windows
================
This command succeeds ( ran via a secondary working OS that is available on another disk on the same system ) but does not solve the problem. Strangely via this secondary drive I can boot the Primary one but the Primary one cannot boot on its own,

Further more I cannot a create a Recovery Drive via the equivalent option in windows 10 ... it tells me "required files are missing".

A bootable USB boots and detects the primary OS but cannot repair it.. it says, " We cant repair it" or similar message. Going into a command prompt after booting the USB, will not see the disk ( because its an SSD , no drivers ) So I cannot try command prompt tools that people are suggesting.

JustinThyme
02-07-2016, 09:40 PM
What BIOS are you running and how do you have it set up?

Creating recovery media after the fact it a moot point. Im afraid you have bopped the beagle on that one. I've seen this same thing happened repeatedly over the years and this is specifically why I remove the original drive and put it away for safe keeping.

Im thinking your only chance now is a clean install, follow the UEFI guide in the sticky and whether or not you will need to load drivers is dependent on what BIOS you are running and how its configured.

You might want to see if this members post applies to your situation.
https://rog.asus.com/forum/showthread.php?79822-G752-with-Samsung-950-Pro-SSD-new-information&p=572265&viewfull=1#post572265

cdma2k
02-08-2016, 01:17 AM
no need to follow UEFI guide.
The current build of Windows 10 iso can detect the key automatically based on my experience, quick and simple, just create a bootable window 10 USB from MS site (https://www.microsoft.com/en-us/software-download/windows10), clean installation of Windows 10, then install the drivers if needed

fixxi.net
02-08-2016, 10:50 AM
I managed to solve it.


Here are my disks.

55454

The C: drive wasn't booting on its own even after I tried bcdboot c:\windows

Instead I had to do bcdboot c:\windows /s m: /f All

where m drive was assigned to the 260 MB EFI partition.

In other words the UEFI setup was expecting the boot manager to go to the EFI partition and will not accept it being in C: drive...

Maybe the EFI standard requires this, in disks where there is a dedicated EFI partition? Possibly,

Thanks for helping guys, all done now.

cdma2k
02-08-2016, 01:06 PM
good!
looks like your recovery partition is gone, did you make usb backup with Asus backtracker?

Gps3dx
02-08-2016, 01:15 PM
In other words the UEFI setup was expecting the boot manager to go to the EFI partition and will not accept it being in C: drive...
Maybe the EFI standard requires this, in disks where there is a dedicated EFI partition? Possibly

Hi there...
for that reason alone I've dedicated almost full-half-day to write the sticky thread "Guide: How to install windows 8/8.1/10 The proper way (UEFI based installation)" (https://rog.asus.com/forum/showthread.php?76993-Guide-How-to-install-windows-8-8-1-10-The-proper-way-(UEFI-based-installation)) - it holds some key ideas about windows based on UEFI machine - that are true also for the latest ROG models.
P.S - One of the most important laws of "creative thinking" is that "the solution is near you" - I can suggest to embrace it - after all, reading doesn't hurt,it might just help :)

JustinThyme
02-08-2016, 01:20 PM
I Know this sounds stupid but did you swap the position of the M2 Drives are you finished cloning?


no need to follow UEFI guide.
The current build of Windows 10 iso can detect the key automatically based on my experience

There is a lot more to UEFI than the product key. Takes you from 16 bit BIOS to 64bit firmware and the UEFI parition is used to execute the boot sequence by commanding the .efi files in the UEFI partition.

Gps3dx's guide is pretty comprehensive and thorough once you get past the blinding color coding.