Windows Server 2012 Missing Disk Space
up vote
0
down vote
favorite
I'm completly lost here, have no clue where the other 20gbs have gone.
Could anyone assist me?
disk-space windows-server-2012-r2 disk-management
edited Jan 28 '15 at 5:58
magicandre1981
80.8k20123200
asked Jan 28 '15 at 5:49
Classicus
111
|
show 3 more comments
up vote
0
down vote
favorite
I'm completly lost here, have no clue where the other 20gbs have gone.
Could anyone assist me?
disk-space windows-server-2012-r2 disk-management
edited Jan 28 '15 at 5:58
magicandre1981
80.8k20123200
asked Jan 28 '15 at 5:49
Classicus
111
I would suggest that you opendiskmgmt.mscvia the Run... command to get a better indication of what the actual allocation is.
– James P
Jan 28 '15 at 10:17
In diskmgmt.msc I get the same information. i.imgur.com/Vagt6t9.jpg
– Classicus
Jan 28 '15 at 16:42
Is it running as a virtual machine?
– James P
Jan 28 '15 at 16:47
Yes, It is a Virtual Private Server.
– Classicus
Jan 28 '15 at 16:51
I think that the disk may be set as dynamically expanding which means it hasn't allocated the 40GB on the host yet. You can test copying some files to see if the useable capacity really is 40GB. Certainly this is the way it works with dynamically allocated RAM if using Windows Server Hypervisor to host the VM's and it makes it very confusing to track resources in the guest OS.
– James P
Jan 28 '15 at 16:53
|
show 3 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm completly lost here, have no clue where the other 20gbs have gone.
Could anyone assist me?
disk-space windows-server-2012-r2 disk-management
edited Jan 28 '15 at 5:58
magicandre1981
80.8k20123200
asked Jan 28 '15 at 5:49
Classicus
111
I'm completly lost here, have no clue where the other 20gbs have gone.
Could anyone assist me?
disk-space windows-server-2012-r2 disk-management
disk-space windows-server-2012-r2 disk-management
edited Jan 28 '15 at 5:58
magicandre1981
80.8k20123200
asked Jan 28 '15 at 5:49
Classicus
111
edited Jan 28 '15 at 5:58
magicandre1981
80.8k20123200
asked Jan 28 '15 at 5:49
Classicus
111
edited Jan 28 '15 at 5:58
magicandre1981
80.8k20123200
edited Jan 28 '15 at 5:58
magicandre1981
80.8k20123200
edited Jan 28 '15 at 5:58
magicandre1981
80.8k20123200
80.8k20123200
asked Jan 28 '15 at 5:49
Classicus
111
asked Jan 28 '15 at 5:49
Classicus
111
asked Jan 28 '15 at 5:49
Classicus
111
111
I would suggest that you opendiskmgmt.mscvia the Run... command to get a better indication of what the actual allocation is.
– James P
Jan 28 '15 at 10:17
In diskmgmt.msc I get the same information. i.imgur.com/Vagt6t9.jpg
– Classicus
Jan 28 '15 at 16:42
Is it running as a virtual machine?
– James P
Jan 28 '15 at 16:47
Yes, It is a Virtual Private Server.
– Classicus
Jan 28 '15 at 16:51
I think that the disk may be set as dynamically expanding which means it hasn't allocated the 40GB on the host yet. You can test copying some files to see if the useable capacity really is 40GB. Certainly this is the way it works with dynamically allocated RAM if using Windows Server Hypervisor to host the VM's and it makes it very confusing to track resources in the guest OS.
– James P
Jan 28 '15 at 16:53
|
show 3 more comments
I would suggest that you opendiskmgmt.mscvia the Run... command to get a better indication of what the actual allocation is.
– James P
Jan 28 '15 at 10:17
In diskmgmt.msc I get the same information. i.imgur.com/Vagt6t9.jpg
– Classicus
Jan 28 '15 at 16:42
Is it running as a virtual machine?
– James P
Jan 28 '15 at 16:47
Yes, It is a Virtual Private Server.
– Classicus
Jan 28 '15 at 16:51
I think that the disk may be set as dynamically expanding which means it hasn't allocated the 40GB on the host yet. You can test copying some files to see if the useable capacity really is 40GB. Certainly this is the way it works with dynamically allocated RAM if using Windows Server Hypervisor to host the VM's and it makes it very confusing to track resources in the guest OS.
– James P
Jan 28 '15 at 16:53
I would suggest that you open
diskmgmt.msc via the Run... command to get a better indication of what the actual allocation is.– James P
Jan 28 '15 at 10:17
I would suggest that you open
diskmgmt.msc via the Run... command to get a better indication of what the actual allocation is.– James P
Jan 28 '15 at 10:17
In diskmgmt.msc I get the same information. i.imgur.com/Vagt6t9.jpg
– Classicus
Jan 28 '15 at 16:42
In diskmgmt.msc I get the same information. i.imgur.com/Vagt6t9.jpg
– Classicus
Jan 28 '15 at 16:42
Is it running as a virtual machine?
– James P
Jan 28 '15 at 16:47
Is it running as a virtual machine?
– James P
Jan 28 '15 at 16:47
Yes, It is a Virtual Private Server.
– Classicus
Jan 28 '15 at 16:51
Yes, It is a Virtual Private Server.
– Classicus
Jan 28 '15 at 16:51
I think that the disk may be set as dynamically expanding which means it hasn't allocated the 40GB on the host yet. You can test copying some files to see if the useable capacity really is 40GB. Certainly this is the way it works with dynamically allocated RAM if using Windows Server Hypervisor to host the VM's and it makes it very confusing to track resources in the guest OS.
– James P
Jan 28 '15 at 16:53
I think that the disk may be set as dynamically expanding which means it hasn't allocated the 40GB on the host yet. You can test copying some files to see if the useable capacity really is 40GB. Certainly this is the way it works with dynamically allocated RAM if using Windows Server Hypervisor to host the VM's and it makes it very confusing to track resources in the guest OS.
– James P
Jan 28 '15 at 16:53
|
show 3 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
Firstly I would check that the file system isn't corrupt as you could run into all sorts of issues. Please try using chkdsk (Windows built in disk checking tool) to check:
- Open a command prompt as administrator
- Type
chkdsk C: /Fand press Enter
- It may well inform you that it cannot lock the volume and requires a scheduled check at boot time, in which case enter
Yand press Enter. You'll need the server/VM to be rebooted for the check to go ahead and obviously there will be some down-time.
If this doesn't work you could try the procedure below. I would recommend getting a full backup done beforehand though
- Open a command prompt as administrator
- Type
diskpartand press Enter. A new command-prompt should appear. - At the
DISKPART>prompt, typelist volumeand press Enter. This will show all the volumes on the system - Type
select volume #(where # is the number of the relevant volume) and press Enter
- Type
extend filesystemand and press Enter
This should adjust the filesystem to use all available capacity in the volume and is based on several articles on the web, including this KB article.
If that still doesn't work, you could try repeating the above but use extend instead of extend filesystem as this will extend the volume itself if there is unallocated space on the disk. But I don't think that is the issue.
answered Jan 29 '15 at 14:47
James P
8,25353047
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Firstly I would check that the file system isn't corrupt as you could run into all sorts of issues. Please try using chkdsk (Windows built in disk checking tool) to check:
- Open a command prompt as administrator
- Type
chkdsk C: /Fand press Enter
- It may well inform you that it cannot lock the volume and requires a scheduled check at boot time, in which case enter
Yand press Enter. You'll need the server/VM to be rebooted for the check to go ahead and obviously there will be some down-time.
If this doesn't work you could try the procedure below. I would recommend getting a full backup done beforehand though
- Open a command prompt as administrator
- Type
diskpartand press Enter. A new command-prompt should appear. - At the
DISKPART>prompt, typelist volumeand press Enter. This will show all the volumes on the system - Type
select volume #(where # is the number of the relevant volume) and press Enter
- Type
extend filesystemand and press Enter
This should adjust the filesystem to use all available capacity in the volume and is based on several articles on the web, including this KB article.
If that still doesn't work, you could try repeating the above but use extend instead of extend filesystem as this will extend the volume itself if there is unallocated space on the disk. But I don't think that is the issue.
answered Jan 29 '15 at 14:47
James P
8,25353047
add a comment |
up vote
0
down vote
Firstly I would check that the file system isn't corrupt as you could run into all sorts of issues. Please try using chkdsk (Windows built in disk checking tool) to check:
- Open a command prompt as administrator
- Type
chkdsk C: /Fand press Enter
- It may well inform you that it cannot lock the volume and requires a scheduled check at boot time, in which case enter
Yand press Enter. You'll need the server/VM to be rebooted for the check to go ahead and obviously there will be some down-time.
If this doesn't work you could try the procedure below. I would recommend getting a full backup done beforehand though
- Open a command prompt as administrator
- Type
diskpartand press Enter. A new command-prompt should appear. - At the
DISKPART>prompt, typelist volumeand press Enter. This will show all the volumes on the system - Type
select volume #(where # is the number of the relevant volume) and press Enter
- Type
extend filesystemand and press Enter
This should adjust the filesystem to use all available capacity in the volume and is based on several articles on the web, including this KB article.
If that still doesn't work, you could try repeating the above but use extend instead of extend filesystem as this will extend the volume itself if there is unallocated space on the disk. But I don't think that is the issue.
answered Jan 29 '15 at 14:47
James P
8,25353047
add a comment |
up vote
0
down vote
up vote
0
down vote
Firstly I would check that the file system isn't corrupt as you could run into all sorts of issues. Please try using chkdsk (Windows built in disk checking tool) to check:
- Open a command prompt as administrator
- Type
chkdsk C: /Fand press Enter
- It may well inform you that it cannot lock the volume and requires a scheduled check at boot time, in which case enter
Yand press Enter. You'll need the server/VM to be rebooted for the check to go ahead and obviously there will be some down-time.
If this doesn't work you could try the procedure below. I would recommend getting a full backup done beforehand though
- Open a command prompt as administrator
- Type
diskpartand press Enter. A new command-prompt should appear. - At the
DISKPART>prompt, typelist volumeand press Enter. This will show all the volumes on the system - Type
select volume #(where # is the number of the relevant volume) and press Enter
- Type
extend filesystemand and press Enter
This should adjust the filesystem to use all available capacity in the volume and is based on several articles on the web, including this KB article.
If that still doesn't work, you could try repeating the above but use extend instead of extend filesystem as this will extend the volume itself if there is unallocated space on the disk. But I don't think that is the issue.
answered Jan 29 '15 at 14:47
James P
8,25353047
Firstly I would check that the file system isn't corrupt as you could run into all sorts of issues. Please try using chkdsk (Windows built in disk checking tool) to check:
- Open a command prompt as administrator
- Type
chkdsk C: /Fand press Enter
- It may well inform you that it cannot lock the volume and requires a scheduled check at boot time, in which case enter
Yand press Enter. You'll need the server/VM to be rebooted for the check to go ahead and obviously there will be some down-time.
If this doesn't work you could try the procedure below. I would recommend getting a full backup done beforehand though
- Open a command prompt as administrator
- Type
diskpartand press Enter. A new command-prompt should appear. - At the
DISKPART>prompt, typelist volumeand press Enter. This will show all the volumes on the system - Type
select volume #(where # is the number of the relevant volume) and press Enter
- Type
extend filesystemand and press Enter
This should adjust the filesystem to use all available capacity in the volume and is based on several articles on the web, including this KB article.
If that still doesn't work, you could try repeating the above but use extend instead of extend filesystem as this will extend the volume itself if there is unallocated space on the disk. But I don't think that is the issue.
answered Jan 29 '15 at 14:47
James P
8,25353047
edited Jan 29 '15 at 14:56
answered Jan 29 '15 at 14:47
James P
8,25353047
answered Jan 29 '15 at 14:47
James P
8,25353047
answered Jan 29 '15 at 14:47
James P
8,25353047
8,25353047
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f870439%2fwindows-server-2012-missing-disk-space%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I would suggest that you open
diskmgmt.mscvia the Run... command to get a better indication of what the actual allocation is.– James P
Jan 28 '15 at 10:17
In diskmgmt.msc I get the same information. i.imgur.com/Vagt6t9.jpg
– Classicus
Jan 28 '15 at 16:42
Is it running as a virtual machine?
– James P
Jan 28 '15 at 16:47
Yes, It is a Virtual Private Server.
– Classicus
Jan 28 '15 at 16:51
I think that the disk may be set as dynamically expanding which means it hasn't allocated the 40GB on the host yet. You can test copying some files to see if the useable capacity really is 40GB. Certainly this is the way it works with dynamically allocated RAM if using Windows Server Hypervisor to host the VM's and it makes it very confusing to track resources in the guest OS.
– James P
Jan 28 '15 at 16:53