Removing failed boot message True Image Created
I was attempting to clone my 256 drive to a 512 drive, which I setup from inside of the windows 7 app and required a restart. On restart I get a message saying the system failed to load (or something like that) and to hit any key to continue. The computer then continues to load up my OS like normal.
I've since see the forum link about the best practices for cloning a disc, but in the mean time how do I revert this failing custom boot option?
thanks for the help,
Nathaniel, welcome to these public User Forums.
The positive side of this issue is that your computer is still booting into your Windows OS as normal albeit it may also be still trying to boot into the Acronis rescue environment for the clone you attempted from within Windows 7.
I would suggest that perhaps the easiest way to resolve this issue would be to use a third party program such as EasyBCD to repair your boot / BCD files, which the program can do very quickly & easily.
Steve, thanks for the lightening fast response! I figured I wouldn't hear an reply before the day was out. I owe you one. I have one final question you might be able to answer for me. The one forum post suggested using disc back and recover as an alternative to cloning. As such I went ahead and made a back up of my C drive. I then
1. chose to recover the drive to my new 512 ssd. The recovery worked, however once booted it shows the C drive as roughly 256 gb and the remaining space as the E drive. I.e. It didn't expand the drive to the new space.
2. With option 1 not working I wiped the 512 and tried again, this time choosing to recover the disc via the partition option. This ended with the same result as option 1.
3. I'm now trying the same partition route as option 2, but this time I dug around the settings and saw some choices about what to do with the unallocated space. The system partition has the unallocated space set to auto, I then changed the main partition (I'm recovering) unallocated space settings "none". I'm hoping this means it will expand my partition into the remaining space of the drive. I guess I'll find out in 20 minutes. If this isn't right do you know how I can copy the backed up data to a larger drive? I've been using True Image since 2011 and I swear I've never had such issues moving my data to a larger drive before!
So I think I've been dealing with a different issue than I thought. Once the disc has been recovered and I boot to the new SSD it shows a C drive with 8 of 232 gb free and an F drive with 295 of 476 free. The crazy thing is they're both the same drive and if I double click on the F drive it shows all the same content at the C drive. Something's obviously gone horribly wrong. Sigh.
Nathaniel, ATI can / should do an automatic resize when doing either cloning or Backup & Recovery to a new larger drive but this seems to be a little hit & miss at times!
Personally, I go with the flow and use another free partition manager tool - MiniTool Partition Wizard and adjust / move partitions / sizes as best suits my needs.
If your new drive is working albeit with the extra duplicate partition, then you could delete the F: duplicate partition then expand the main C: OS partition to use the freed unallocated space. If not, start again as per your first recovery, then use PW to resize the OS partition. You may find that there is a Windows Recovery Partition after the C: that needs to be moved to the end of the new drive!
Sadly this is more strange than an extra partition. The drive is showing up twice. Disk 0 which it lists as a 256 drive , which was the size of my old disc (it even says it's using the samsung driver) and Disk 1 which is 512 in size. I definitely don't have a 256 drive in the machine. It's now sitting next to my keyboard. I'm so confused.
Nathaniel, I would suggest starting over again and wiping the new drive then recover your backup to it again when there is nothing else on the drive.
Steve. Thanks for all your suggestions. So I'm a total idiot. To verify that the data of the two discs were actually pointing the same block of data I created a file on the C drive expecting it then also appear on my E drive, but it didn't. WTF? I look back at my hard drive array and at the very bottom of my stack is a SSD still plugged in. Apparently I had an old SSD still plugged in (but not mounted) to my machine for the past few years (heh), which is what I removed instead of my C drive :) I feel like a total idiot, but at least the world makes sense again.