• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 397
  • Last Modified:

Partition expansion not visible

Hi all,

Our customer is running ESXi5.1 on local storage. My VM hardware and tools is up to date. The VM runs Server 2008 x86.
The VM has 2 virtual disks. The D drive was 700gb thin provisioned, I expanded it to 1tb (the space is available).

In Windows disk management I ran "rescan disks" and the 300gb extra space was detected. I following the wizard to expand the volume to maximum size (around 1tb).

Next, I received an error "the parameter is incorrect". The weirdest thing happened:
- In the visual display the partition is 1tb. In the list of volumes the partition is still 700gb.
- Also in Explorer the server reports 700gb.

What happened? How to get the 1tb space available?
0
eensolution
Asked:
eensolution
1 Solution
 
pjamCommented:
Try reducing it slightly to say 299GB tosee if Parameters are not correct goes away
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
This often happens that partition table gets "corrupted".

The fix, is to shrinks the partition, from it's existing size.

1. Shutdown and restart the OS, check no chkdsk errors.
2. Shrink partition by 50GB.
3. Restart OS.
4. Increase size of partition to the desired size e.g. 1TB.
0
 
RickEpnetCommented:
This happened to me one time.  I created a new partition and copied everything over and change the drive letter and deleted the old partition.  Not a great solution and is not applicable in all situation but it did work for me.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
David Johnson, CD, MVPOwnerCommented:
nopoints: hancooka's suggestion works almost always.
0
 
noxchoGlobal Support CoordinatorCommented:
Actually shrinking it for 500MB and then extending it back is enough. Te problem is in PartMGr driver of Windows which is responsible for refreshing the info about partitions in system. Sometimes it ges dumb and refuses doing it. So this kind of "shaking" makes it work.
0
 
eensolutionAuthor Commented:
Thanks, this did the trick
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now