Check source for file system errors Check destination for file system errors Set drive active (for booting OS) DON'T SELECT Disable SmartSector copying DON'T SELECT Ignore bad sectors during copy Copy MBR Destination partition type : Primary Drive letter : None
For Win7
Check source for file system errors Check destination for file system errors Resize drive to fill unallocated space (ONLY if you want to) DON'T SELECT Disable SmartSector copying DON'T SELECT Ignore bad sectors during copy Destination partition type : Primary Drive letter : None
For Copy Drive if a SRP is not present
Check source for file system errors Check destination for file system errors Resize drive to fill unallocated space (ONLY if you want to) Set drive active (for booting OS) DON'T SELECT Disable SmartSector copying DON'T SELECT Ignore bad sectors during copy Copy MBR Destination partition type : Primary Drive letter : None
Restore to a new HD if a SRP is present
For the SRP
Verify recovery point before restore Partition type : Primary Check for file system errors after recovery Set drive active (for booting OS) Restore original disk signature Restore master boot record
For Win7
Verify recovery point before restore Resize drive after recover (unallocated space only) (ONLY if you want to) Partition type : Primary Check for file system errors after recovery
Restore to a new HD if a SRP is not present
Verify recovery point before restore Resize drive after recover (unallocated space only) (ONLY if you want to) Partition type : Primary Check for file system errors after recovery Set drive active (for booting OS) Restore original disk signature Restore master boot record
Restore to the same HD if a SRP is present
For the SRP
No need to restore
For Win7
Verify recovery point before restore Partition type : Primary Check for file system errors after recovery
Restore to the same HD if a SRP is not present
Verify recovery point before restore Partition type : Primary Check for file system errors after recovery Set drive active (for booting OS)
We are having trouble applying a Windows 7 image to different hard drives that don't have SRPs. Here is what we're doing:
FOR THE SRP
Verify recovery point before restore Partition type : Primary Check for file system errors after recovery Set drive active (for booting OS) Restore original disk signature Restore master boot record
FOR WIN7 PARTITION Verify recovery point before restore Partition type : Primary Check for file system errors after recovery Restore original disk signature Restore master boot record
After the restore, we get all the way to the "Starting Windows" screen and it just sits there forever. What are we doing wrong? Should we not even be restoring the SRP? I noticed in your instructions for "Restore to a new HD if a SRP is NOT present" that you haven't broken it apart for the SRP and Win7 separately.
Any help would be greatly appreciated - these recoveries are driving us crazy!!!
I'm a bit confused. Where is the image from? Does that computer have a Win7 partition and a SRP or just a Win7 partition?
Are you restoring the image to the same computer? Or to a HD in a different computer?
"Restore to a new HD if a SRP is NOT present" that you haven't broken it apart for the SRP and Win7 separately.
By this I mean the original HD only had Win7. There was no SRP. The Win 7 image was being restored to a new (maybe larger) HD. I don't have a SRP in my Win7 computers. The booting files are contained in the Win7 partition.
After the restore, we get all the way to the "Starting Windows" screen and it just sits there forever.
I have heard of these hardware problems - however, if there was no indication of hardware failure and the unit was booting up fine previously, I would think we are just selecting the wrong options in Ghost?
If we had chosen "Restore MBR" for the C: Drive image (non-system reserved), would that be causing our symptoms? I recall instructions from Norton when I was on the phone with them and they told me to Restore MBR for both the SRP and the Win7 partition. Perhaps that is causing all our problems?
Thanks for all your help and how quickly it has come!
Check source for file system errors Check destination for file system errors Set drive active (for booting OS) DON'T SELECT Disable SmartSector copying DON'T SELECT Ignore bad sectors during copy Copy MBR Destination partition type : Primary Drive letter : None
For Win7
Check source for file system errors Check destination for file system errors Resize drive to fill unallocated space (ONLY if you want to) DON'T SELECT Disable SmartSector copying DON'T SELECT Ignore bad sectors during copy Destination partition type : Primary Drive letter : None
For Copy Drive if a SRP is not present
Check source for file system errors Check destination for file system errors Resize drive to fill unallocated space (ONLY if you want to) Set drive active (for booting OS) DON'T SELECT Disable SmartSector copying DON'T SELECT Ignore bad sectors during copy Copy MBR Destination partition type : Primary Drive letter : None
Restore to a new HD if a SRP is present
For the SRP
Verify recovery point before restore Partition type : Primary Check for file system errors after recovery Set drive active (for booting OS) Restore original disk signature Restore master boot record
For Win7
Verify recovery point before restore Resize drive after recover (unallocated space only) (ONLY if you want to) Partition type : Primary Check for file system errors after recovery
Restore to a new HD if a SRP is not present
Verify recovery point before restore Resize drive after recover (unallocated space only) (ONLY if you want to) Partition type : Primary Check for file system errors after recovery Set drive active (for booting OS) Restore original disk signature Restore master boot record
Restore to the same HD if a SRP is present
For the SRP
No need to restore
For Win7
Verify recovery point before restore Partition type : Primary Check for file system errors after recovery
Restore to the same HD if a SRP is not present
Verify recovery point before restore Partition type : Primary Check for file system errors after recovery Set drive active (for booting OS)
I don't think I have encountered your error after a restore but I think I have seen it. But I can't recall under what circumstances.
Try my suggested options but I don't think they will work. The only difference between my suggestions and what you are doing is that you restored the MBR and Disk Signature twice. I doubt that is relevant.
Are you using a blank unpartitioned HD as the target for your restore process?
Where are your images stored? On an external HD?
Is there anything different about the target computers from the source computer? USB devices attached? I guess not or you would have told me.
One thing would be interesting. Go back to the original computer that you imaged and where Win7 is working properly. Replace its HD with an empty HD and restore the images. See if Win7 works. Or have you already done this?
What partitions are on the original HD (in Disk Management)? I thought Dell always had a Utility partition at the start of the HD. How large is the SRP? The few Dells I've seen recently had the booting files in the Recovery Partition.
I'm not really knowledgable about disk structure but when I've been doing some system restores recently on a laptop -- however not with GHOST as it happens -- I had made an image of the hard drive initially onto an USB connected hard drive and then restored it to a blank larger hard drive in the laptop as a replacement.
It was a COMPAQ but with a SRP and I made the image of the whole drive -- C: and the SRP -- booting to the imaging software CD.
When I restored I just restored the image onto the out of the box new hard drive without any preparation and it did the job perfectly without any specific action on the MBR. The drive just booted up normally
All of which is a lead in to a question -- why did you take a specific action to restore the MBR? Was it because the system would not boot up after restoring the image or did not show the SRP? What "source" did you use to restore the MBR?
I'm sorry if this is answered already but if so ignore the question which I ask because it is my understanding that the MBR contains the code that tells the BIOS what to do and that would include recognizing the two partitions on the drive. So unless you restored it from a source that knew the original geometry you could in fact stop the system from booting up properly.
I haven't done specific tests with Win7 but with WinXP it is not essential to restore the MBR when restoring an image to a new HD. If you don't select the Restore MBR option a standard MBR is created by Ghost. But if you have a special MBR you will need to choose Restore MBR otherwise you will lose your special MBR. Dell computers and other computers that use a Recovery partition have a special MBR. Also certain boot managers have a special MBR. When you create an image with Ghost the First Track is backed up. LBA-0 to LBA-62. All these sectors are restored when you choose Restore MBR. However the Partition Table and the Disk Signature components of LBA-0 are not restored with the Restore MBR option.
Win7 requires the Disk Signature to be restored because a successful boot requires the Disk Signature to match the Partition Signatures in the Registry. WinXP doesn't really need the Disk Signature to be restored. It can cope by recalculating Partition Signatures to match the different Disk Signature.
This is interesting. I zeroed Track 0 and then created a bogus Disk Signature. There was no boot code or partition table present in LBA-0.
A Win7 image was restored to the HD using Ghost 15. I didn't tick Restore MBR or Restore Disk Signature. To my surprise, Win7 booted normally.
Using a Disk Editor I found the Disk Signature had actually been restored, even though it wasn't requested. The boot code was a Standard MBR, not a Win7 MBR. A Standard MBR is OK.
From your point of view, this is either good or bad. Ghost ignored the request to NOT restore the Disk Signature but in doing so, Win7 booted.
I'll let you know what my results are after this morning. Thanks for all your recommendations.
When I said "we get all the way to the Starting Windows screen," I meant that the computer successfully gets through the Dell splash screen and then into the Starting Windows screen, where it freezes. The Windows symbol animates, so the monitor image itself is not frozen, but it never gets beyond that screen. Does that make sense?
I started an online chat with a Norton support technician who told me "It is not necessary to have the System Reserved partition. We need to restore the C: always first and boot the computer and check whether its working fine. Since the C: is the one that has the Boot file location."
Using Brian's suggested settings for Restore to a new HD if a SRP is present, I got to the Starting Windows screen and it remained frozen there.
Using the Norton support tech's advice of *only restoring the C: image*, it booted up to a "BOOTMGR is Missing" error. I booted to the Win 7 DVD and did a repair. Restart gave the same error message. Booted to Win 7 DVD again and did a repair. System booted into Windows 7 successfully.
In Disk Management, there is no SRP, only a C: Drive partition (System, Boot, Page File, Active, Crash Dump, Primary Partition).
I am ecstatic that I have finally gotten Ghost to work for our Windows 7 images, but this is a very round-about way of getting it done! Does anyone have any suggestions??? If I cut an image of this machine now without an SRP, will that make it easier to restore that image in the future?
we get all the way to the Starting Windows screen," I meant that the computer successfully gets through the Dell splash screen and then into the Starting Windows screen, where it freezes.
I saw that frozen screen yesterday. In my case I fixed it by reseating the RAM. I still don't understand your situation.
it booted up to a "BOOTMGR is Missing" error.
That is correct as there are no booting files. You did two repairs from the Win7 DVD and Win7 booted. That is my experience too.
If I cut an image of this machine now without an SRP, will that make it easier to restore that image in the future?
It should. But I still don't understand why your computers froze on that screen. They were obviously well past the booting file stage.
Edit... Did you use Sysprep prior to creating the Ghost images?
Not sure what Sysprep is, so I'm fairly confident that was not part of us creating our Ghost images. Our system is pretty simple (or at least I thought)... Dells that we have stripped down to just SRP and C: partitions, imaging them with Ghost with all of the defaults to an external USB drive, and then restoring them with Ghost from the same USB external drive. Nothing too complicated in my opinion. To me, it makes no sense that I can restore the image right onto the same computer the image came from and it renders the computer unable to boot. I must be doing something fundamentally wrong.
Do you suggest I pull the RAM if I encounter this stuck screen?
To me, it makes no sense that I can restore the image right onto the same computer the image came from and it renders the computer unable to boot.
Ted,
That has me stumped too.
Could you try eliminating the USB HD. As a test.
Install a second HD, create the images to the second HD and restore the images to the original partitions on the first HD. All done in the same computer. Does Win7 boot? I'm not sure where this will lead but I'm really interested to know if it will work.
As a side note, would any settings pertaining to SATA operation have anything to do with this?
If it's any help, I have a SATA drive going bad and when it's not working my system hangs on the animation screen for a very long time. It eventially continues because it's not a system drive and when the drive decides to work it boots normally through that screen.
I'm not suggesting that your drive is bad but Windows defiantly is scanning or trying to access all the drives at that logo screen.