Unallocated Space in Disk Management

[inwell]

Hello,
I have installed Win7 Ultimate (x86) on my 350GB SATA HDD.(2 partitions NTFS) and one old IDE HDD is used as slave (two partitions NTFS) (both disks MBR) (OLD HDD has WinXP Pro installed)

Win 7 disk management shows 8mb and 9mb space as unallocated at the end of partitions (on both HDD).
but the same disks wont show such unallocated disk space when checked through Win XP disk management

what is the reason ? what actually is the real case ? some space unallocated or not ?

regards

 

[Kaktussoft]

Post screenshot please so I can see it

 

[inwell]

@ Kaktussoft

here....

 

[Kaktussoft]

Do you really care about 9MB and 11MB? You can use partition wizard HOME (it's free) to exend the partitions Free download Magic Partition Manager Software, partition magic alternative, free partition magic, partition magic Windows 7 and server partition software - Partition Wizard Online

 

[lehnerus2000]

You may not be able to eliminate those leftover bits.

I've had that issue occur when I have resized partitions.
Even unallocated space at the end of partitions, couldn't be reintegrated into the existing ones.

The only way (that I've found) that works 100% of the time, is to obliterate everything and repartition the drive from scratch (it isn't worth the effort for a few MB).

I suspect that it must be due to some sort of "rounding" issues.
For example, when you create partitions using GParted, it has an option like "Round to nearest cylinder" (the wording might not be correct/exact).

 

[inwell]

Do you really care about 9MB and 11MB? http://www.partitionwizard.com/download.html

true...i really don't care about those few mb..but i was really willing to know why these two OS show the space differently...

 

[gregrocker]

Have you tried to extend your Logicals in Disk Mgmt?

Then try Partition Wizard Resize Partition - Video Help.

If the Home version won't do it the CD version might. It's a great tool to have handy anyway.

 

[AddRAM]

That`s just what you get when you install XP on a drive.

You won't see the unallocated from XP, but you will from 7.

It`s totally normal.

 

[Lady Fitzgerald]

I ran into the same thing with the 2TB WD Black from my old XP machine (may the old machine rest in h...ah...peace). I would up with a single 9MB unallocated partition I couldn't get rid of for love nor money (nor creative language). After fooling around with the piece of...with it in Disk Misman...er...Management and the free version of Minitool Partition Wizard, I managed to make the unallocated partition 54MB (mutter mutter, mumble mumble). I tried formatting the unallocated space and somehow wound up, not only formatting it, but spanning it with the other partition (censored)! I was able to delete the partition, after which Minitool was able to expand the remaining partition into the unallocated volume. I now have just one volume on the drive.

My suggestion would be to try to format the unallocated space, then delete the new partition, then try to expand the other partition into the space. Apparently formatting erases whatever was in the way...I guess. Heck, I don't know; I'm just glad I got the stupid thing fixed!

 

[LMiller7]

I believe this space is reserved for the use of Dynamic disk. When a disk is converted to Dynamic disk it uses this space to store volume information and other information. Without this reserved space the conversion would not be possible.

 

[Lady Fitzgerald]

I believe this space is reserved for the use of Dynamic disk. When a disk is converted to Dynamic disk it uses this space to store volume information and other information. Without this reserved space the conversion would not be possible.

Curious, especially since when I get rid of the space (or it's not there in the first place) the HDD works just fine. Now, the unallocated space that shows up when installing an OD is a whole 'nuther story. It is necessary but, even then, there is a way to get rid of it (actually, incorporate it in the C:/ partition itself).

 

[jimbo45]

Hi there
sometimes this happens because you are using "Logical Volumes in an Extended partition". Personally I would run everything as Primary partitions -- but I don't think I'd bother for the sake of a few measly MB. I also wouldn't mic FAT32 and NTFS partitions on the same physical drive either -- however that's just my preference.

Cheers
jimbo

 

[LMiller7]

Curious, especially since when I get rid of the space (or it's not there in the first place) the HDD works just fine. Now, the unallocated space that shows up when installing an OD is a whole 'nuther story. It is necessary but, even then, there is a way to get rid of it (actually, incorporate it in the C:/ partition itself).

The drive will work fine with absolutely no issues, unless you try to convert the drive to Dynamic Disk. Them the conversion will fail.

 

[gregrocker]

But you can convert the Logicals to Primary using Partition Wizard to set partition as Primary or Logical
if you want to test the theory that Logicals cause this problem, and the steps I proposed earlier fail.

It would be nice to finally know what causes this. Dynamic is another theory. Did you have a Dynamic Disk at any time because it is not now.

If this cannot be resolved then the next time you have the chance I would wipe the HD with Diskpart Clean Command but you must of course have your data backed up, along with a System Image if you are not reinstalling.