Hi,
So one of my personal media servers recently got a storage upgrade. So due to how I had the first RAID array configured (5TB RAID0) and the drives I had laying around for this, I had to create a separate array...
So there's 2x RAID arrays:
5x 1TB RAID 0 drives (Current)
2 X 4TB RAID 0 drives (New array)
The current configuration has a physical/logical volume group that uses all of the 5TB... called vg_mediavg I've added the two 4TB drives in created the RAID array as normal and rather than adding as a separate disk/storage device in proxmox I've simply tried extending the existing volume group to use the new disks... This appears to have worked to an extent as it looks like proxmox on the host level recognises all of the storage space which is the desired result (Around 11.3TB)
The issue comes to adding the storage space within the virtual machine itself here's some info;
[root@media ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
medialv vg_mediavg -wi-ao---- 4.43t
[root@media ~]# vgs
VG #PV #LV #SN Attr VSize VFree
vg_mediavg 1 1 0 wz--n- 4.43t 0
[root@media ~]# fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 12244.6 GB, 12244561690624 bytes
255 heads, 63 sectors/track, 1488649 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 267350 2147483647+ ee GPT
Disk /dev/mapper/vg_mediavg-medialv: 4874.4 GB, 4874414587904 bytes
255 heads, 63 sectors/track, 592613 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
[root@media ~]#
Any attempts to resize with parted/lvm don't seem to have made a difference they won't use any of the space that was extended on the host level. Additionally I can't resize the disk by selecting the VM (I wasn't expecting to be able to from the GUI but rather from inside the VM due to the nature of me just extending the lv from the host level)
NB: All images come from the virtual machine not from the proxmox host.
What's the advice on this?
Kind Regards,
Jerome Haynes
So one of my personal media servers recently got a storage upgrade. So due to how I had the first RAID array configured (5TB RAID0) and the drives I had laying around for this, I had to create a separate array...
So there's 2x RAID arrays:
5x 1TB RAID 0 drives (Current)
2 X 4TB RAID 0 drives (New array)
The current configuration has a physical/logical volume group that uses all of the 5TB... called vg_mediavg I've added the two 4TB drives in created the RAID array as normal and rather than adding as a separate disk/storage device in proxmox I've simply tried extending the existing volume group to use the new disks... This appears to have worked to an extent as it looks like proxmox on the host level recognises all of the storage space which is the desired result (Around 11.3TB)
The issue comes to adding the storage space within the virtual machine itself here's some info;
[root@media ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
medialv vg_mediavg -wi-ao---- 4.43t
[root@media ~]# vgs
VG #PV #LV #SN Attr VSize VFree
vg_mediavg 1 1 0 wz--n- 4.43t 0
[root@media ~]# fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 12244.6 GB, 12244561690624 bytes
255 heads, 63 sectors/track, 1488649 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 267350 2147483647+ ee GPT
Disk /dev/mapper/vg_mediavg-medialv: 4874.4 GB, 4874414587904 bytes
255 heads, 63 sectors/track, 592613 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
[root@media ~]#
Any attempts to resize with parted/lvm don't seem to have made a difference they won't use any of the space that was extended on the host level. Additionally I can't resize the disk by selecting the VM (I wasn't expecting to be able to from the GUI but rather from inside the VM due to the nature of me just extending the lv from the host level)
NB: All images come from the virtual machine not from the proxmox host.
What's the advice on this?
Kind Regards,
Jerome Haynes
