Problem with system booting after image restoration from related question
I have done it several times. I booted with Ghost32 and successfully created images of the C: partition and the D: partition. I re-created the partitions as needed. The drive letters even show correctly with DISKPART. I booted back with ghost32 and moved the images back to their respective drives. Within my wds winpeimage I can use the command window to go to C: and D: and all the files are there from the images.
So everything seems to have gone perfect! i reboot machine and it won't boot. It sees the drives, the logical drives, etc. It tries to PXE boot (which is where i did the DISKPART and Ghost32 is in my bootable image). For some reason a direct image did not make the C: drive bootable. DISKPART shows the Disk 0, All partitions, all volumes correct, healthy even shows the correct used space. BUT NO BOOT.
Any ideas how to fix this? Boot.ini shows the correct information, but i thought that the EXACT image that was the C: drive before would make the "new" C: drive the exact same. In the past when doing this to servers, I never had this issue. I am on a major time crunch here, I am onsite RIGHT NOW hoping to get some ideas.
So everything seems to have gone perfect! i reboot machine and it won't boot. It sees the drives, the logical drives, etc. It tries to PXE boot (which is where i did the DISKPART and Ghost32 is in my bootable image). For some reason a direct image did not make the C: drive bootable. DISKPART shows the Disk 0, All partitions, all volumes correct, healthy even shows the correct used space. BUT NO BOOT.
Any ideas how to fix this? Boot.ini shows the correct information, but i thought that the EXACT image that was the C: drive before would make the "new" C: drive the exact same. In the past when doing this to servers, I never had this issue. I am on a major time crunch here, I am onsite RIGHT NOW hoping to get some ideas.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you both for the very quick responses :)
That is why I love this site!
Thanks, I split the points, but majority went to Vahiid.
That is why I love this site!
Thanks, I split the points, but majority went to Vahiid.
Glad I could help :)
It is the little things that can mess u up.
ASKER
Almost exactly what you said vahiid,
from cmd in pxe boot os utility I created.
sel disk 0
sel par 1
active
Exited everything and rebooted. It worked like it is supposed to. lol Teaches me to get in a hurry! geez!