New additional hard drive

[Kynao]

Hi,

I use Proxmox since release 1.3 where vm are installed on a main sata harddrive.
Today i added a second sata harddrive i would like to use as a backup for the vm.
So i added a preformated ext3 drive but proxmox does not sse it, how can i do to male it usable to Proxmox ?

 

[tom]

first, upgrade your system. 1.3 is very outdated.

to your question:
just mount your drive somewhere (add it to /etc/fstab via the console) and then use the gui to add this dir as backup storage.

 

[Kynao]

lol, i'm not in 1.3, i'm in 1.7, i simply use proxmox since 1.3.
Yes, i'am searching how to mount it

 

[Kynao]

Ok, so i know nothing about linux so my steps are risky )
First i use fdisk -l to see where is my second harddrive
Then did a mkfs.ext3 -j /dev/sdb, apparently proxmox still works so my vm are not deleted.

I wait for the end to try a mount /dev/sdb /etc/fstab if that makes any sense

Edit : That didn't work, i have mount point /etc/fstab is not a directory, you meant i have to create the directory ?

 

[udo]

Ok, so i know nothing about linux so my steps are risky )
First i use fdisk -l to see where is my second harddrive
Then did a mkfs.ext3 -j /dev/sdb, apparently proxmox still works so my vm are not deleted.

I wait for the end to try a mount /dev/sdb /etc/fstab if that makes any sense

Edit : That didn't work, i have mount point /etc/fstab is not a directory, you meant i have to create the directory ?

Hi,
what do you want to do with the second disk? If you want to use space for kvm-guest, you can install a separate lvm on the disk. If you simple want to expand your /var/lib/vz you can easily use the second disk for that (also lvm).
For a filesystem you should use a partition-table: create a partition - then you have sdb1:
fdisk /dev/sdb
mkfs.ext3 /dev/sdb1
mkdir /data
mount /dev/sdb1 /data

to make the mount "rebootable" you must use an entry in /etc/fstab.
take a look with "cat /etc/fstab"

Udo

 

[Kynao]

Proxmox propose to define backup jobs, so i simply would like to use the second drive for that purpose.

 

[arkestler]

Hi,
If you simple want to expand your /var/lib/vz you can easily use the second disk for that (also lvm).

How do you do this?

 

[udo]

How do you do this?

Hi,
asuming that your second disk is sdb, create an partition (type 8e) o the disk

fdisk /dev/sdb

see "man fdisk" and "man lvm"
create a physical volume:

pvcreate /dev/sdb1

look before for space:

vgdisplay pve

extend the volumegroup:

vgextend pve /dev/sdb1

and look with vgdisplay again.

Udo

 

[Kynao]

mkdir /data

this is done from what directory ?

 

[arkestler]

Thanks for the great info! So should the pve storage group be added to the storage in the web interface? What is the difference of using pve vs the directory that the system created by default set up?

 

[udo]

this is done from what directory ?

Hi,
it's equal, because the path is absolute ( /data) not relative ( data ).

Udo

 

[Kynao]

and drive is not important ? i can do mkdir /data from anywhere ?

 

[udo]

and drive is not important ? i can do mkdir /data from anywhere ?

Drive???
proxmox runs on linux not windows!
On *nix the root is / - all things are below the root. during boot was a filesystem mounted on / - this is in case of pve the logical volume pve-root.

With "mkdir /data" (which is only an example btw.) you only create an empty directory with the name data on the filesystem directly under / - not more and not less.

Perhaps you should buy an linux-beginners book?

Udo

 

[Kynao]

Thanks for the informations Udo
Of course i need to read Linux books, and also so many books on so many subjects
but that would be overkill just to install a second hard drive on a proxmox system,
one day i will do overkill my pleasure, in the meantime, i continue to improve my developer skills.
Thanks again

 

[phreekbird]

Hi,
asuming that your second disk is sdb, create an partition (type 8e) o the disk

fdisk /dev/sdb

see "man fdisk" and "man lvm"
create a physical volume:

pvcreate /dev/sdb1

look before for space:

vgdisplay pve

extend the volumegroup:

vgextend pve /dev/sdb1

and look with vgdisplay again.

Udo

I have done all that, it works great, see below:

proxmox:~# vgdisplay pve
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 6
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 2
Act PV 2
VG Size 931.02 GB
PE Size 4.00 MB
Total PE 238340
Alloc PE / Size 237317 / 927.02 GB
Free PE / Size 1023 / 4.00 GB
VG UUID JsejWr-qd1N-kH2J-gPnb-0jMO-XfBc-kt7faI

proxmox:~#

OK, but when I look at the website for proxmox, I cannot see the extra storage anywhere:

Storage List

	Storage Name	Type	Enabled	Active	Shared	Used (GB)	Capacity (GB)
	local	Directory	Yes	Yes	No	13.29	355.59	3.74%​

What am I doing wrong here?

 

[udo]

I have done all that, it works great, see below:



OK, but when I look at the website for proxmox, I cannot see the extra storage anywhere:



What am I doing wrong here?

Hi,
because you don't defined an extra storage. You only expand an exsisting storage.

Your vg show only 4GB free (min. space required for backup (snapshot)) - so I assume you have allready expand your logical viólume (pve-data)?
What show following commands

pvs
vgs
lvs

Udo

 

[phreekbird]

proxmox:~# pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 pve lvm2 a- 465.26G 4.00G
/dev/sdb1 pve lvm2 a- 465.76G 0
proxmox:~# vgs
VG #PV #LV #SN Attr VSize VFree
pve 2 3 0 wz--n- 931.02G 4.00G
proxmox:~# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
data pve -wi-ao 827.02G
root pve -wi-ao 96.00G
swap pve -wi-ao 4.00G
proxmox:~#

 

[udo]

proxmox:~# pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 pve lvm2 a- 465.26G 4.00G
/dev/sdb1 pve lvm2 a- 465.76G 0
proxmox:~# vgs
VG #PV #LV #SN Attr VSize VFree
pve 2 3 0 wz--n- 931.02G 4.00G
proxmox:~# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
data pve -wi-ao 827.02G
root pve -wi-ao 96.00G
swap pve -wi-ao 4.00G
proxmox:~#

Arghh,
there was an misunderstanding on my side. You don't want to see an extra storage but more space!

I assume you forgot to extend your filesystem on the pve-data volume.
Use simply

df -h /var/lib/vz
resize2fs /dev/mapper/pve-data
df -h /var/lib/vz

Udo

 

[phreekbird]

That worked ... it was teh resize2fs c0mmand, I new I was forgeting to do something! (I have shrunken vmware HD's this way ... so I knew roughly what to do with proxmox) but of course I forgot the resize ... thanks a ton man.

proxmox:~# resize2fs /dev/mapper/pve-data
resize2fs 1.41.3 (12-Oct-2008)
Filesystem at /dev/mapper/pve-data is mounted on /var/lib/vz; on-line resizing required
old desc_blocks = 23, new_desc_blocks = 52
Performing an on-line resize of /dev/mapper/pve-data to 216798208 (4k) blocks.
The filesystem on /dev/mapper/pve-data is now 216798208 blocks long.


proxmox:~# df -h /var/lib/vz
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-data 815G 14G 801G 2% /var/lib/vz
proxmox:~#