unable to create data volume at /usr/bin/proxinstall line 567

[hambleto]

Hello. I am hoping someone can help me here. I am trying to install the latest iso onto a new server. The server specs are:
IBM X3650 M2
24GB of Ram
12 500GB HD in a raid 5. Via a LSI MR10i Raid card.

Proxmox install CD sees the hd as /dev/sda 5112gb ServerRaid-MR10i However when it gets to the point where it is creating partitions it fails with unable to create data volume at /usr/bin/proxinstall line 567 Does anyone have any thoughts or suggestions?
Thank you,
Ben

 

[tom]

the install partition needs to be < 2TB.

do you plan a single installation or a cluster? and KVM or OpenVZ?

 

[hambleto]

Tom,
Thank you for the quick reply.
So I should make two partitions then? One with 2tb and the other with 3tb? Or do you have another recommendation? I am very open to suggestions.
I planned on adding this box to our other three servers running proxmox.
I would be running both KVM and OpenVZ on this box.

What would you recommend?
Thank you,
Ben

 

[tom]

First, take a look here http://pve.proxmox.com/wiki/Storage_Model

(so I assume you do not have a SAN (nfs, iSCSI or FC)?)
therefore my comments:

Go for 2 Raid volumes - use RAID10 for best performance, RAID5 has slow write speed - but depends on your requirements.

First volume (installation volume)
OpenVZ:
can only use one storage location (var/lib/vz) so you need to calculate how much space do you need for containers - this volume can be up to 2 TB.

Second volume (LVM for KVM guests)
see http://pve.proxmox.com/wiki/Storage_Model#Use_local_devices_.28like_.2Fdev.2Fsd...2F.2C_FC.29

 

[mwojciechowski]

I have similar situation, this time with IBM x3650 M3 (14 x 600GB HDD).

Hardware raid /dev/sda is in RAID10 and it's size is 3.8 TB

When trying to install Proxmox 1.8 I've got an error pointing that fdisk is unable to create partition larger than 2TB, because disk label is msdos.

BUT!

I also have ds3400 disk storage array, one /dev/sdb1 ext3 9TB and it works perfectly. Instead using fdisk I used parted and changed disk label from msdos to gpt (fdisk is unable to do that, parted can).

Commands were:

parted /dev/sdb
mklabel gpt
mkpart primary ext3 0% 100%
set 1 lvm on
quit

The question is: can you modify installation scripts to use parted with gpt instead fdisk with msdos label type? That would solve the problem for everyone using servers with over 2TB HDD.

Best regards,
Marcin

 

[dietmar]

The question is: can you modify installation scripts to use parted with gpt instead fdisk with msdos label type? That would solve the problem for everyone using servers with over 2TB HDD.

We have already fixed that in upcoming 2.0 release.