Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I installed proxmox on a single 250GB hard drive and I would like to add a second identical hard drive to put more VM's on. I already tried once, and didn't get very far. I added it and formatted it as an ext4, but when I went to use the disk, it said only 8GB was available. That's not quite right. So I did some searching and found that I had to make the device ID 8e for a linux lvm. After I did this, it said I had to restart, so I did... and it wouldn't boot!!!

What did I do wrong? And how do I do it right? (I know I could throw in a RAID card and do a RAID 0, but I'd rather not).

share|improve this question

You can either use your new disk to create new storage resources:

  • New directory (tree) to store files
    • partition and format your device using your filesystem of choice (ext3/4 and XFS are the most commonly used)
    • mount the FS to, say, /srv (do it manualy with mount command and add it to fstab)
    • create the needed directories with mkdir /srv/{isos,images,templates,backups,containers}
    • create the Proxmox storage resources of type directory in the web UI.
  • LVM volume group to store VMs disks "images" as logical volumes:
    • partition your device and set the LVM (8e) flag
    • create a new physical volume with pvcreate /dev/<DEVNAME>
    • create a new volume group with vgcreate <VGNAME> /dev/<DEVNAME>
    • create the Proxmox storage resource of type LVM group in the web UI

Or you can use it to increase size of the default one:

  • LVM physical volume to extend the default pve-data LVM logical volume and /var/lib/vz filesystem:
    • partition your device and set the LVM (8e) flag
    • create a new physical volume with pvcreate /dev/<DEVNAME>
    • extend default VG with vgextend pve /dev/<DEVNAME>
    • extend data logical volume with lvextend /dev/mapper/pve-data /dev/<DEVNAME>
    • verify your FS is clean with fsck -nv /dev/mapper/pve-data
    • resize your FS with resize2fs -F /dev/mapper/pve-data


share|improve this answer
Is it better to extend pve-data or make a new group? I don't understand the ramifications of either. – AllanT Jan 23 at 3:26

Finally found the page that talks about it:

share|improve this answer

Use "GNU parted" for partitions > 2TB and partition type "ee" (GPT)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.