VirtualBox virtual disk does not resize in GParted
I am running VirtualBox 5.2_18 on Ubuntu 18.04 to host a Windows 7 instance as a guest system. The virtual hard disc is "dynamically allocated" and became too small for what I need to run within the Windows instance. I made four snapshots in the past if this is relevant. Therefore, I followed the large amount of articles on the topic on how to resize the virtual disk. Here is what I did:
- Unmount the disk in VirtualBox
- Resize the disk by executing
VBoxManage modifyhd Windows7.vdi --resize 50000
- Remount the disk in VirtualBox
- Mount GParted ISO to resize the virtual disk
At this point VirtualBox understands the new virtual size (~50GB).
The actual size is still what it has been (13,42GB) as shown in this screenshot:
Than I boot the GParted Live CD. As highlighted in the following GParted screenshot the disk size is still around 30GB which was the old size of the virtual disk.
How can I let GParted recognize the new disk size?
18.04 virtualbox windows-7 gparted
asked Jan 27 at 17:28
JJDJJD
41421036
add a comment |
I am running VirtualBox 5.2_18 on Ubuntu 18.04 to host a Windows 7 instance as a guest system. The virtual hard disc is "dynamically allocated" and became too small for what I need to run within the Windows instance. I made four snapshots in the past if this is relevant. Therefore, I followed the large amount of articles on the topic on how to resize the virtual disk. Here is what I did:
- Unmount the disk in VirtualBox
- Resize the disk by executing
VBoxManage modifyhd Windows7.vdi --resize 50000
- Remount the disk in VirtualBox
- Mount GParted ISO to resize the virtual disk
At this point VirtualBox understands the new virtual size (~50GB).
The actual size is still what it has been (13,42GB) as shown in this screenshot:
Than I boot the GParted Live CD. As highlighted in the following GParted screenshot the disk size is still around 30GB which was the old size of the virtual disk.
How can I let GParted recognize the new disk size?
18.04 virtualbox windows-7 gparted
asked Jan 27 at 17:28
JJDJJD
41421036
In my case, GParted (System Rescue CD boot) reflects the new VDI (block device) after runningVBoxManage modifyhd --resizeagainst the VDI. Looks like something went wrong during themodifyhd --resize, try to run again using a larger size and see if GParted detects the change correctly.
– Terry Wang
Jan 29 at 4:27
See the answer for more suggestions moving forward.
– Terry Wang
Jan 29 at 4:30
add a comment |
I am running VirtualBox 5.2_18 on Ubuntu 18.04 to host a Windows 7 instance as a guest system. The virtual hard disc is "dynamically allocated" and became too small for what I need to run within the Windows instance. I made four snapshots in the past if this is relevant. Therefore, I followed the large amount of articles on the topic on how to resize the virtual disk. Here is what I did:
- Unmount the disk in VirtualBox
- Resize the disk by executing
VBoxManage modifyhd Windows7.vdi --resize 50000
- Remount the disk in VirtualBox
- Mount GParted ISO to resize the virtual disk
At this point VirtualBox understands the new virtual size (~50GB).
The actual size is still what it has been (13,42GB) as shown in this screenshot:
Than I boot the GParted Live CD. As highlighted in the following GParted screenshot the disk size is still around 30GB which was the old size of the virtual disk.
How can I let GParted recognize the new disk size?
18.04 virtualbox windows-7 gparted
asked Jan 27 at 17:28
JJDJJD
41421036
I am running VirtualBox 5.2_18 on Ubuntu 18.04 to host a Windows 7 instance as a guest system. The virtual hard disc is "dynamically allocated" and became too small for what I need to run within the Windows instance. I made four snapshots in the past if this is relevant. Therefore, I followed the large amount of articles on the topic on how to resize the virtual disk. Here is what I did:
- Unmount the disk in VirtualBox
- Resize the disk by executing
VBoxManage modifyhd Windows7.vdi --resize 50000
- Remount the disk in VirtualBox
- Mount GParted ISO to resize the virtual disk
At this point VirtualBox understands the new virtual size (~50GB).
The actual size is still what it has been (13,42GB) as shown in this screenshot:
Than I boot the GParted Live CD. As highlighted in the following GParted screenshot the disk size is still around 30GB which was the old size of the virtual disk.
How can I let GParted recognize the new disk size?
18.04 virtualbox windows-7 gparted
18.04 virtualbox windows-7 gparted
asked Jan 27 at 17:28
JJDJJD
41421036
asked Jan 27 at 17:28
JJDJJD
41421036
asked Jan 27 at 17:28
JJDJJD
41421036
asked Jan 27 at 17:28
JJDJJD
41421036
asked Jan 27 at 17:28
JJDJJD
41421036
41421036
In my case, GParted (System Rescue CD boot) reflects the new VDI (block device) after runningVBoxManage modifyhd --resizeagainst the VDI. Looks like something went wrong during themodifyhd --resize, try to run again using a larger size and see if GParted detects the change correctly.
– Terry Wang
Jan 29 at 4:27
See the answer for more suggestions moving forward.
– Terry Wang
Jan 29 at 4:30
add a comment |
In my case, GParted (System Rescue CD boot) reflects the new VDI (block device) after runningVBoxManage modifyhd --resizeagainst the VDI. Looks like something went wrong during themodifyhd --resize, try to run again using a larger size and see if GParted detects the change correctly.
– Terry Wang
Jan 29 at 4:27
See the answer for more suggestions moving forward.
– Terry Wang
Jan 29 at 4:30
In my case, GParted (System Rescue CD boot) reflects the new VDI (block device) after running
VBoxManage modifyhd --resize against the VDI. Looks like something went wrong during the modifyhd --resize, try to run again using a larger size and see if GParted detects the change correctly.– Terry Wang
Jan 29 at 4:27
In my case, GParted (System Rescue CD boot) reflects the new VDI (block device) after running
VBoxManage modifyhd --resize against the VDI. Looks like something went wrong during the modifyhd --resize, try to run again using a larger size and see if GParted detects the change correctly.– Terry Wang
Jan 29 at 4:27
See the answer for more suggestions moving forward.
– Terry Wang
Jan 29 at 4:30
See the answer for more suggestions moving forward.
– Terry Wang
Jan 29 at 4:30
add a comment |
1 Answer
1
active
oldest
votes
The process of resizing (growing) a dynamic VDI is to:
- Run the
VBoxManage modifyhd Windows7.vdi --resize 50000to resize the VDI - grow the partition (can be the whole disk / block device) on which the file system is created so that it can leverage the additional spaces added (by resizing the VDI)
- grow the file system (NTFS in this case)
Looks like the growing partition step didn't complete successfully.I've done at least 50 VDI resizes for VirtualBox VMs in the past (all Linux though, some were more complicated LVM layout, 1 VG, multiple LVs on single block device) using parted, all worked as expected.
NOTE: If you have multiple snapshots based on this VDI (means there is a VDI tree), I'd recommend doing a VDI clone to get a clean merged (coalesced) VDI of the current state, then do a
VBoxManage modifyhd --resizeon the new VDI, detach the existing VDI (with snapshots) from the VM and attach the resized clone, boot with System Rescue CD and check if the change is correctly reflected. If it does, all good, boot into Windows and rundiskmgmt.mscto grow the volume to use the extra space.
answered Jan 29 at 0:34
Terry WangTerry Wang
6,45932224
Thank you for sharing your advice. I will be able to try them out by March 2019 when I have access to the computer again. I will let you know how it turned out.
– JJD
Jan 29 at 10:00
1
No problem, will be keen to know the result. BTW: if there is not more VMs running on the same box, try to upgrade VirtualBox version to the latest current release with minor, but don't jump to the next major release. This will avoid running into random Storage/VDI related bugs.
– Terry Wang
Jan 29 at 12:39
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2faskubuntu.com%2fquestions%2f1113326%2fvirtualbox-virtual-disk-does-not-resize-in-gparted%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The process of resizing (growing) a dynamic VDI is to:
- Run the
VBoxManage modifyhd Windows7.vdi --resize 50000to resize the VDI - grow the partition (can be the whole disk / block device) on which the file system is created so that it can leverage the additional spaces added (by resizing the VDI)
- grow the file system (NTFS in this case)
Looks like the growing partition step didn't complete successfully.I've done at least 50 VDI resizes for VirtualBox VMs in the past (all Linux though, some were more complicated LVM layout, 1 VG, multiple LVs on single block device) using parted, all worked as expected.
NOTE: If you have multiple snapshots based on this VDI (means there is a VDI tree), I'd recommend doing a VDI clone to get a clean merged (coalesced) VDI of the current state, then do a
VBoxManage modifyhd --resizeon the new VDI, detach the existing VDI (with snapshots) from the VM and attach the resized clone, boot with System Rescue CD and check if the change is correctly reflected. If it does, all good, boot into Windows and rundiskmgmt.mscto grow the volume to use the extra space.
answered Jan 29 at 0:34
Terry WangTerry Wang
6,45932224
Thank you for sharing your advice. I will be able to try them out by March 2019 when I have access to the computer again. I will let you know how it turned out.
– JJD
Jan 29 at 10:00
1
No problem, will be keen to know the result. BTW: if there is not more VMs running on the same box, try to upgrade VirtualBox version to the latest current release with minor, but don't jump to the next major release. This will avoid running into random Storage/VDI related bugs.
– Terry Wang
Jan 29 at 12:39
add a comment |
The process of resizing (growing) a dynamic VDI is to:
- Run the
VBoxManage modifyhd Windows7.vdi --resize 50000to resize the VDI - grow the partition (can be the whole disk / block device) on which the file system is created so that it can leverage the additional spaces added (by resizing the VDI)
- grow the file system (NTFS in this case)
Looks like the growing partition step didn't complete successfully.I've done at least 50 VDI resizes for VirtualBox VMs in the past (all Linux though, some were more complicated LVM layout, 1 VG, multiple LVs on single block device) using parted, all worked as expected.
NOTE: If you have multiple snapshots based on this VDI (means there is a VDI tree), I'd recommend doing a VDI clone to get a clean merged (coalesced) VDI of the current state, then do a
VBoxManage modifyhd --resizeon the new VDI, detach the existing VDI (with snapshots) from the VM and attach the resized clone, boot with System Rescue CD and check if the change is correctly reflected. If it does, all good, boot into Windows and rundiskmgmt.mscto grow the volume to use the extra space.
answered Jan 29 at 0:34
Terry WangTerry Wang
6,45932224
Thank you for sharing your advice. I will be able to try them out by March 2019 when I have access to the computer again. I will let you know how it turned out.
– JJD
Jan 29 at 10:00
1
No problem, will be keen to know the result. BTW: if there is not more VMs running on the same box, try to upgrade VirtualBox version to the latest current release with minor, but don't jump to the next major release. This will avoid running into random Storage/VDI related bugs.
– Terry Wang
Jan 29 at 12:39
add a comment |
The process of resizing (growing) a dynamic VDI is to:
- Run the
VBoxManage modifyhd Windows7.vdi --resize 50000to resize the VDI - grow the partition (can be the whole disk / block device) on which the file system is created so that it can leverage the additional spaces added (by resizing the VDI)
- grow the file system (NTFS in this case)
Looks like the growing partition step didn't complete successfully.I've done at least 50 VDI resizes for VirtualBox VMs in the past (all Linux though, some were more complicated LVM layout, 1 VG, multiple LVs on single block device) using parted, all worked as expected.
NOTE: If you have multiple snapshots based on this VDI (means there is a VDI tree), I'd recommend doing a VDI clone to get a clean merged (coalesced) VDI of the current state, then do a
VBoxManage modifyhd --resizeon the new VDI, detach the existing VDI (with snapshots) from the VM and attach the resized clone, boot with System Rescue CD and check if the change is correctly reflected. If it does, all good, boot into Windows and rundiskmgmt.mscto grow the volume to use the extra space.
answered Jan 29 at 0:34
Terry WangTerry Wang
6,45932224
The process of resizing (growing) a dynamic VDI is to:
- Run the
VBoxManage modifyhd Windows7.vdi --resize 50000to resize the VDI - grow the partition (can be the whole disk / block device) on which the file system is created so that it can leverage the additional spaces added (by resizing the VDI)
- grow the file system (NTFS in this case)
Looks like the growing partition step didn't complete successfully.I've done at least 50 VDI resizes for VirtualBox VMs in the past (all Linux though, some were more complicated LVM layout, 1 VG, multiple LVs on single block device) using parted, all worked as expected.
NOTE: If you have multiple snapshots based on this VDI (means there is a VDI tree), I'd recommend doing a VDI clone to get a clean merged (coalesced) VDI of the current state, then do a
VBoxManage modifyhd --resizeon the new VDI, detach the existing VDI (with snapshots) from the VM and attach the resized clone, boot with System Rescue CD and check if the change is correctly reflected. If it does, all good, boot into Windows and rundiskmgmt.mscto grow the volume to use the extra space.
answered Jan 29 at 0:34
Terry WangTerry Wang
6,45932224
edited Jan 29 at 4:39
answered Jan 29 at 0:34
Terry WangTerry Wang
6,45932224
answered Jan 29 at 0:34
Terry WangTerry Wang
6,45932224
answered Jan 29 at 0:34
Terry WangTerry Wang
6,45932224
6,45932224
Thank you for sharing your advice. I will be able to try them out by March 2019 when I have access to the computer again. I will let you know how it turned out.
– JJD
Jan 29 at 10:00
1
No problem, will be keen to know the result. BTW: if there is not more VMs running on the same box, try to upgrade VirtualBox version to the latest current release with minor, but don't jump to the next major release. This will avoid running into random Storage/VDI related bugs.
– Terry Wang
Jan 29 at 12:39
add a comment |
Thank you for sharing your advice. I will be able to try them out by March 2019 when I have access to the computer again. I will let you know how it turned out.
– JJD
Jan 29 at 10:00
1
No problem, will be keen to know the result. BTW: if there is not more VMs running on the same box, try to upgrade VirtualBox version to the latest current release with minor, but don't jump to the next major release. This will avoid running into random Storage/VDI related bugs.
– Terry Wang
Jan 29 at 12:39
Thank you for sharing your advice. I will be able to try them out by March 2019 when I have access to the computer again. I will let you know how it turned out.
– JJD
Jan 29 at 10:00
Thank you for sharing your advice. I will be able to try them out by March 2019 when I have access to the computer again. I will let you know how it turned out.
– JJD
Jan 29 at 10:00
1
1
No problem, will be keen to know the result. BTW: if there is not more VMs running on the same box, try to upgrade VirtualBox version to the latest current release with minor, but don't jump to the next major release. This will avoid running into random Storage/VDI related bugs.
– Terry Wang
Jan 29 at 12:39
No problem, will be keen to know the result. BTW: if there is not more VMs running on the same box, try to upgrade VirtualBox version to the latest current release with minor, but don't jump to the next major release. This will avoid running into random Storage/VDI related bugs.
– Terry Wang
Jan 29 at 12:39
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1113326%2fvirtualbox-virtual-disk-does-not-resize-in-gparted%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
In my case, GParted (System Rescue CD boot) reflects the new VDI (block device) after running
VBoxManage modifyhd --resizeagainst the VDI. Looks like something went wrong during themodifyhd --resize, try to run again using a larger size and see if GParted detects the change correctly.– Terry Wang
Jan 29 at 4:27
See the answer for more suggestions moving forward.
– Terry Wang
Jan 29 at 4:30