Please verify that the image used to create your VM supports disk expansion.


ModelPlatformSupports Expansion?
V100VMWareNo
V200VMWareYes
V101Hyper-VNo
V201Hyper-VYes
V202AzureVMYes
V203AWSYes


Note: The new disk size must be a multiple of 1 MiB (1048576), otherwise the cache size expansion will fail.


To expand the hard drive in your CacheDrive VM, power down the VM using the Morro Cloud Manager, then follow the directions below according to your virtualization platform.

Disk expansion will be performed during boot. So you need to shutdown your virtual CacheDrive first. Then you can change virtual disk size, and then finally you can power it up. Process takes up to a minute or two. (Most of cases are within a few seconds. But if you configure the disks as thin provisioned, it might take longer.)


VMWare

  1. After the CacheDrive is shutdown, ESXi will show the VM as powered off.

  2. Right-click on the VM and select Edit Settings.
  3. Set the data disk size to the desired new size and click Save. Please note that if you have multiple disks assigned for data volume (RAID0), you need to increase both disks at the same size.

  4. Disk size may only be increased.  If you try to shrink the disk, you will see the following error message.

  5. Power on the VM.
  6. Once the CacheDrive is done booting, verify in MCM that the cache size has now been increased.


Hyper-V

  1. After the CacheDrive is shutdown, Hyper-V Manager will show the VM with a state of "off".
  2. Select the VM, then click Settings in the right side menu.
  3. Under SCSI controller, select the data drive.  Note the filename for the virtual hard disk.

  4. Click Cancel.
  5. Click Edit Disk in the right side menu.
  6. Click Next until you reach Locate Disk.

  7. Click Browse and select the virtual hard disk file from the Settings menu.  Then Click Next.
  8. Select Expand, then click Next.
  9. Enter the desired new hard drive size and click Next.  You will see an "Out of Bounds" error popup if you try to shrink the drive.

  10. Verify that the settings are correct, then click Finish.
  11. Click Start in the right side menu.  If you see a popup asking about reverting to a previous checkpoint, click Continue to use the last machine state.

  12. Once the device has finished booting, verify that the cache size has increased in MCM.



AzureVM

Note: When the VM restarts, you may see an error message stating that provisioning failed.  Check the serial console to verify that the VM has started properly.  The expected serial console output is:


  1. After the CacheDrive is shutdown, the Azure Portal will show the VM status as "Stopped".  In this state, the disk cannot be resized.
  2. Completely stop the VM from the Azure Portal by clicking the "Stop" button.
  3. Once the VM is completely stopped, the Azure Portal will show the VM state as "Stopped (deallocated)".


  4. Select the data disk attached to the VM and confirm the Disk state is "Reserved".  If the disk is still attached, Disk state will be shown as "Attached" and cannot be resized.

  5. From Settings/Configuration, enter the desired disk size.  The disk size can only be increased and may not be decreased.  Azure will charge according to the next available pre-defined size.  Please consult with Microsoft for disk size selection.

  6. Restart the VM and verify that the cache size has increased in MCM.


AWS

  1. After the CacheDrive is shutdown, the AWS console will show the VM with a state of "Stopped".
  2. Click Volumes in the left side menu, then select the data volume for the VM.  In the Actions menu, select "Detach Volume".
  3. Once the volume is detached, select "Modify Volume" from the Actions menu.

  4. Enter the new volume size in the "Size" field, then click Modify.  The disk size cannot be decreased, only increased.
  5. The volume may be in the "optimizing" state for a long period of time.  This is normal and the device can still be used while the volume is in this state.

  6. Select "Attach Volume" from the Actions menu and select the CacheDrive's instance.  Enter "/dev/xvdb" for the device, then click Attach.

  7. Restart the VM and verify that the cache size has increased in MCM.