[SOLVED] Expand LVM from increased hardware Raid volume

delpiero3

Member
May 17, 2020
35
0
11
41
Hello all,

i am requesting your help because i would like to know the best practice to expand the storage in Proxmox from my system.
I recently moved my configuration to a new server, with additional storage and extended the 2 RAID volumes i have on it.
As you can see in my bellow screenshot, there are 2 LVMs, one is the second partition of the first RAID Volumes, with the PVE installation, and the second is meant for my media storage (used by OMV).
Sans titre.png

If we have a look on the output of lsblk, there is what you get :
Sans titre2.png

I am not really sure what the best practice would be, i read a lot about lvresize, pvresize, resizing the partition and so on, but i am not sure which way applies to me.
First of all, when i do a parted on sdb volume, it doesn't see any partition, which confuses me.
Hope that someone can give me some advice, as both sda and sdb have been extended, and maybe the procedure is different from a volume to another.
thanks for the help.
 
Any thoughts on that ? I have a bunch of data on the data volume, and don't have enough storage to save everything. That's why i would like to have your opinion.
Thanks.

Edit :
What i don't really get is that it looks like i don't even have a partition on my sdb drive, it is directly the logical volume, how is that possible ?

I have the impression that i need to use the lvresize command, someone to confirm ?
 
Last edited:
Hello all,

last try by pulling this topic up, hopefully someone with the knowledge is back from vacation, who knows.
 
Hello guys, there are some news.
I am almost there, i still have a little issue.
As i don't have a partition on the RAID volume where my LVM is stored, i was able to increase its size by using the following commands
pvresize /dev/sdb
lvresize -L 34T /dev/Data-VM/vm-101-disk-0

and ended up with my LVM showing the correct size in the webui and my data volume using 34TB out of the 36 (i will use the last 2TB for other VMs).
From there, i resized the virtual disk of my VM using the command :
qm resize 101 virtio1 +17T
and now my VM configuration is good, using the 34TB i would like.
When i go on the OMV host of that VM, lsblk output correctly a physical disk of 34TB as /dev/vdb.
However, i am not able to resize the partition /dev/vdb1 to the maximum size of the disk, i tried xfs_growfs and growpart, none of them works, i keep my partition size to the 16TB allocated previously.
Any idea why this is not working ?
Thanks for the help.
Code:
root@media:~# xfs_info /srv/dev-disk-by-label-Data/
meta-data=/dev/vdb1              isize=512    agcount=17, agsize=268435455 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=0
data     =                       bsize=4096   blocks=4394319611, imaxpct=5
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=521728, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
root@media:~# xfs_growfs /srv/dev-disk-by-label-Data
meta-data=/dev/vdb1              isize=512    agcount=17, agsize=268435455 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=0
data     =                       bsize=4096   blocks=4394319611, imaxpct=5
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=521728, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
root@media:~# growpart /dev/vdb 1
NOCHANGE: partition 1 could only be grown by -30859591647 [fudge=2048]
root@media:~# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sr0     11:0    1 1024M  0 rom 
vda    254:0    0  128G  0 disk
├─vda1 254:1    0  112G  0 part /
├─vda2 254:2    0    1K  0 part
└─vda5 254:5    0   16G  0 part [SWAP]
vdb    254:16   0 33.4T  0 disk
└─vdb1 254:17   0 16.4T  0 part /srv/dev-disk-by-label-Data
 
Solved, i used the OMV-Extras to download the Gparted bootable ISO and started my VM with it, increase the XFS partition from there and now use the full capacity of my Data-VM volume.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!