System Image problem

[Uber Philf]

Hey guys, really not sure if this is the right section to post this, but if it's not please move it.

Yesterday after doing a fresh install, i decided that i would make a system image, but ran into a small problem.

When i got to create a system image, it wants to make an image of both C and D drives.

I only want it to image the C drive, although after doing a pick of looking around, i noticed that some of the boot files are on the D drive.

I've enclosed an image of my Disk Management, to point out that both C and D drives are marked at Active.

Steps i have taken so far to try to fix the problem, set the C Drive as active, removing the other HDD and letting boot repair try to fix it, which said it couldn't.

I'm really out of idea, and would greatly appreciate it if anyone could help me solve this dilemma.

Thanks

 

[whs]

Looks like you have or had an OS on D and the MBR is still sitting there. I guess you need to fix the MBR on C. An image without the MBR is pretty useless.

 

[Uber Philf]

Hmm, never had an OS on D, but another strange thing, my 500GB drive (C) is in SATA port 1, and the 1TB (D,E,F) is in SATA port 2, but in Disk management, shows up as the first drive :/.

 

[whs]

Well, make a test. Disconnect the big disk and see whether C boots. If not, you may have to fix the MBR after all. http://www.sevenforums.com/tutorials/20864-mbr-restore-windows-7-master-boot-record.html

 

[Uber Philf]

Well, make a test. Disconnect the big disk and see whether C boots. If not, you may have to fix the MBR after all. http://www.sevenforums.com/tutorials/20864-mbr-restore-windows-7-master-boot-record.html

I'm so incompetent... >_<

I already removed the 1TB drive, but only ran Startup repair twice, failhard >_<

I'll remove, and run it 3 times, and post back the results.

 

[whs]

 

[Uber Philf]

Ran it 3 times, still no dice, another thing i noticed, that's a bit weird, after i click startup repair from the options, it shows Windows 7, then the Partition size is 0.

Is that supposed to be like that?

 

[nate42nd]

This MAY be because you have a program on the "D" drive that's starting with Windows. My "D" drive does this also, but I have a lot of programs installed on it. I thought that was why....just my thought.

 

[Uber Philf]

Thing is, i don't have any programs on D: at all, it's just media, movies , music etc.

I know on my D drive there's a folder called boot and a boot.dll, but im not game enough to copy them over just in-case all hell breaks loose.

 

[nate42nd]

Thing is, i don't have any programs on D: at all, it's just media, movies , music etc.

I know on my D drive there's a folder called boot and a boot.dll, but im not game enough to copy them over just in-case all hell breaks loose.

I see, well there goes my theory. I has to be some sort of system mapping or something.

This is why people say they don't like Windows imaging I guess. I don't mind this because I have never had this happen where it wants to back up tons of music and movies. That's not cool. I know theres a way to get around it. If I learn anything I will let you know. I wish you the best.

 

[Uber Philf]

Thanks Nate, I'm just thinking, next time i do a format, just to have 500GB drive in it, so it has nowhere else to put the boot files, besides the 100MB partition, that i am missing :/.

 

[whs]

I suggest you call in Gregrocker or Siw2. They are experts in this field. I would hate to give you false advice because i am not firm enough in the MBR subject.

 

[Uber Philf]

Yeah, think that's my last resort.

Neither of them are on :/ hmm.

 

[whs]

Yeah, think that's my last resort.

Neither of them are on :/ hmm.

Send them a PM. They'll pick it up from there.

 

[Uber Philf]

Thanks for your help so far.

 

[whs]

Thanks for your help so far.

You are very welcome. I was not of much help because for some strange reason I had never painted myself into that corner (defunct MBR) yet. So I never had to fix one yet. But at least you know what needs repair.
I wonder though, how it did get to that point in the first place. That is a real mystery. When I do an installation, I always disconnect the "other" disk - mainly because there is usually an OS on the other disk and I do not want to end up in a dual boot situation. But when you installed, that was not the case.

 

[Uber Philf]

Thanks for your help so far.

You are very welcome. I was not of much help because for some strange reason I had never painted myself into that corner (defunct MBR) yet. So I never had to fix one yet. But at least you know what needs repair.
I wonder though, how it did get to that point in the first place. That is a real mystery. When I do an installation, I always disconnect the "other" disk - mainly because there is usually an OS on the other disk and I do not want to end up in a dual boot situation. But when you installed, that was not the case.

Thst's right, no OS on the other disk, but i didn't unplug it..

I couldn't wait much longer, have alot of things to do on it, so i caved in and am currently reinstalling. I DID this time unplug the 1TB to avoid this happening again.

SO i should be fine, marked thread as closed.

 

[whs]

Lots of luck. That was certainly one option. May I suggest you use free Macrium for imaging. Too many people had trouble with the Win7 imaging. Besides, you cannot mount the image files. Only Win7 can.

 

[Uber Philf]

Ahh! fair enough..

On a very sad note, today my brain is not functioning properly.

Made a very stupid mistake, only just as i was about to reinstall, i noticed my D,E and F drives showing up in the 'where do you want to install' leading to only 1 answer, ive been pulling the 500GB drive out, not the 1TB.

After i kicked myself, called myself a retard, ripped all my hair out, i put the 500GB in and took the 1TB out, ran startup repair twice, and now the system is working perfectly. But i on the otherhand, am not working properly.

Very sorry for the muckup, just not with it today.

 

[whs]

LOL, why don't you take a break and make a walk thru the park. That will calm your nerves.