HDD to SSD Clone
Greetings,
I purchased True Acronis Home 2012 many months ago, and only just came around to using it. Instead of originally using it for OS backups (Kept putting off the great idea, heh), I've finally come to need it for Cloning my OS HDD to my new OCZ Agility SSD (120GB).
Software seems to work great, I used the Clone tool and Windows rebooted into a True Acronis interface (Pre-Windows Boot) to perform the clone, and I then proceeded to replace the HDD with the SSD to make the switch. The new SSD Clone works fine all the way till Windows is booting; the Windows Logo animation spirals in but BSOD's before it can "finished it's animation", and it occurs so fast I can't tell what the Error message is. I think I see about 4 long segments of Hex code after the traditional BSOD message at the top.
So, some things not quite right. Upon auto-reboot from the BSOD, I get the option to continue loading windows normally (BSOD's everytime), or perform the Windows Startup recovery thing. Choosing the latter option I only get one error come up after it's done it's checks, which is 0x490 under a sub-heading I can't recall at hand. Googling it has suggested MBR trouble, so I run Bootrec.exe /ScanOS via CMD and it finds Zero OS entries which is a bit disconcerting when it should see the SSD clone. I even then tried /FixMBR and /FixBoot, and neither made any difference at all.
But, and here's the real kicker, I have found a way to make the SSD boot perfectly: by leaving my old HDD connected.
My Boot Load order is *specifically* the SSD (Listed as C:\), and not my Seagate HDD (Listed as G:\). Even my Environment variables are utilising C:\ so everything seems to suggest the SSD is working, but ONLY if my old OS HDD is present (Also, I logged in as fast as I could on bootup and I can see a clear performance boost, so I'm very sure this is the SSD in operation right now).
For clarity, the Boot Load order is 1) SSD 2) CD ROM 3) Floppy - Two & Three aren't even present/connected.
So somehow my original HDD is supporting the SSD's boot success, how can I rectify this and completely remove my old HDD?
I'm not running AHCI(?) Drive mode if that counts for anything, it's in RAID Mode since I'm operating a separate RAID Stripe using the onboard RAID chipset. Also running a Software RAID Mirror, but I doubt the Windows level Disk Management stuff has any effect here.
Also, apparently this version, TI2011, automatically supports Partition Alignment, although I'm curious to check my SSD after this is fixed (or perhaps sooner rather then later) to be sure it's not at 63, instead 1024 (or whatever). (Update: It's 2048, it's fine.)
Last but not least, I have read about the forums making an entire Partition Backup and Restore is better then Cloning in some circumstances. Could this be my problem? Perhaps this is a solution... I've got this far though, I'd rather pause while I'm ahead. (Update: Doesn't work.)
Thanks for the support in advance! :)
Brief PC Spec: Win7 Pro 64bit (mostly up-to-date) / AMD Phenom II X6 1055T / ASUS M4N72-E Mobo / 8Gb OCZ DDR2 800Mhz / [SLI x 2] Asus GeForce GTX275 896MB / Asus Xonar DX 7.1 / Acronis True Image Home 2012 [Update v2.1 (Build 7133)]
Update: Switching my SSD to a native SATA power connection hasn't helped (Previously Molex Adapter). Using MBRWizard CLI, and performing a Fixed MBR (Win7 version obviously) to the SSD hasn't changed anything. MBRWizard also reports the 100MB System Reserve partition on the SSD is Boot enabled, and the regular partition containing the OS and all is disabled for boot, identical to my original HDD.
My mind is blown. What does my regular HDD have, that my cloned SSD doesn't? The question remains. I understand the turn-around for a response here isn't blazingly fast, that's fine, I'm just reporting what I've been doing to shed some light on potentials covered.
Update 2: Can't solve the problem. Backup & Restore method doesn't work either, still the exact same situation. I'm out of idea's, I welcome any assistance.
Thanks for the reply, I followed the instructions provided in the link exactly, and unfortunately the same problem persists; damn BSOD's at Windows boot.
I went the extra mile, convinced I can make this SSD work. I used my SLR Camera to record the BSOD, and took pics of various info screens from MBRWizard and BCDEdit.exe (Didn't use any commands, don't worry) and Bootrec.exe (Only used /OSScan).
One thing I find that doesn't add up, is the configuration of my OS HDD compared to the instructions provided for the other Forum member. The Hidden Partition on my OS HDD starts at 2048, thus the Backup of my OS HDD will presumably carry that over. The 1024 (1MB) in the instructions.... is too small for my Backup? My Backed-up MBR is twice the size of the space I'm leaving when configuring the SSD?
http://img801.imageshack.us/img801/6397/01disk0info.png - MBRWizard
Update: Never mind, I'm confusing Sectors with Megabytes/Kilobytes. There would in fact be ample space.
Perhaps worth noting, Bootrec.exe reports Zero Windows installations present, despite the recovery being apparently successful.
http://img832.imageshack.us/img832/6254/03bootrec.png - Bootrec.exe
http://img268.imageshack.us/img268/4433/02startuprepairresult.png - Windows Startup Repair Result (0x490 Error for System Files Integrity Check And Repair)
http://img194.imageshack.us/img194/9241/05bsod.png - The BSOD Error: 0x0000007a
Searching in relation to SSD's, generally Firmware updates are a recommendation, but I won't do anything yet since I already know it can load Windows successfully under some circumstances (i.e. The old OS HDD being present)
Also, the Backup I'm working from for the SSD was produced whilst Windows was booted.... I'm beginning to wonder if I should backup the OS HDD from the Acronis Startup Disc, and try again.
Beginning to get late here, so I will have to try whatever you might recommend next tomorrow.
Thanks for your continued support!
The Hidden Partition on my OS HDD starts at 2048, thus the Backup of my OS HDD will presumably carry that over. The 1024 (1MB) in the instructions.... is too small for my Backup?
The 1mb (1024) or the 2mb(2048) is referencing the "amount of free space" before the first partition. Either is acceptable as it is a correct divisible number.
Yes, it should carry over from the backup but you will need to confirm before you restore the first partition or after the procedure is finished.
James,
Something must have gone wrong as you applied the instructions.
That said, your BSOD points at some drive issue.
Just to make sure, here are some customized instructions for your case:
- Reboot your computer on your OLD disk, and make sure it is working normally, the new SSD being completely disconnected.
- Use Windows disk management to verify that the active partition is on the system disk (right click on the computer icon on your desktop, choose manage, storage, disk management)
- Print a screen shot of the disk management console for future reference
- Uninstall any program you don't want on the SSD (eg: games, ).
- Do a full backup of your current disk. Include all partitions, even the hidden ones (no need to use the sector by sector setting)
- Put your SSD at the same spot at your current disk. Remove your current disk from the computer for the time being.
- Boot your computer on the Acronis recovery CD
- Restore each partition at a time in the same order they were laid out (use your screen shot). This will allow to control resizing and offset to align the disk
- Leave a 1MB space before the System Reserved partition
- Mark the System Reserved primary,active
- Leave the drive letter change option alone
- Restore the C:\system partition
- No need to reboot inbetween partition restores
- After the last partition, restore the MBR+track0 and the disk signature
That's it.
Reboot on your new SSD. If Windows reboots with a BSOD, first it shows that it boots normally :-) The problem is that Windows doesn't like something about your new drive. Did you change the BIOS settings? Maybe from IDE to SATA or something? That would explain that...
Then, if you want to use your old disk, put it back in the computer, reboot. Delete whatever you want, etc.
You have some tweaks to optimize your SSD:
- disable automatic defragmentation of that disk
- optionally, disable indexing on the disk (not a big deal)
- disable the superfetch service, and prefetch
- leave the page file on the SSD
- verify that TRIM is activated http://www.ghacks.net/2010/09/14/verify-that-trim-is-enabled-in-windows…
When you restore, make sure the OLD disk is NOT in the computer and that the SSD is at the same spot as the OLD disk.
The fact that bootrec doesn't find any OS suggests the restores system reserved is not correctly marked active. You can correct this by using the "ACTIVE" command of DISKPART when System Reserved is the selected Partition (LIST DISK, SELECT DISK ..., LIST PARTITION, SELECT PARTITION 1).
The fact that the backup was produced in Windows is irrelevant.
Again, either your backup doesn't contain a partition that was on your system disk before, or you didn't restore all the partitions, or your active partition is not marked active.
Resolving this will resolve the fact that BootRec cannot find an OS. From there you should be able to fix the startup of your computer.
Writing from my tablet atm, forgive any typo's.
Had a battle with it this morning, still no joy. Made a fresh full backup of my perfectly functioning OS HDD, checked Disk Management for partition reference. Booted with Acronis Recovery, and copied the partitions onto the SSD in the sequential order, except for MBR plus Tack0 plus Disk Signature last. Same thing again. Only bios tampering is Boot order re-arrangement, SSD is running off same SATA port as HDD was.
Beginning to lose hope, I doubled checked the default settings for active partitions as well when recovering, they were correct. Guess I will look into SSD firmware updates later after work, because... I can't see where I'm going wrong.
How does bootrec.exe not see a Win7 installation when it obviously tries to boot it anyway, ridiculous. Will rage some more tonight when I look at it again.
Thanks for your continued support, Pat.
Since your computer boots, Windows starts loading, you restore succeeded. It looks like Windows fails to install the right driver for the disk and that creates the error.
What were your BIOS settings IDE or AHCI for the old disk setup? What are they now?
RAID mode is selected, AHCI and one other option is available, but since I've used RAID+0 via chipset for years, I never sought to change it (and presumably cannot without losing the stripe).
It's occured to me, that when the SSD did boot Windows fine (when the old OS HDD was present too), the disk signatures couldn't have been the same. That was earlier on when I used Cloned attempts though, so it's safe too assume the disk signature isn't copied when cloning.
But regsrdless of that, the SSD was capable of booting and functioning fine. Still makes me wonder what the HDD has that the SSD didn't. Does this rule out the Driver problem?
I do recall seeing back on those successful boots, that after Logging into my user account, the system tray would successfully identify the SSD and install correct drivers. It would then request a PC restart as one might expect.
So fudgin' confusing. I wonder if replicating that circumstance again, and letting it install that driver in windows, would allow a successful reboot without the old OS HDD.
Or is that wishful thinking... I could reload the MBR+Track0 AND Disk Signature afterwards...
Update: I'm getting close to attacking the SSD with a hammer. I appear to have a very unique, seemingly unsolvable problem. I can't even get a dodgey SSD boot now, the HDD loads despite not even being in the boot order.
At this rate, what should be a simple backup/restore, may end up being a fresh OS install. Reluctantly, it's seeming the only bet. I could firmware update the SSD, but OCZ say it has to be from an AHCI enabled Mobo, and Win Vista or later. Rules out my PC and Notebook, typical. They have a Linux boot thing available, guess I will download that and sit on my mechanical OS HDD for a while.
I don't want to waste more of your generous time on me Pat, but if you have anymore thoughts on this, I will try after work tommorow. The joy of working every weekend, it is mine :/
You typically do not want to have both disks in the computer at the same time. Windows can get really confused.
If booting on the SSD with the OLD HDD still there gets you to have Windows install the right driver for the SSD, you can repeat that. Then reboot without the old HDD. Hopefully you can repair the boot records if it doesn't boot, but at least we'd know that it is not a hard drive driver issue. You have to make sure that the OS that gets the driver is on the SSD.
You do not want to change the BIOS setting used for the OLD HDD.
What is the software RAID that you are running? For which disk is it?
Apologies for my "rage" last night, was getting pretty tired by 2am and was stressing myself out over such a silly thing.
"You typically do not want to have both disks in the computer at the same time. Windows can get really confused."
Considering it ignored Boot Load selection to reach the HDD when I attempted replication of the previous SSD circumstance I had, I can believe that, hehe.
"If booting on the SSD with the OLD HDD still there gets you to have Windows install the right driver for the SSD, you can repeat that."
I failed to replicate it, but may try again. I think I covered it before, but Environment variables, C:\ Drive Capacity and sheer performance increase pointed towards the Windows on the SSD was running - kinda nice to know that the SSD *does* work in a sense.
"You do not want to change the BIOS setting used for the OLD HDD."
Aye, save losing the Stripe.
"What is the software RAID that you are running? For which disk is it?"
They're twin 750GB Seagate's storing the equivalent of 'My Documents' basically. I can't stand losing data so I have the Mirror in place (And a RAID5 NAS, I'm so greedy) to hopefully prevent the worst from ever happening. It's built purely with Windows Disk Management, no 3rd Party Software at play.
Anyway, I will try to fool the computer into loading the SSD again, will clone the drive instead since that is what I believed led to it (All becoming a blur, heh). Getting frustrating though, I have 6 SATA ports on the Mobo, 4 are the Mirror & Stripe, so I'm juggling the SSD, OS HDD and Optical (For Acronis), plugging and unplugging them. I refuse to clone 60GB over USB2.0 to a Docking Station, christ.
I also read somewhere once, that SATA Data plugs were only designed to be reinserted 75 times. Or maybe that's some BS? lol, anyway, it's put me on edge constantly switching drives XD
I give up.
I'm not sure what I'm going to do, but spending any more then 5 days trying to make an SSD work is silly. Last night my DVDRW Drive even malfunctioned and persists on failing, I can only guess due to the excessive powering up/down I was having to do. For the most part I was unplugging from the mains and releasing the stored energy in the caps as well, christ.
If you have an ASUS M4N72-E Mobo, and an OCZ 'Agility 3' 120GB, then good luck. I would hope a fresh Install of Win7 works fine, I'm not prepared to do that right now (considering my Disc has gone walkies anyway, although handily I found small free Application on CNET Downloads that allowed me to view my Windows Product Key and store it). I'm also not sure of my SSD Firmware version (not noted on the SSD casing sticker) since I do not have access to an AHCI Enabled/WinXP or higher machine to run the OCZ Toolbox. The Linux distribution also needs AHCI enabled still, so I didn't even bother with that in the end.
I'm left suspecting either:
1) The SSD needs firmware updating, might try and get to a friends computer to test this.
2) It doesn't like RAID configured Controllers
3) It hates something about my Mobo chipset or SATA Controller Chip
4) Combination of 2 & 3
There is a 2012 BIOS update for my Mobo which I only just discovered now, but the patch notes do not appear to address any SSD issues. The patch notes could be watered down, but I won't keep my hopes up. Might email OCZ too, or post on their Forums, check if this has ever been an issue with there (apparently named) Sandforce based SSD's.
I guess one can only have so much luck with a long term custom computer build, before something comes along and fracks it up.
Thanks Pat for your services, been greatly appreciated, if I ever find a solution I'll post back.
Edit: Ugh, my original OS HDD now has an exposed System Reserved partition visible in My Computer, assigned with Drive F:\ - I didn't even modify/replace the HDD MBR+Track0 on this drive. JUST what I wanted.
Lucky me, Disk Management can just remove it's drive letter without any problems apparently...
James,
You have a lot of things going on and you should consider trying to do things separately to find out the point of failure, if any.
Let's try to do a clean install of Windows on the SSD alone in the system. But first, let's verify a couple of things.
Can you still boot your computer on your OLD HD? If yes, use Windows disk management. In the menu, choose view, top, list disks. Verify whether your OLD disk is MBR or GPT. Verify it is a basic disk also.
If it is GPT, do you use UEFI or legacy BIOS?
Regardless of the answer, do not change it in the BIOS for the time being.
Disconnect the computer from the network (to avoid having Windows check on updates and stuff).
Shutdown the computer, Remove *all* disk from the computer, put the SSD on the same connector as the old disk.
Boot on the Windows installation DVD. Use diskpart to clean your SSD and initialize it exactly as your OLD HDD. If you old HDD was MBR basic, initialize the SSD as MBR basic. If it was GPT basic, then make the SSD GPT basic. You got the idea.
Then, let's do a clean install of Windows 7 on the the SSD when it is the only disk in the system, without changing your BIOS Sata settings.
Once the computer boots normally on the SSD, add back the other disks (except your OLD system disk), until you have a functional system.
Then, boot the computer on the Acronis recovery CD and do a pristine backup of your SSD.
Then, restore on the SSD the image of your old HDD. If the computer doesn't boot any longer, restore your pristine backup of your SSD. If the computer doesn't boot, I am running out of ideas. If it reboots with the pristine image, but not with the old image, then there is a problem with that old image. You can try to do a new image of the old disk and try again. If that doesn't work, forget about the old image, restore your pristine image again and continue your clean install.
Can you still boot your computer on your OLD HD? If yes, use Windows disk management. In the menu, choose view, top, list disks. Verify whether your OLD disk is MBR or GPT. Verify it is a basic disk also.
Yes, it boots fine, I am currently operating from it without any issues. They are all listed as MBR, the OS HDD is Basic.
If it is GPT, do you use UEFI or legacy BIOS?
Every HDD is listed as MBR, so I guess the above doesn't apply?
The remainder of your instructions is somewhat similar to what OCZ suggested. I won't beat around the bush, I have posted on the OCZ Forums very recently, hoping to confirm or deny any known conflicts/firmware issues relating to this. Basically the answer is a No, but filling them in briefly on the matter, they have instructed me to perform a similar operation.
Disconnect all HDD's, switch to AHCI mode (I'm assured if I don't tamper with the RAID chipset in any manner, it will retain the Stripe build info) and utilise the OCZ proprietary software to blank it, and install Win7 from scratch. It seems to have reached a point where the least desirable option is required to be performed just to rule out certain possibilities, hehe.
I understand the merit of both suggestions, since they initially amount to the same thing anyway. I will use their software to prep the SSD, and perform the clean Windows install.
It probably doesn't feel very appreciative that I've now got them assisting me as well, in fact I feel kinda bad, it wasn't exactly what I intended. I was foolishly just trying to rule out incompatibility/firmware issues and I received directions as a result.
I will maintain open channels with both Forums, until any recipients choose to close communication :)
Thanks for your continued support Pat, I won't let ya down, I will get back to you when I get a new DVDRW Drive to burn this OS ISO. I have a legit key, and found official download links (can you believe it) for Win7 Pro 64bit Full Install, so I'm almost there. Hurray!
Normally, you don't have to change the BIOS from RAID to AHCI. If you have an intel controller, you should be able to swith the AHCI back to RAID, reboot the computer on the SSD (still alone on the computer). Windows should find the raid drivers and install them.
If you get a BSOD then it couldn't instal the drivers, and you will have to reinstall Windows all the way.
You should be able to update your firmware using a special boot disk that takes windows out of the question. Maybe this is what you do and you still have to AHCI enabled for the update. Follow the OCZ instructions there.