Problem with Win 7 startup after backup recovery to new SSD!

teamplus · 08 Apr 2016

I used Acronis True Image to backup the partitions made of my c: to my backup external drive. I have since restored that backup to my new OCZ Trion 150-240 GB SSD. I then booted from another Win 7 drive on the same machine and had the new SSD as a secondary drive when the recovery was made.

Following recovery my diskmgmt.msc view shows the 2 partitions created on drive 0 as partition 1, drive 1: "System Reserved" and partition 2, drive 2: "Windows 7". It also does not list information shown on other healthy partitions of windows which create 2 partitions with only 1 drive letter... partition 1, drive 1- "System Reserved" (system,active,primary partition) and partition 2, drive 2 - "Windows 7" (boot , page file, crash dump, primary partition).

After recovery:

disk 0
partition 1 "System Reserved"
drive 1
Healthy(Active, Primary Partition)

disk 0
partition 2 "Windows 7"
drive 2
Healthy (Primary Partition)

I am trying to narrow down if the problem has to do with then work toward a fix.

1) A problem with the recovery method used or setup of the SSD (installed new ssd when installed as a secondary drive)
2) The backed up drive data data itself used for the recovery
3) A problem with the boot file structure.

Thanks!

teamplus · 08 Apr 2016

In this picture I have the new SSD as a secondary disk, being disk 1- only so I could use diskmgmt.msc.

ignatzatsonic · 08 Apr 2016

Your boot files are on System Reserved on disk 0. You know that because that partition is marked as "system" in your picture.

Offhand, I don't see any purpose to the System Reserved partition on disk 1. That's E in your picture.

Normally, you only want 1 partition to be marked active. You have 2.

Normally, you only want 1 System Reserved partition. You have 2.

I'd disconnect disk 1 and confirm that the PC will in fact boot from disc 0 alone.

If it will, I'd delete System Reserved on disk 1 and add that space to partition F---or just ignore that very small space.

I assume partition F is for your personal data and that you want to keep personal data on a different hard drive than C is on. Nothing wrong at all with that idea.

If you instead want disk 1 to be your boot drive, you could do that if:

1: you copy the boot files from System Reserved on disk 0 to System Reserved on disk 1. An application such as Easy BCD can do that quickly. You'd need to leave System Reserved on disk 1 as an "active" partition, as it is now and remove the "active" flag from System Reserved on disk 0. You can do that from Disk Management.

2: Partition F has a valid Windows installation. It would become C if you copy the boot files to System Reserved on disk 1.

You'd need to then confirm that the PC will in fact boot with disk 0 disconnected. If it will, what is now F on disc 1 would become C and you could then wipe disk 0 or do whatever you want with it.

teamplus · 09 Apr 2016

I have not explained my image layout above correctly. The image above reflects the current situation where I have hooked up another windows drive (disk 0), to the computer, only to test and to access diskmgmt.msc which I found to be nonaccessible from the recovery disk boot. The disk 1 above is the drive in question. This is the one I have attempted the recovery to and is the new ssd that fails to boot when installed in disk 0 position.

It appears to lack proper boot and system files required by windows and further appears to have a problem from the way the recovery assigned a drive letter to each of the two required partitions.

I hope that clarifies the issue better.

AddRAM · 10 Apr 2016

Please remove the letter from the SR partition on Disk 1

Disconnect drive 0, get it out of the system.

Run startup repair until the 223 GB drive boots on it`s own.

Don`t worry about it`s drive letter, it will be C when you get it booting

It`s only F in your picture because you are not booted into it.

teamplus · 11 Apr 2016

Will do and post results

Thanks