Merging Partitions

ignatzatsonic said:

You may eventually need to run Diskpart and then "extend".

I seem to recall a similar situation from several months back that was solved in that way.

won't surprise me if we need to go that route. Right now I'm hoping for resolution without having to use DiskPart or PartitionWizard.

[QUOTE=Sir George;1909316]

Crash dumps are simply copies of whatever was in your system's memory at the time of a crash, used for analysis/debugging purposes.

/QUOTE]

Wrong. Please read up on the topic.

SirGeorge,
You may find this microsoft article helpful.
Understanding Crash Dump Files - Ask the Performance Team - Site Home - TechNet Blogs

powerpca said:

Yes but why is the C Drive 350G while the Disk 0 is 698G I merged 2 drives and can no longer see the balance 698-350. Please refer to the snapshot of my Disk Management window

Upon a look at the second screen you posted both "System C" and D are the exact same size indicating Windows is seeing two drives instead of one. One option you can tend to while booted in Windows is another visit to the DM where you use the rescan disks option in the menu bar>Actions to see if Windows will correct itself with a fresh scan of all drives and devices connected.

One other question to ask here would be how you went about deleting the D partition and extended C afterwards? Did you do this while in the DM or use a 3rd party program?

It looks as if the D volume was being mounted as a virtual drive while C was extended as originally planned explaining why Windows still has a memory of it on display in the DM.

NightHawk,
You have raised a couple of good questions.

We'll see what the thread starter has to say.

Flattery. Flattery.

karlsnooks said:

NightHawk,
You have raised a couple of good questions.

We'll see what the thread starter has to say.

One of the reasons for suggesting the D volume could have been mounted as a virtual drive is knowing that from mounting system images made by Acronis True Image which made me wonder if this was why the D volume was still being seen.

Note the blue edges not black on D in the screen as well. That could indicate the volume was mounted as an extended not primary virtual disk as well.

The method used however is the key for solving this one without risking the extended C primary however. The preferred option here would have been to simply plan a fresh start nuking the entire drive and creating a fresh new C primary due to past experience with extending the OS primary and running into a trashed OS when the partition information was somehow lost.

One other advice for the OP would be backing things up from the C volume just in case something does go wrong while trying to get this cleared up. There wouldn't be too much on the drive this fast but just in case.