maplerest.blogg.se

1. Ubuntu logical volume manager 16.04 server how to#
2. Ubuntu logical volume manager 16.04 server update#

You're specifying the first partition on the partition table, and extending the partition to use 100% of the disk. If you are using Ubuntu 14.04, or the command below does not work, do NOT continue, and create a new OVA then migrate to that instead. This option is unavailable for Ubuntu 14.04 and below, and requires you to delete and re-create the partition, which if done incorrectly, can destroy your server's disks beyond recovery. If your VM Appliance is running Ubuntu 16.04 or newer, then the default version of parted installed should support resizepart, which allows you to resize partitions. Number Start End Size Type File system Flagsġ 2048s 134215679s 134213632s primary boot, lvm Sector size (logical/physical): 512B/512B Then print the partition table so you have it available for reference: (parted) p First, open the parted prompt with parted /dev/sdaĭon't forget to set your units to sectors to make it easier to track. Then, we'll need to go into parted to modify the partitions. dev/sda1 * 2048 134215679 134213632 64G 8e Linux LVM Resizing the partitionsĪs the OVA uses a swap partition, you'll need to turn that off swapoff -a However, the partition /dev/sda1 should still be set to 64GB Device Boot Start End Sectors Size Id Type This should now display the new size of the disk /dev/sda at the top line. Once the server has booted back up, log back in and check fdisk. If this is still displaying the original size of 64GB, you will need to reboot the VM. You should be able to see that /dev/sda has increased, i.e, if you increase the disk to 100GB: Disk /dev/sda: 100 GiB, 107374182400 bytes, 209715200 sectors On the VM, probe the hardware to see if it picks up the larger disk by running partprobe Once that's done, in your hypervisor, clone the existing VM, so you have a backup in case things go wrong, and then increase the size of the disk on the original VM. This should stop any changes being made or new tickets being processed during the procedure. We would also recommend disabling the helpdesk, by going to Admin > Setup > Settings, and checking the box marked Disable the helpdesk, before clicking Save. To find out what version of Ubuntu your OVA is using, login to the server via SSH, and run the following command: cat /etc/os-release You can then migrate your old helpdesk over to your new helpdesk using the dputils tool. In this case, we recommend performing a fresh OVA install, then increase the disk space on the new OVA following this guide.

Ubuntu logical volume manager 16.04 server update#

At the time of writing, this version is past the End of Standard Support, and is coming up to End of Life, so we highly recommend you update to a newer version. Older versions of the Deskpro OVA installed Ubuntu 14.04 LTS instead. This guide is specifically for Ubuntu 16.04 LTS and above. The guide below will walk you through the process of increasing the disk size on the Deskpro OVA.

Ubuntu logical volume manager 16.04 server how to#

We would need to tell the server that the disk has increased and how to use it. However, as it is running Linux, it is not as straight forward as increasing the size of the disk on your hypervisor. One of the options to resolve this issue is to increase the size of the disk on your Deskpro server. However, if you have a larger helpdesk, or have been using the VM Appliance for a long time, you may find you are running out of disk space. By standard, the OVA requires a 64GB disk, which will be adequate for the majority of users. If you installed your Deskpro on-premise server using the VM Applicance (OVA), then you would not have had the option to configure the virtual hardware during installation.