Extending PVE Data with a 2nd Drive

[webiscore]

I'm trying to extend the main PVE Data volume adding to it a second drive.

fdisk /dev/sdb
fdisk -l
pvcreate /dev/sdb1
vgcreate newdrive /dev/sdb1
vgextend pve /dev/sdb1
lvextend /dev/mapper/pve-data /dev/sdb1
fsck -nv /dev/mapper/pve-data

Then I increased the meta data pool as mentioned here:
https://pve.proxmox.com/wiki/LVM2#Configuration_2

lvresize --size +1G --poolmetadatasize +1G pve/data

While checking the partition I get an error "Bad magic number in super-block"

root@proxmox:~# fsck -nv /dev/mapper/pve-data
fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mapper/pve-data

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

Am I doing anything wrong over here? Is everything healthy not to worry of future issues?

Thank you in advanced!

 

[dcsapak]

/dev/mapper/pve-data does not contain a filesystem, it is an lvm thinpool so a fsck will not work there

 

[webiscore]

/dev/mapper/pve-data does not contain a filesystem, it is an lvm thinpool so a fsck will not work there

Thank you for the reply, so should I consider everything is working properly and I can complete creating VMs with no issues to worry about?

 

[dcsapak]

Thank you for the reply, so should I consider everything is working properly and I can complete creating VMs with no issues to worry about?

you can check with pvs/vgs/lvs if the result is the one you desired

 

[kappclark]

I have just added a 2TB hd to Proxmox 5.3. I have a Linux samba container. the container uses disk vm-100-disk-0 which proxmox shows is now 3.7TB, after doing LVS at the command prompt. However, when I log into the container, it doesn't show the additional storage (says I have used 82% of 1.8TB).

My question is how do I extend the size of the hard drive within the container ?