Sign in with
Sign up | Sign in
Your question

HELP - Clonezilla Screwed up my Windows7 OS migration to SSD

Last response: in Windows 7
Share
April 29, 2013 2:10:07 PM

Inside my HP Pavilion Elite e9107c desktop PC, I have a 750GB Seagate HDD separated into 3 partitions that has been getting worse for a long time. My C drive partition is ~90GB of which about 50GB are being used by the OS. I kept a good portion of the data files on the much larger B drive partition. I got a Samsung 840 Series 120GB SSD to move the Windows7 OS to in hope of increased bootup performance and not having to worry about lossing everything in a HDD crash. After reading up on migrating Windows7 to a new SSD and some unhappy reviews of the Samsung migration software, I decided to follow this HTG (http://www.howtogeek.com/97242/how-to-migrate-windows-7...) migration guide. I followed it closely, including making a System Repair Disk and making a backup with a system image that I put on a virtual hard drive I created in the extra space of the B partition and on my HP Personal Media Drive that connects to my motherboard through USB_4.
From the directions it seemed that I should be able to use Clonezilla so I did as directed with the exception that I selected "Local Partition to Local Partition cloning" in Clonezilla instead of "Local Device to Local Device cloning" since I only wanted to migrate the C drive partition with the OS.
When Clonezilla completed (suspiciously fast), my PC was even slower than ususal. In Disk Management, it showed that the cloning had indeed taken place, with system files on the SSD, but the OS was still booting from the C drive on the HDD. It also showed that the SSD still lacked a drive letter. I then tried EaseUS Partition Master and the Samsung Migration tools but neither could access enough space or identify the SSD to complete the migration. I thought of reformating the SSD and starting from the beginning but failed at every attempt to clear it out because of the System files on it. I attempted to migrate the System files back to the C HDD via Clonezilla, but after that Windows has consistently failed to start. I have been trying to use the System Repair Disk to repair Windows but I can't find any of the backup images.
Help! What should I do?
April 29, 2013 2:36:35 PM

clonezilla only copies, it doesn't move. So if you remove the SSD, you should be able to boot to the other C drive like u did before. Then try running clonezilla again to a freshly erased and formatted SSD.
m
0
l
April 29, 2013 2:38:13 PM

if it won't boot to the old C drive, it's something you did, not clonezilla.

(I had to try a few times to get the clone to work right for me, but I did get my partition from my old SSD to my new one USING CLONEZILLA)
m
0
l
Related resources
April 29, 2013 2:47:27 PM

ittimjones said:
if it won't boot to the old C drive, it's something you did, not clonezilla.

(I had to try a few times to get the clone to work right for me, but I did get my partition from my old SSD to my new one USING CLONEZILLA)


I'm fairly certain it was when I tried to reverse the process (running Clonezilla with SSD as source & C drive HDD as destination) that I really screwed things up. Now I need help to just get Windows back running before I proceed with the migration issues.
m
0
l
April 29, 2013 2:51:31 PM

ittimjones said:
clonezilla only copies, it doesn't move. So if you remove the SSD, you should be able to boot to the other C drive like u did before. Then try running clonezilla again to a freshly erased and formatted SSD.


When Clonezilla completed, should the copied part on the SSD also have been labeled "C:"? I am wondering if the lack of a drive letter is what is hindering any of the other migration programs (EaseUS Partition Master and the Samsung Migration tools) from working. But how do I assign this copy the necessary drive letter "C:" when it is already assigned to the OS partition of the HDD?
m
0
l
!