AllianceInfoSystems
asked on
Disk Extend 2008
Hi Folks,
Have a unique issue I can't seem to find a good answer to. It does require a bit of backstory.
In March, we did a server upgrade for our customer. They were running on a lone SBS2003 box. We installed a new SBS2011 box in its place, but since the old one was in good shape, we also bought a license for Windows Server 2008 32 bit. The goal was to turn the old server into a Antivirus/Print/Apps server and have the SBS be the file server/dc/exchange. The problem was, Microsoft requires you to keep both SBS servers running when doing a migration. So our 32 bit Server 2008 had to be installed regardless, otherwise we could not complete the migration.
So I chose to install the Server 2008 as a virtual machine on my laptop, set it up and configure it, then move it to the SBS2011 server under Hyper V. This was all successful. I created it initially with a 60 GB Virtual Hard Drive. The D drive was set for 20 GB at that time. We then moved it to the hyper-v, and this was also successful. At that time, I had about 70 GB I could spare for the Virtual Server, so I went ahead and extended the drive to bring it close to 90 GB. This was all successful.
Later, I moved it using Acronis to the physical box (the old SBS2003 server.), blowing that server away in the process. The conversion was successful. But here is the problem:
When I extended the Data drive to reach the remainder of this server's storage capacity (It's about 270GB), Disk Management did it successfully and had no issue, and shows a D partition of 270 GB. But When I look in my computer and properties of D: drive, I still have the 90ishGB drive listed. Right now we are at half of that (45) but I would like to know if anyone has had this issue and what they would recommend doing to troubleshoot. I almost want to max the drive out and see if it allows you to go over but I don't want to do that live.
Suggestions?
Have a unique issue I can't seem to find a good answer to. It does require a bit of backstory.
In March, we did a server upgrade for our customer. They were running on a lone SBS2003 box. We installed a new SBS2011 box in its place, but since the old one was in good shape, we also bought a license for Windows Server 2008 32 bit. The goal was to turn the old server into a Antivirus/Print/Apps server and have the SBS be the file server/dc/exchange. The problem was, Microsoft requires you to keep both SBS servers running when doing a migration. So our 32 bit Server 2008 had to be installed regardless, otherwise we could not complete the migration.
So I chose to install the Server 2008 as a virtual machine on my laptop, set it up and configure it, then move it to the SBS2011 server under Hyper V. This was all successful. I created it initially with a 60 GB Virtual Hard Drive. The D drive was set for 20 GB at that time. We then moved it to the hyper-v, and this was also successful. At that time, I had about 70 GB I could spare for the Virtual Server, so I went ahead and extended the drive to bring it close to 90 GB. This was all successful.
Later, I moved it using Acronis to the physical box (the old SBS2003 server.), blowing that server away in the process. The conversion was successful. But here is the problem:
When I extended the Data drive to reach the remainder of this server's storage capacity (It's about 270GB), Disk Management did it successfully and had no issue, and shows a D partition of 270 GB. But When I look in my computer and properties of D: drive, I still have the 90ishGB drive listed. Right now we are at half of that (45) but I would like to know if anyone has had this issue and what they would recommend doing to troubleshoot. I almost want to max the drive out and see if it allows you to go over but I don't want to do that live.
Suggestions?
I get that you want to extend a drive, but I am confused on about all of the other particulars. Instead of asking a bunch of questions, can you post a screenshot of what it looks like in Disk Management?
The data.vhd has a maximum size of 90G and you cannot change it.
with the vm offline the simplest solution move the current vhd to another location
remove that vhd from the virtual machine and point it to the new location
create a new vhd that is the maximum size that you can and then move the files from the old.vhd to the new.vhd
then remove the old.vhd from the virtual machine.
Note: you can use another virtual machine to do the moving as long as the original virtual machine remains off.
with the vm offline the simplest solution move the current vhd to another location
remove that vhd from the virtual machine and point it to the new location
create a new vhd that is the maximum size that you can and then move the files from the old.vhd to the new.vhd
then remove the old.vhd from the virtual machine.
Note: you can use another virtual machine to do the moving as long as the original virtual machine remains off.
I've had that issue when I extended the disk to use the full space. It is better to leave a little unpartitioned space on the disk (around 10MB is enough). What you can do is reduce the size in diskmanagement by some GB's, reboot, then increase the size again, but leave those 10MB unused at the end of the drive. You will probably need another reboot, but after that the size should be reflected properly.
If that doesn't work use a 3rd party tool, like those available from paragon, to do the resizing. With those I've never had problems.
If that doesn't work use a 3rd party tool, like those available from paragon, to do the resizing. With those I've never had problems.
The problem is in PartMgr by Microsoft. Sometimes it does not care about updating file system parameters in registry when the partition borders change and thus you see different sizes. I think if you look in Windows Disk Management then you could see there that disk used space has also increased.
To fix it follow the steps suggested by rindi. It did always help.
To fix it follow the steps suggested by rindi. It did always help.
ASKER
Hmm, i'll post screenshots to clarify. Just a sec.
ASKER
See below...
ASKER
ahhh.... now your question makes sense. strange stuff!
from command line running as administrator, run diskpart and then the commands 'list disk' and 'list volume' and see if they line up with what My Computer shows or Disk Manager.
from command line running as administrator, run diskpart and then the commands 'list disk' and 'list volume' and see if they line up with what My Computer shows or Disk Manager.
Have you done as I told you, and left some free space (around 10MB) unpartitioned?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Alright, i'll try shrinking and rextending leaving 10MB available.
Also, for the record I did run diskpart, it shows the 258GB partition. Only explorer sees the partition as 86ish
Also, for the record I did run diskpart, it shows the 258GB partition. Only explorer sees the partition as 86ish
The trick is that you reboot the machine after shrink and then extend it.
ASKER
diskpart locked up during the shrink. Yipeeeeee
I'll let you know in a while how it goes...
I'll let you know in a while how it goes...
Oops. Ok, have fun.
Just try again, it probably isn't an issue.
If you keep having problems, I'd backup the drive, delete it and recreate it Should be easier since it is not the boot/system drive.
Have you tried the procedure in this video, and what are your results? Screen shots would be nice
ASKER
Well I let it be for a while, and good news, it has been resolved.
I guess when I tried to shrink the partition by 100 MB it realized that the partition really wasn't truly extended. When I came back to disk manager and it was responsive is showed the disk as 86.4 GB. I extended it again and it now sees all 260 gb of the storage space.
Thanks all.
I guess when I tried to shrink the partition by 100 MB it realized that the partition really wasn't truly extended. When I came back to disk manager and it was responsive is showed the disk as 86.4 GB. I extended it again and it now sees all 260 gb of the storage space.
Thanks all.
ASKER