partition lager then 2TB

[Erwin123]

I'm doing a reinstall of a server that had 8 1TB disks with 8 2TB disks.
I'm installing version 1.3 for the time being, next week we will shift to 1.8.

After the 7 hour initialisation of the raid-10 partion of 8TB I tried to install proxmox.
Unfortunaly it gave:
unable to create data volume at /usr/bin/proxinstall line 577

Did a search at this forum and found that you cannot install proxmox (at least 1.3) on partitions larger then 2TB.
I've must have encountered and solved it the previous time I installed this server but I'm not sure I'm doing it right this time.
I'm now making two raidsets, one small to install proxmox and hopefully a big one for the vz data.

After I install proxmox on the small partition, how do I tell proxmox to use the large partition for the container data?
Can I just mount it in Fstab?

I realise my question is kinda noobish but I don't toy with this stuff too much

Thanks in advance!

 

[Erwin123]

I managed to get proxmox installed on the smaller partition.
I now get at df -h

Filesystem Size Used Avail Use% Mounted on
/dev/pve/root 35G 679M 32G 3% /
tmpfs 7.9G 0 7.9G 0% /lib/init/rw
udev 10M 76K 10M 1% /dev
tmpfs 7.9G 0 7.9G 0% /dev/shm
/dev/mapper/pve-data 85G 184M 84G 1% /var/lib/vz
/dev/sdb1 504M 33M 446M 7% /boot

fdisk -l

Disk /dev/sda: 7899.9 GB, 7899999895552 bytes
64 heads, 32 sectors/track, 7534027 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System

Disk /dev/sdb: 149.9 GB, 149996175360 bytes
255 heads, 63 sectors/track, 18235 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 66 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sdb2 66 18235 145948317 8e Linux LVM

Disk /dev/dm-0: 16.1 GB, 16106127360 bytes
255 heads, 63 sectors/track, 1958 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 37.3 GB, 37312528384 bytes
255 heads, 63 sectors/track, 4536 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 91.7 GB, 91746205696 bytes
255 heads, 63 sectors/track, 11154 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-2 doesn't contain a valid partition table

blkid

/dev/sdb1: UUID="2335681d-9a3f-494a-817e-cee62bbe1ab6" TYPE="ext3"
/dev/sdb2: UUID="zGXLBD-CjOO-5RdN-G3wr-26Ug-dwd9-eA72Ne" TYPE="lvm2pv"
/dev/dm-0: TYPE="swap" UUID="8c98d809-cd87-4509-ac13-59799da99468"
/dev/dm-1: UUID="5f5e0a22-2d20-448f-8bc5-562f859c7457" TYPE="ext3"
/dev/dm-2: UUID="ee1694d4-d9e2-4373-a3bb-679b3bbc73d6" TYPE="ext3"

I tried to mount /dev/sda -> /var/lib/vz
But I get a message about blocks upon booting, so I guess I need some formatting orso to do.
I understand this is quite basic linux but could someone please tell me what command to run?

Thanks in advance!
Thanks.

 

[Erwin123]

I found an old thread that said to run pvcreate.
I did that obviously I missed a step:

pvcreate /dev/sda
Physical volume "/dev/sda" successfully created
node:~# vgdisplay
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 139.18 GB
PE Size 4.00 MB
Total PE 35631
Alloc PE / Size 34610 / 135.20 GB
Free PE / Size 1021 / 3.99 GB
VG UUID 6FTzU8-I9D1-MjDp-dlz9-frDl-6X19-Vj1dc5

so still my 7.9B not available.
I'll wait for your answer now

 

[Erwin123]

Lets try again, sorry but I really need this fixed.

I found this solution given by Udo:

pvcreate /dev/sdb
vgdisplay # look for Free PE
vgextend pve /dev/sdb
vgdisplay # look already for Free PE
# give /dev/pve/data 1200G more space - or more
lvextend -L +1200G /dev/pve/data # Attention, 1200G is an example, leave min. 6 GB free, or you get in trouble with your backup
lvdisplay and vgdisplay # to be sure
resize2fs /dev/mapper/pve-data

Now I'm not sure If I need to do pvcreate /dev/sdb
and
vgextend pve /dev/sdb

or do I need to use "/dev/sdb1" or "/dev/sdb2" in my case?

again my fdisk -l:

Disk /dev/sda: 7899.9 GB, 7899999895552 bytes
64 heads, 32 sectors/track, 7534027 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x00000000

Disk /dev/sda doesn't contain a valid partition table

Disk /dev/sdb: 149.9 GB, 149996175360 bytes
255 heads, 63 sectors/track, 18235 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 66 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sdb2 66 18235 145948317 8e Linux LVM

Disk /dev/dm-0: 16.1 GB, 16106127360 bytes
255 heads, 63 sectors/track, 1958 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 37.3 GB, 37312528384 bytes
255 heads, 63 sectors/track, 4536 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 91.7 GB, 91746205696 bytes
255 heads, 63 sectors/track, 11154 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-2 doesn't contain a valid partition table

 

[Erwin123]

Finally figured it out :/

The missing disk IS /sda
I followed the great Udo steps with /dev/sda and my vz partition is growing while I watch.
Now, time for some paracetamol.