Proxmox RC1 LVM pain...

bobele

New Member
Feb 22, 2012
3
0
1
Hi there..

i have a problem :)

im trying now a full week to setup a LVM group..the get the snapshot capability ..
maybe my brain is dead..but maby some of you can help me up again..
maybe a smal howto in a step by step format just for dummies :))

here is my setup

proxmox 2 rc1 running on a
500gb hd
my vm´s are stored
on a 2x 750gb HD raid 1 (hardware raid)
plus an extra 500gb hd for backups/snapshot 50/50 patition
plus an extra 500gb USB HD for testing till now
plus a 8BG usbstick for testing

error: if im tryin to snapshot a running vm

INFO: starting new backup job: vzdump 100 --mode snapshot --compress lzo --storage extHDD1 --node proxmox
INFO: Starting Backup of VM 100 (qemu)
INFO: status = running
INFO: mode failure - unable to detect lvm volume group <<<<<<----------- problem :)
INFO: trying 'suspend' mode instead
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: suspend vm
INFO: creating archive '/extHDD1/dump/vzdump-qemu-100-2012_02_22-22_04_16.tar.lzo'
INFO: adding '/extHDD1/dump/vzdump-qemu-100-2012_02_22-22_04_16.tmp/qemu-server.conf' to archive ('qemu-server.conf')
INFO: adding '/storage/vmdk/images/100/vm-100-disk-1.vmdk' to archive ('vm-disk-ide0.vmdk')
INFO: resume vm
INFO: vm is online again after 7 seconds





vgdisplay
root@proxmox:~# vgdisplay
Couldn't find device with uuid tTUHNp-RSHi-Asuk-iMp9-tNak-1Ogf-AKlfui.
--- Volume group ---
VG Name extHDD
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 1
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 2
Act PV 1
VG Size 257.46 GiB
PE Size 4.00 MiB
Total PE 65911
Alloc PE / Size 0 / 0
Free PE / Size 65911 / 257.46 GiB
VG UUID lpoucS-cRQu-qcVN-OdVE-aMdh-BX9y-VkUIxV


--- 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 465.26 GiB
PE Size 4.00 MiB
Total PE 119106
Alloc PE / Size 115012 / 449.27 GiB
Free PE / Size 4094 / 15.99 GiB
VG UUID RO3e5D-LeFP-Cj0x-QTC9-ai2S-MhJL-jYgZFE

root@proxmox:~# pvdisplay
Couldn't find device with uuid tTUHNp-RSHi-Asuk-iMp9-tNak-1Ogf-AKlfui.
--- Physical volume ---
PV Name /dev/sde1
VG Name extHDD
PV Size 250.00 GiB / not usable 4.53 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 64000
Free PE 64000
Allocated PE 0
PV UUID BaUu2s-LZai-HyR5-wJ54-cSoe-yRRP-emE004


--- Physical volume ---
PV Name unknown device
VG Name extHDD
PV Size 7.47 GiB / not usable 4.06 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 1911
Free PE 1911
Allocated PE 0
PV UUID tTUHNp-RSHi-Asuk-iMp9-tNak-1Ogf-AKlfui


--- Physical volume ---
PV Name /dev/sdc2
VG Name pve
PV Size 465.26 GiB / not usable 4.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 119106
Free PE 4094
Allocated PE 115012
PV UUID LGy57B-w3pe-Vfcr-ADq5-FUtY-z848-J5qKqe


"/dev/sde2" is a new physical volume of "215.75 GiB"
--- NEW Physical volume ---
PV Name /dev/sde2
VG Name
PV Size 215.75 GiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID lKk7qB-DRjm-rdbU-pMES-gv1c-Gw4z-U6Gv4b



root@proxmox:~# fdisk -l


Disk /dev/sdb: 500.0 GB, 499999834112 bytes
255 heads, 63 sectors/track, 60788 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


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


Disk /dev/sda: 750.0 GB, 749999226880 bytes
255 heads, 63 sectors/track, 91182 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


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


Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000370fb


Device Boot Start End Blocks Id System
/dev/sdc1 * 1 66 523264 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sdc2 66 60802 487862272 8e Linux LVM


Disk /dev/sdd: 8023 MB, 8023703552 bytes
5 heads, 32 sectors/track, 97945 cylinders
Units = cylinders of 160 * 512 = 81920 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Device Boot Start End Blocks Id System
/dev/sdd1 * 51 97946 7831616 7 HPFS/NTFS


Disk /dev/dm-0: 103.1 GB, 103079215104 bytes
255 heads, 63 sectors/track, 12532 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


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


Disk /dev/dm-1: 7516 MB, 7516192768 bytes
255 heads, 63 sectors/track, 913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


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


Disk /dev/dm-2: 371.8 GB, 371799883776 bytes
255 heads, 63 sectors/track, 45202 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


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


Disk /dev/sde: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa7660927


Device Boot Start End Blocks Id System
/dev/sde1 1 32636 262148638+ 83 Linux
/dev/sde2 32637 60801 226235362+ 83 Linux


root@proxmox:~# mount
/dev/mapper/pve-root on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/mapper/pve-data on /var/lib/vz type ext3 (rw)
/dev/sdc1 on /boot type ext3 (rw)
/dev/sda on /storage type ext3 (rw)
/dev/sdb on /Platte type ext3 (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,default_permissions,allow_other)
beancounter on /proc/vz/beancounter type cgroup (rw,name=beancounter)
container on /proc/vz/container type cgroup (rw,name=container)
fairsched on /proc/vz/fairsched type cgroup (rw,name=fairsched)
192.168.116.101:/c/Data on /mnt/pve/NetgearNAS type nfs (rw,vers=3,addr=192.168.116.101)
/dev/sdd1 on /extHDD1 type ext3 (rw)



maybe there is just a smal error ..can someone check my config and HELP me and my brain :)
i have testet an lvm group an another pc with 2x 2gb usbsticks and its working but why not here ?


thanx

;-)
 
Seems you mount /dev/sdd1 on /extHDD1 (/dev/sdd1 does not look like a LVM device, so it is not possible to make snapshots)
 
thanks for reading and the hint...

but please what to do now ?
iv try to create --with pvcreate
and than create a ext3 filesystem on that pv..to mount it..
if i don´t create a ext3 on it i cannot mount it ?!

????
 
thanks for reading and the hint...

but please what to do now ?
iv try to create --with pvcreate
and than create a ext3 filesystem on that pv..to mount it..
if i don´t create a ext3 on it i cannot mount it ?!

????
Hi,
lvm-storage (for images) don't use an filesystem! e.g. you create an volumegroup and define this vg in the storage-gui (for images).
After that you can add disks for VMs on this storage (which is simple an lv with the size of the disk).

To move existing VMs to the lvm-storage use backup/restore (you can also use dd, but this is not beginners-like).

Udo
 
mhmm ok..

but i think do make the snapshot work..the backup volume were i wanna store the snapshots..have to be a lvm to ? or at leaat a pv or vg ??
 
I haven't used v2.0, so I could be wrong, but in v1.9 you have to define the storage for backups as "NFS Share" or "Directory", and set content to "VZDump backups" when adding the storage in web GUI. The backups will then be stored in the directory specified as .tar files. I imagine it's similar in v2.0, but correct me if I'm wrong.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!