This explains how to extend the Local Container Storage of a Proxmox server. Stitching disks end to end to enable more containers to be stored locally on a Proxmox VE server. In this article, you will learn how to extend Proxmox Local Container Storage. Here is how to create a cluster in Proxmox VE. Below is the command to list disks “fdisk -l“. This command will not be enough for GPT partitions since PVE uses LVMs.
root@pve:~# fdisk -lWARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.Disk /dev/sda: 10.7 GB, 10737418240 bytes
The following will yield the current status of disk devices and their partition details.
cat /proc/partitions
root@pve:~# cat /proc/partitionsmajor minor #blocks name8 0 10485760 sda8 1 1007 sda18 2 130048 sda28 3 10354671 sda3253 0 2359296 dm-0253 1 1179648 dm-1253 2 5636096 dm-2root@pve:~#
Create the Physical Extent
To do this, please enter the command below.
root@pve:~# pvcreate /dev/sdb1Physical volume "/dev/sdb1" successfully created
Now to check if it is available in the set of Physical Volumes.
root@pve:~# pvdisplay --- Physical volume --- PV Name /dev/sda2 VG Name pve PV Size 1.82 TB / not usable 2.56 MB Allocatable yes PE Size (KByte) 4096 Total PE 476803 Free PE 1022 Allocated PE 475781 PV UUID I8G01N-slgw-6nBh-tjhy-EL6E-TJBC-p18pYS"/dev/sdb1" is a new physical volume of "1.82 TB" --- NEW Physical volume --- PV Name /dev/sdb1 VG Name PV Size 1.82 TB Allocatable NO PE Size (KByte) 0 Total PE 0 Free PE 0 Allocated PE 0 PV UUID hDyYtM-yJkZ-GKGa-Cva7-d73A-JKk6-xxxxxx
Note that the Physical Volume /dev/sdb1 does not have any Volume Group Name (VG Name) as yet.
Please see Fix INACCESSIBLE_BOOT_DEVICE in Windows and Windows Server, How to fix Windows Boot Error 0xc0000098 (winload.efi), and Fix Veeam Proxmox VE Backup Error: Failed to prepare disk for backup.
Extend the Volume of Group
To extend the volume of the group. You may want to take a look at this link for more information. Please use the command below.
root@pve:~#vgextend "pve" /dev/sdb1Volume group "pve" successfully extended
To display the volume of a group, please use the command “vgdisplay” as shown below.
root@pve:~#vgdisplay VG Name pve System ID Format lvm2 Metadata Areas 2 Metadata Sequence No 5 VG Access read/write VG Status resizable MAX LV 0 Cur LV 3 Open LV 3 Max PV 0 Cur PV 2 Act PV 2 VG Size 3.64 TB PE Size 4.00 MB Total PE 953734 Alloc PE / Size 475781 / 1.81 TB Free PE / Size 477953 / 1.82 TB VG UUID Tb9Ooy-N9vl-6fb0-3Px7-BX6w-yazp-lq5nVi The VG Size is now expanded (first highlight) and the Free PE (Physical Extents) / Size enlarged.
Resize the Logical Volume
Locate the volume of interest to allocate the available storage capacity. Actual Resizing the Logical Volume
lvresize -l 924296 /dev/mapper/pve-data
Result (Output)
Extending logical volume data to 3.53 TB. Logical volume data successfully resized.
I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.
