Solved Merging Partitions

[powerpca]

I deleted a D partition and merged (extended) with the C Drive. The PC is operating normally. However, the properties dialog shows only 350G while the memory management dialog shows correctly 698G This is a 750G drive. Why does the properties dialog only show 350G. And why do I have listed a crash dump in drive 0? Does this crash dump take up the lost 400G storage and can I delete this crash dump?
Dennis

 

[karlsnooks]

If you have installed SP1, then please update your specs to reflect such.

We need a better disk management snapshot and here is a procedure:

HOW TO POST A SNAPSHOT OF DISK MANAGEMENT DISPLAY
Run disk management:
WIN | type DISKMGMT.MSC | ENTER
WIN=key with Microsoft logo on top.


Maximize the output of Disk Management:
ALT-Spacebar key combo | X key (selects Maximize) |
Drag the field separators (such as between Status and Capacity) to show entire field.


Make a snapshot:
WIN | type SNIPPING | ENTER | New
Drag the cursor around the area you want to snip.
File | Save as | select save location and name | Save


Post the snapshot:
Post a File or Screenshot in Seven Forums

==================================================

oh yes, you can safely delete a crash dump.

 

[powerpca]

the full disk mgmt pic is attached. How do I delete a crash dump. I canot find it on the disk

 

[Night Hawk]

The crash dump file is located in the "C:\Windows\Minidump\" folder. Generally when having a problem you would zip that up in a new zip or rar file to upload for analysis. That will automatically be replaced on it's own when some other minor or more serious system event occurs with no need to rush to delete.

You may need to unhide the protected system files and folders by way of Windows Explorer>menu bar>Tools>Folder options>View tab in order to see it however.

 

[karlsnooks]

You don't delete that which does not exist.

I will show you how to delete any collected dump files.
After following this procedure, I very strongly recommend that you uncheck the item that I show you to check.

CCLEANER | Cleaner icon | Windows tab | System category |
check Memory Dumps

Link to CCleaner in my signature.

 

[Night Hawk]

The Disk Cleanup tool can also be used for that without downloading anything else. That's a quick fix with a few simple steps! How to Get Rid of a Dump File With Disk Cleanup | eHow.com

 

[karlsnooks]

disconnect your disk 1 and your disk 2.
Power backup.

Does DiskManagement now reflect the correct size?
If no, then power down, power up, does diskmanagment now reflect the correct size?

If no, leave the disk 1 and and disk 2 disconnected. We have more steps to execute.

 

[powerpca]

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

 

[karlsnooks]

With disk 1 and disk 2 disconnected:

post a fresh disk management snapshot.
thanks,

 

[ignatzatsonic]

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.

 

[Sir George]

the full disk mgmt pic is attached. How do I delete a crash dump. I canot find it on the disk

A good utility for displaying folder/file size is "Folder Size" which can be downloaded from;

Folder Size - Freeware file size analysis. Check the directory sizes, folder sizes and file sizes on your computer with this freeware tree size analysis tool.

It is free and provides an easy to use GUI. Additionally, you can use it to delete anything that is unnecessary, which includes CrashDump files.

Just an FYI;

Crash dumps are simply copies of whatever was in your system's memory at the time of a crash, used for analysis/debugging purposes. Unless you plan to use them it's prudent to delete them and use the space for other purposes.​

HTH

 

[karlsnooks]

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.

 

[karlsnooks]

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.

 

[karlsnooks]

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

 

[Night Hawk]

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.

 

[karlsnooks]

NightHawk,
You have raised a couple of good questions.

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

 

[Sir George]

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

Did you actually read that article? There is nothing in it that contradicts what I stated. I don't believe this forum is designed for people technically proficient enough to utilize the information in the link you provided.

Perhaps my prior post to you didn't clearly express the fact that I don't find your bloviating all that helpful.

 

[karlsnooks]

Flattery. Flattery.

 

[Night Hawk]

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.

 

[F5ing]

For some reason, I'm not seeing quite the same thing in these snapshots as others. Not sure why, I do see them, although the second DM screenshot is clipped on the right side when I view it.

What I can make out, is I do see Disk0 {C:} and Disk1 {D:} are exactly the same size. Coincidence, maybe? The other thing that's kind of odd is that Disk1 contains only one extended partition containg only one logical partition.