Partition resize issue

Hi,

Please see the image - note the difference in the size of the D: drive.

D: is on a RAID array which had a new physical disk added and the controller successfully increased the size of the array.

Windows then increased the size of the disk and confirmed the partition had increased - but it appears not to have updated the filesystem to the correct size.

Thanks,

Benjamin Arnold
Screenshot from Disk Management
pccorrectAsked:
Who is Participating?
 
noxchoConnect With a Mentor Global Support CoordinatorCommented:
You need to convert the disk into Basic type first. Then shrink the D: partition for 500MB apply changes and increase it again. This will "shake" PartMgr tool of Windows which is responsible for correct depiction of file system state and size information in user interface. Your problem is that PartMgr has not refreshed itself. And this shrink and following increase of the size will "shake" it and let work.
If you can shrink and increase without converting the disk into Basic then it is easier. CHKDSK does not fix such issues normally because the problem is deeper than CHKDSK can dive.
0
 
Miguel Angel Perez MuñozCommented:
I had never seen before...

Could yo tell us how do you resized this volume?
0
 
pccorrectAuthor Commented:
Right-click on it and "Expand Volume" - simple as that!

Thanks.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Miguel Angel Perez MuñozCommented:
WOW... try running chkdsk d: /f? remember chkdsk dismount volumes during this check.
0
 
rindiCommented:
First, why are you using a Dynamic disk? That is normally only needed when you are running Windows built-in software RAID, but you are using your RAID controller for that...

I've sometimes seen issues with the reported size after expanding a partition with diskmanagement when I used the complete disk. Because of that I leave about 10MB of the disk unpartitioned. Try shrinking the partition by about 10MB again and then check whether the space is reported correctly. When using 3rd party tools for resizing, I've never seen this happening.
0
 
pccorrectAuthor Commented:
I'll try shrinking the disk and let you know.

In fact now you mention this I've seen on another system when the disk was expanded full WinServerBackup didn't work and shrinking it by 2 GB or therebouts fixed that.
0
 
pccorrectAuthor Commented:
Get "Logical Disk Manager" - "Access is Denied"

Running as Administrator (!)

Some pages seem to imply this is a general "oops, I can't do the resize for some reason" message...?
0
 
rindiCommented:
Maybe you need a reboot.
0
 
pccorrectAuthor Commented:
Tried that many times already
0
 
noxchoGlobal Support CoordinatorCommented:
What is the actual physical size of the HDD0 (RAID) shown in RAID Controller Utility?
Does it correlate with the given size in Windows Disk Management?
0
 
pccorrectAuthor Commented:
Yes - the size at the bottom of the screen is the correct size (following the RAID resize) in the RAID manager. It appears though that the filesystem wasn't resized correctly.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
comment was posted last week about running chkdsk
did you do this?  i'm wondering how the free space is reported there
0
 
pccorrectAuthor Commented:
noxcho - I had already attempted to try that (shrinking the disk) many times but it kept on giving an "Access Denied" error.

Last night I had a "flash of inspiration" and tried stopping the Exchange Information Store (which runs on the D: drive) first (!) and then tried a shrink. It only allowed me to shrink it by 2 MB - but that was enough, and when it completed, the drive had shrunk by 140 GB (ie back to its original size).

I then expanded it by 130 GB which ran successfully and all appears fine now.
0
 
pccorrectAuthor Commented:
This was sort-of the answer, although as I mentioned I had already tried it and it didn't work. But stopping Exchange first (which should have occured to me!) resolved it.

BTW no need to convert the disk to basic first.
0
All Courses

From novice to tech pro — start learning today.