LV Creation host, time ubuntu-server, 15:24:01 +0000 LV UUID KfMCNz-e2DU-eUXJ-vXA8-Uk0q-DDTW-vnfE27 # Instruct LVM that disk size has changed PV UUID cJxkPB-wQVI-cAMV-jkNc-CDz3-fQ2Y-圓emxI dev/sda is 1.48Tb, but our lv is only 6.102 Gb Extend Physical Drive Partition $ growpart /dev/sda 3 Sector size (logical/physical): 512 bytes / 512 bytes The backup GPT table is not on the end of the device. GPT PMBR size mismatch (16777215 != 3145727999) will be corrected by write. EvaluationĬheck free space available with fdisk $ sudo !! Now, start the machine and get shell a shell on the system.
Hopefully it helps someone else as well! Starting PointĮnter the hardware section of the clone, and resize the disk: This information is available elsewhere but I find myself putting together 2-3 sources to get my result each time, so I’m documenting my process here. At this point, everything is configurable again before I boot in terms of hardware, except for the Disk! We can increase Disk size, but the LVM doesn’t automatically update. I find it convenient to start a VM from a cloud-init enabled template I’ve built which pre-configures the machine with my SSH credentials, networks and so on.
0 kommentar(er)
