Solved

Cloned original smaller SSD to larger SSD with TodoBackup, now computer won't boot

Let me preface this by saying that my knowledge of computers is fairly limited, but I attempted to clone my original Crucial 64gb SSD to a larger Sandisk 256gb because I've run out of room on the tiny 64GB that came with my machine.

To begin with, this is a ZT machine from Costco, running Win 8.1. I cloned my original drive using TodoBackup, then swapped drives, and have been stuck ever since. When I originally attempted to boot, I got the following message:
"Recovery
Your PC needs to be repaired
A required device isn't connected or can't be accessed.
Error code: 0xc000000f
You'll need to use the recovery tools on your installation media. If you don't have any installation media (like a disc or USB device), contact your system administrator or PC manufacture."

So, I grabbed the recovery drive I made last night, plugged it into the USB port, and was able to get to the "Choose an option" screen, where I could troubleshoot or turn off the PC.

Selecting "troubleshoot" to refresh or reset my PC didn't work on either account. When attempting to refresh, it tells me "The drive where Windows is installed is locked. Unlock the drive and try again." When attempting to reset, it tells me "Unable to reset your PC. A required partition is missing."

I've searched this issue and tried several of the command prompt suggestions, although I'm not entirely sure what they're supposed to do. Either way, none of them have worked:
(Bootrec /fixMBR
bootrec /fixBoot
bootrec /rebuildBCD
for what it's worth).

At this point, I'm at a loss. I've gone into BIOS and repeatedly changed the boot order to see if maybe one time something would stick, but no joy. Does anyone have any suggestions as to how to get around this? I'm not sure what other information I need to include, but just let me know what else to include, and I'll do my best to find it.
6 answers Last reply Best Answer
More about cloned original smaller ssd larger ssd todobackup computer boot
  1. 1) Put the old drive in and see if it works. Let us know.
    2) When you wrote "clone," did you do a full disk clone, or just copy the partition? There is stuff outside of your C: drive that does need to be copied. My guess would be that you did that, but it doesn't hurt to ask.
  2. Thanks for the quick reply, Wyoming! I just plugged the old drive in, and it booted up like normal. In fact, I'm back on the desktop that it's installed in.

    When I cloned the drive, I did a full clone, which copied over 3 partitions IIRC (the OS, recovery, and then blank space).
  3. Best answer
    Without looking at it, it certainly smells to me as if the boot segment did not get written. There are two solutions to that (well, a hundred, but let's focus on two).

    One, if you have a full Win 8.1 disk (not the recover disk that came with the machine), you can try a Repair install. It should detect that there is no boot sector and fix that, as long as the new SSD is the only drive attached to the machine at the time.

    The alternative is to wipe the new drive (I strongly recommend a Secure Erase for reasons of TRIM) and clone again, going through the options and check boxes with someone here to make sure that the boot is copied along with the data that is in partitions.

    My personal approach is _always_ to do an image backup to an external disk and an image restore to the new disk. Just the way that I prefer it, for some reason. I think having a verified backup makes me feel warm and secure.
  4. WyomingKnott said:
    Without looking at it, it certainly smells to me as if the boot segment did not get written. There are two solutions to that (well, a hundred, but let's focus on two).

    One, if you have a full Win 8.1 disk (not the recover disk that came with the machine), you can try a Repair install. It should detect that there is no boot sector and fix that, as long as the new SSD is the only drive attached to the machine at the time.

    The alternative is to wipe the new drive (I strongly recommend a Secure Erase for reasons of TRIM) and clone again, going through the options and check boxes with someone here to make sure that the boot is copied along with the data that is in partitions.

    My personal approach is _always_ to do an image backup to an external disk and an image restore to the new disk. Just the way that I prefer it, for some reason. I think having a verified backup makes me feel warm and secure.


    Ok, awesome. :) I've never used any sort of cloning software before, so I really wasn't entirely sure what I was doing. I hit the 'clone' button, and assumed that everything that was on drive 1 would be copied over to drive 2, but it's definitely possible (and likely) that I missed something. Once I'm back home, I'll plug the new drive into the external and wipe it, and try again.

    Is there any software (preferably free, since I'll only be using it this one time) that you'd recommend to do the job without too many hiccups and without a lot of technical knowledge?
  5. My personal choice has switched to Easeus ToDo Backup. I stuck with Norton Ghost version 8 (DOS based!) until I switched over to SSDs and needed to worry about 4k alignment.
  6. I know this query is not terribly recent, but I have run into the same problem (at least nearly...mine will boot but does so with the following error: "boot manager failed to boot" though it will boot upon selecting "enter", I just have to do so after every cold boot). Additionally I have tried to reset via the "NOVO button" three times sequentially, but the effect is the same. I cloned the factory 128GB Samsung drive (in a Lenovo Yoga-11S i5-4210Y) to a new 1.0TB Samsung SSD via Todo Backup 6.X and chose to check the "sector-by-sector clone" as well as "optimize for SSD" radio boxes. I have done likewise (without checking optimize for SSD) with HDDs many times in the past and the clone worked as expected, but this one has me baffled. It should be noted that the original SSD was in the machine, running Win. 8.1, at the time of clone because I have only one mSATA->SATA adapter and SATA->USB cable (whereas I typically remove all drives and put them in 2.5in. hot-swap bays for cloning). I'm going to attempt to clone the drive again (which should take about an hour, more or less, as I'm going through USB-2.0), this time unchecking the sector-by-sector radio box and see what happens. Thank you in advance for any assistance that leads to the remediation of this problem.

    Tried to clone the drive again (after performing a full erase) and could not successfully clone at all, the drive dismounts, the clone fails to write to one of the sectors and the program terminates. Thinking it was the adapter (mSATA->SATA adapter) that failed I purchased a second (same brand, Syba, different model no.), which actually caught on fire when trying to clone, however the SSD still works in the first adapter (it will show up just fine, but when I try to clone it still dismounts and fails)...now I'm wondering if my SSD is bad while I wait for a third adapter (this one from Startech, a failed device is one thing, but one that catches aflame and has a component {small capacitor or perhaps a diode is my best guess because the board indicates the polarity} forcefully eject itself from the board is something entirely different). I'm really hoping that I can at least get to the point I was at with the previous clone...then perhaps I might be able to restore the boot files with a WinPE emergency disk.
Ask a new question

Read More

SSD Computers Locked Systems