Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
I came back from vacation to find my C: drive giving read errors and not booting on my Dell XPS system. Since the drive is 4 years old, I figured the time was right to replace both by C and D drives and expect from two 100 gb drives to two 500 gb drives.
Since I have only a single controller, I am limited to two SATA drives in the system at a time.
After guessing wrong on which drive was which, I pulled the bad C drive and installed a new drive with windows and copied all of the files from the good D drive to the new drive. Reboot, everything is happy there.
I then copied my C drive set of DVD files to the new drive, installed Ghost 12, did a Live Update and verified that the backup I was trying to restore with was good. Still happy.
I then pulled the old D drive and put the second new drive in and proceeded to go through the start of the windows install process so that I can format the drive as an NTFS file system and get an MBR record there.
I then booted into the rescue disk and did a recover from the partition backup to the new partition I just created. I used the chkdisk and verify options and it proceeded without any errors. I did the reboot and boom, blue screen of death:
STOP: 0x0000007B (0xF789E524,0xC0000034,0x00000000,0x00000000)
Slightly worried, I figured that the boot.ini file was incorrect. The OEM disk from Dell had a utility partition on it and I had not recovered that, so fixing the file from partition(2) to partition(1), I tried again. Still failed.
Based on some googling, I then tried fixmbr, fixboot, and bootcfg /rebuild commands. Still no dice. At this point I tried chatting with Norton support. They indicated that I would not have formatted the partition, that I should let the restore process do that. I questioned that advice because I didn't think a partition backup would fix that, but they assured me it would work.
Obvious, since I'm posting here, it didn't.
Did I blow it by creating a partition backup? Is there any hope?
Obviously, I can reinstall windows from scratch, spend several days reinstalling and pull individual files out of my partition backup,. Does anyone have any better ideas? Obviously I still have the old C: drive with read errors on it,
Phil wrote:did you restore partition from image, or exactly how did you make the copy? If you copy(ied) partition to image, then you need to restore image to partition. The image has all the info to make the drive bootable etc. If you just copied files instead of copying the partition, you didn't get all the information you needed. If you still have the original drive and it boots corectly, you could try again.
I did restore from an image of a partition. It starts the boot process but then fails with the stop error.
So there is only one drive in the system now?
did you restore partition from image, or exactly how did you make the copy? If you copy(ied) partition to image, then you need to restore image to partition. The image has all the info to make the drive bootable etc. If you just copied files instead of copying the partition, you didn't get all the information you needed. If you still have the original drive and it boots corectly, you could try again.