New
#120
What's John suggest?
What's John suggest?
I tried to image mine with AOMEI and it didn't work. I finally did what I didn't want to do... I did a clean install, and now that it's done, I'm glad I did. I owe a lot to whs for all the great advice, tutorials, and most of all, his patience. Now I can delete the AOMEI programs for good.
Thanks again
I recovered the Windows 7 system partition from my spinner to an SSD using Acronis, and although it booted/worked I was surprised to see that the alignment wasn't right. The starting offset was 32,256 bytes so Acronis must not have recognized that the Kingston HyperX drive was an SSD maybe. But after reading thru this thread, and downloading MiniTool Partition Wizard Home Edition 8.1.1 (freeware) I was able to re-align the loaded partition to 1,048,576 bytes. Took some 10-15 minutes total so I assume the process involved reading-and-rewriting all the data.
After doing this however, the SSD no longer booted the computer. "Missing boot blocks" or loader or something. But upon restarting with a W7 Repair Disc inserted to my DVD drive, the repair of the boot loader took just a second and the SSD now boots again just fine.
I've since tweaked this with EasyBCD to be able to boot the SSD or the older spinner, or Acronis, and it's all good.
Thanks whs for the thread, and to Britton30--may he R.I.P. --for mentioning MiniTool. Looks to be a wonderful free addition to the toolbox.
:)
Yes Max Britton and I were great friends and we both discovered this great program while looking for an alternative to Ease US - I use it a lot for all manner of jobs and if you look there is an addition to the partitioning and surface testing stuff in the data recovery part of the start up GUI - really good stuff.
Has anyone seen a '0' offset number when checking alignment using Diskpart?
I realize any '0' number divided by four will return a zero which would say that its aligned but I question whether the SSD is truly aligned.
I also noticed on the msinfo32 page the starting offset showing the same. Also, there were 512 bytes/sector and 63 sectors/track which might indicate it not be running efficiently.
Makes be wonder if the SSD is aligned correctly. Any thoughts out there?
Thanks. I could have sworn it was aligned six months ago when I installed the new SSD.
I was planning on doing a clean install this weekend anyway.
Cheers.
I wanted to create a dual boot XP/W7 on an old Acer laptop. I replaced the hard drive in my laptop with a new 250 GB SSD, then loaded a Windows XP image from a backup that came with my laptop, taking it back to stock. I updated some of the drivers, but nothing specifically for the SSD. Windows XP was running perfectly, and all updates were installed thanks to LifeHacker and his POS registry hack for Windows Update. Then I used PerfectDisk and Diskpart to lower the partition size down to 33 GB (because Windows XP puts a set of files in the middle of whatever disk you install on...thus I had to use diskpart to shrink the size of the partition, then PerfectDisk to move the files again, then diskpart to shrink again, etc). The problem is that I didn't understand at the time why PerfectDisk was warning me not to use the "Prepare for Shrink" mode instead of the recommended "SSD" mode. Anyway, now I can load Windows 7, but I cannot get Windows Update to work. I have tried several reinstalls of W7 and worked with the Microsoft techs to solve the problem, but nothing works. Then I came across this thread and started to wonder if I screwed things up early on. So in diskpart, my list partition now looks like "Partition 1 - Primary - 33GB - 31KB offset" and "Partition 2 - Primary - 199GB - 33GB offset". Are my offsets totally screwed up? Can I fix it? And is it possible that that my W7 offset is screwing up Windows Update, or is it most likely a separate issue?