07-26-2012 12:01 PM
I've been trying for about a week now to replace my existing hard drive with a new, larger hard drive. I've had multiple Ghost fails, and now multiple Windows Backup and Restore fails.
Note: I verified, and I'm using Service Pack 1 on Ghost 15 (ran LiveUpdate too, and it said it was most recent)
I did some searching, and on this last round, followed Brian's instructions from here:
Which were very similar to the detailed instructions I found here (higlighted in green, post by redk9258):
That is, I backed up my drive using Ghost.
- I looked for recovery points by Filename.
- I selected the System Reserved v2i file
- I used edit, and selected the new hard drive (which was unallocated)
Note: It came up automatically having 100MB partition; so I chose Delete Drive, and selected the complete, empty drive
- I set the settings like Brian's post had: Primary, Check for file system errors, Set drive active, restore orig disk sig, restore master boot record.
- Clicked OK, then Add, so I could add the Local C Drive v2i file
- I again used edit, and selected the new hard drive:
Note: It came up automatically having 465GB partition (the old drive size); so I chose delete drive, and selected the complete, empty drive.
I then set the settings like Brian's post had, but added the resize: Resize Drive (set to max), Primary Partition, Check file systems for errors.
Clicked OK, Clicked Next, and Finish. It went through the restore, and it said it restored successfully. I was optimistic.
I then rebooted, and low and behold, Windows started. I made it into Windows, and the only thing I saw was an error saying that the device driver for my hard drive failed (Seagate Momentus 750GB if that matters.) So I went into device manager, clicked on update driver, did automatic update, it found the driver (from Microsoft corporation), and said it needed to restart to finish updating the driver.
When it went to update, instead of loading windows, it went into the system recovery mode; and said that:
Startup Repair cannot repair this computer automatically. Looking at the details, it gave:
Event Name: StartupRepairOffline
Event 1: 7.1.7600.16385
Event 2: 7.1.7600.16385
Event 3: Unknown
Event 4: 137
Event 5: AutoFailover
Event 6: 1
Event 7: MissingOsLoader
I did some searching, and found some posts (no longer have links) that said it could take multiple restarts for the automatic recovery to fix. So, I tried about five times now, and I keep getting that same error.
So, I searched for MissingOsLoader, and found an article saying someone fixed thier similar issue by rebuilding using command prompt and bootrec (again, can't re-find the link), but it told me to:
I did all these commands successfully, and then it said to re-run the startup repair; that it should fail one more time, then it should pass successfully. I tried running the startup repair three more times, and always get the same error.
I've found other articles on how to fix startup issues, but I'm getting in over my head. Have you guys seen this issue before, and how can I fix it?
(I echo the thoughts of many other people. Why can't upgrading a hard drive just be more simple. I've killed over 40 hours on this already, and still don't have a working system yet. /end_of_rant)
Thanks for any help,
07-26-2012 12:25 PM
Several notes / clarifications:
- In this most recent round of attempt, I used the backup/restore method; NOT the disk copy
- Prior to going in to try this round, I went into disk manager, removed all the partitions; and went into diskpart and did a CLEAN command (which is why I said it went to unallocated space.)
So now that I've gone into the Startup Repair, I went to a command prompt, and saw that it looks like it assigned the System Reserved partition the drive letter C, and my Win7 partition is now D (at least, that's what it's showing in the command prompt, and verified using diskpart) So, to me, for some reason, it looks like after the first boot (the first boot worked fine), Windows now has given the System Reserved partition a drive letter.
I tried to remove that drive letter using diskpart; but it just adds it back the next time I boot.
I found this:
Which says to zero out the diskID. Don't know (yet) if I should try that... (or what problems that would cause down the line - i.e. windows re-authorization, etc?)
07-26-2012 03:11 PM
I then rebooted, and low and behold, Windows started. I made it into Windows, and the only thing I saw was an error saying that the device driver for my hard drive failed (Seagate Momentus 750GB if that matters.)
Weird. You made it into Windows so Ghost worked. What happened subsequently has nothing to do with Ghost.
Can you repeat the restore but don't do anything about the error. Just reboot and get back to us.
07-26-2012 03:47 PM
Yeah, I know. Unfortunately, it's still somehow related to the image; as my original drive didn't do this. (I'm thinking maybe the registry settings for drive ID's? but that shouldn't happen if it copied the original drive... don't know.) If the drive has been seen by the OS; if you use diskpart to clean it; then it shouldn't have any drive letters assigned / everything should be unallocated; right?
FYI, I did do the Win98 FDisk command to clear the DiskID, (which is from one of your posts http://community.norton.com/t5/Other-Norton-Produc
I then tried to re-run the system repair. Ran the system repair once, and it said it would need to restart; but on restart, it gave me the resource unavailable message that I have seen others get. Couldn't get past that (will admit I didn't try very hard though; need to get this working, and soon.)
So, I went into diskpart again, cleared the destination drive; and now I'm trying to restore just the original C drive, and get rid of the stupid SRP, following your instructions:
Will let you know how that goes.
If that doesn't work, backup plan is to go to Seagate DiskWizard; as both source and destination drives are Seagate, and I think that is a disk image, rather than partition image. (from what I've been reading...) Please enlighten me if I'm mistaken.
I've done quite a bit of research, so to help other people, here are a bunch of links with info:
Hope it helps folks out...
07-26-2012 04:24 PM
I still feel it's nothing to do with your image or with Ghost. Could the new HD be "bad"? Could a restart have fixed the problem? Certainly updating the driver caused a worse problem.
07-26-2012 05:07 PM
It's possible what you are thinking, but I'm thinking it wasn't the driver fix. It didn't even get to do the usual update which happens on startup of windows after you do an update; because it never even booted to windows on the second go around. It went straight to the recovery partition (which now had a C drive assigned to it.) I'm speculating though; I'm sure you know much more about this than me...
Hoping the removal of the SRP cures my problem (as then there is no other partition to be assigned drive letters, etc.) That's my thought anyway...
07-26-2012 05:12 PM
...and as for the new hard drive being bad; highly unlikely. Before I knew about not having the OS see the drive at all, I formatted it, and ran disk tools on it; and it came out clean; and then I deleted that partition before trying another restore. When the first Ghost image failed, I did the same thing (create partition, format, run disk tools, etc.) Did it a third time after another image failed (as I wanted to start with a clean/tested hard drive.) All of those disk tests came out successful; not even a rogue index entry...
FYI, I tried to do a disk copy with Ghost too (was trying to exhaust all options) and I had the same issue as noted by several other users. That is, I couldn't see the drive as a valid destination unless it was initialized and with a simple volume by the OS (which would fail based on my readings - the link I have above, which I believe was from you - about XP not booting with drive copy.)
Anyway, thanks again for your thoughts...
07-26-2012 08:46 PM
So here's where I'm at. I cleaned the drive, restored using the settings recommended by red. After the restore, I opened diskpart; and my drive was F, not C. So I used Assign to set the drive that WAS set to C to G, and then set my new destination as C (also using Assign).
I then tried to do the bcdboot command, but got an incompatible version message. Since I was still in the Ghost SRD, I'm guessing it was 32 bit, and my Windows is 64-bit.
So, I shutdown, removed all the other devices; and booted up into my Windows 7 System Repair disk. It said that there were errors, do I want to fix them? I said no, went to advanced settings, and opened up a command prompt. From there, I was able to successfully execute the bcdboot command.
I shut everything down, and prayed while trying to boot the system. Unfortunately, got a BOOTMGR is missing, press Ctl+Alt+Del to restart.
I'm going to try to use the Win7 System Repair disk, and hopefully that fixes things...
07-26-2012 09:27 PM
Start again, as in start from getting a new backup image?
Or just trying the restore of the SRP then Win 7 (like the closest thing I had to working.)?
Or trying the restore of Win 7, and trying to get rid of the SRP?
Each of these iterations are 5-6 hours for a backup, and another 5-6 (or longer for USB) for a restore...
I've got quite a bit of time invested already; and would like to be a little more clear...