Hi,
I have an Ubuntu Server 12.04 VM on an ESXi host.
There is no sign internally that the drive is bigger. I've shut down the VM, turned it off, turned it back on again and restarted the VM. No difference.
What I NEED is for the LVM partition to be bigger. But the extended partition (sda2) is too small to grow sda5, and of course sda5 can't grow.
What I would LIKE to have is a GPT partition table that looks something like this, barring sizes of partitions:
I'm not asking for partitioning help, rather I'm after either a way to resize the existing extended partition and the lvm2 partition inside, or to copy the data to another drive which will be already partitioned.
Having thought about it awhile I think it might be best to create a new drive and copy data over.
This is a running system and we need it to stay running as much as possible. I know I can use DD to transfer at the filesystem level, but I want to change sizes of the filesystems. (disk destroyer!)
I could probably create a new disk with my preferred partition layout, recursive copy the /boot partition and use LVM2 to copy the filesystems over, but I'm not really sure how to be sure it's right. This is a business system, don't really have the option to mess it up.
Thanks.
I have an Ubuntu Server 12.04 VM on an ESXi host.
- I started with an 8G drive for some reason. I'm out of space.
- I resized to 32G (sparse) in the ESXi control panel.
- Internally, the VM still looks the same size.
- The server is a default install, meaning it has the old partition table, a /boot on sda1 and an LVM as sda5.
- The extended partition is too small now that I've resized the drive.
Code:
fdisk -l /dev/sda
Disk /dev/sda: 34.4 GB, 34359738368 bytes
255 heads, 63 sectors/track, 4177 cylinders, total 67108864 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b169a
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 499711 248832 83 Linux # This is /boot
/dev/sda2 501758 16775167 8136705 5 Extended # This is too small
/dev/sda5 501760 16775167 8136704 8e Linux LVM # This is where / is.What I NEED is for the LVM partition to be bigger. But the extended partition (sda2) is too small to grow sda5, and of course sda5 can't grow.
What I would LIKE to have is a GPT partition table that looks something like this, barring sizes of partitions:
Code:
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1465149168 sectors, 698.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 736B3181-5AB6-416B-B5C8-96D2C7B7B267
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1465149134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 6143 2.0 MiB EF02 bios
2 6144 1054719 512.0 MiB EF00 /boot
3 1054720 22026239 10.0 GiB 0700 /
4 22026240 1465149134 688.1 GiB 8E00 Linux LVMHaving thought about it awhile I think it might be best to create a new drive and copy data over.
This is a running system and we need it to stay running as much as possible. I know I can use DD to transfer at the filesystem level, but I want to change sizes of the filesystems. (disk destroyer!)
I could probably create a new disk with my preferred partition layout, recursive copy the /boot partition and use LVM2 to copy the filesystems over, but I'm not really sure how to be sure it's right. This is a business system, don't really have the option to mess it up.
Thanks.