Problems creating my first VM

R

renegade

New Member
Aug 5, 2021
7
0
1
38
Hi all,

I am new to Proxmox and recently installed ProxMox VE 7.0-8

I ran a vgextend and added another drive to the volume group pve.

When I go to create my first VM - I select the iso etc - and fill in the details. It then fails at the create stage with the following error:

Code: 
WARNING: ext4 signature detected on /dev/pve/vm-100-disk-0 at offset 1080. Wipe it? [y/n]: [n]
  Aborted wiping of ext4.
  1 existing signature left on the device.
  Failed to wipe signatures on logical volume pve/vm-100-disk-0.
TASK ERROR: unable to create VM 100 - lvcreate 'pve/vm-100-disk-0' error:   Aborting. Failed to wipe start of new LV.

I have researched some others problems which usually suggest updating and restarting - or that an orphaned VM exists - but I have never created a VM until now.

In an effort to debug - i looked for a logical volume list command and found:

Code: 
lvdisplay
  --- Logical volume ---
  LV Path                /dev/pve/swap
  LV Name                swap
  VG Name                pve
  LV UUID                sHmc4h-Tw0S-l2bG-g2CL-DQ09-iCPV-L7Qutt
  LV Write Access        read/write
  LV Creation host, time proxmox, 2021-08-03 11:03:01 +0100
  LV Status              available
  # open                 2
  LV Size                8.00 GiB
  Current LE             2048
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0
  
  --- Logical volume ---
  LV Path                /dev/pve/root
  LV Name                root
  VG Name                pve
  LV UUID                tpkQ5x-yjOR-Gahz-Hlsb-n8FC-UNbE-gjYA1c
  LV Write Access        read/write
  LV Creation host, time proxmox, 2021-08-03 11:03:01 +0100
  LV Status              available
  # open                 1
  LV Size                62.25 GiB
  Current LE             15936
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1
  
  --- Logical volume ---
  LV Name                data
  VG Name                pve
  LV UUID                0BYpIe-O31l-MLMq-NHjs-Dhmi-wZuI-RFwdZp
  LV Write Access        read/write
  LV Creation host, time proxmox, 2021-08-03 11:03:11 +0100
  LV Pool metadata       data_tmeta
  LV Pool data           data_tdata
  LV Status              available
  # open                 0
  LV Size                159.98 GiB
  Allocated pool data    0.00%
  Allocated metadata     1.00%
  Current LE             40955
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:4
  
root@proxmox:/var/lib/vz/template/iso#

which suggests pve is ok - but we only see the 3 proxmox volumes so far.

Please suggest some next steps I can take!
 
Last edited:
* please post the output of `pveversion -v` (there was a fix for this/a similar issue recently)
* please post your /etc/pve/storage.conf (and indicate on which storage you try to create the disk)

Thanks!
 
Hi.

I also looked for any existing file called vm-100* but they don't exist:

Code: 
root@proxmox:/dev/pve# find / -type f -name "vm-100*"
find: ‘/var/lib/lxcfs/cgroup’: Input/output error
root@proxmox:/dev/pve#

Output from pveversion -v
Code: 
root@proxmox:/dev/pve# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-1-pve)
pve-manager: 7.0-8 (running version: 7.0-8/b1dbf562)
pve-kernel-5.11: 7.0-3
pve-kernel-helper: 7.0-3
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.0.0-1+pve5
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-4
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-7
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.1-1
proxmox-backup-file-restore: 2.0.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.2-4
pve-cluster: 7.0-3
pve-container: 4.0-5
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-7
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.4-pve1
root@proxmox:/dev/pve#

Contents of storage.cfg (assuming you mean cfg as conf doesnt exist ;)
Code: 
root@proxmox:/dev/pve# cat /etc/pve/storage.cfg


dir: local


    path /var/lib/vz


    content vztmpl,iso,backup





lvmthin: local-lvm


    thinpool data


    vgname pve


    content rootdir,images





lvm: main_storage


    vgname pve


    content images,rootdir


    shared 0

I am trying to create the VM storage on volume group pve - which is the group i extended successfully with another drive.
 
renegade said:
libpve-storage-perl: 7.0-7
Click to expand...
the glitch was fixed with libpve-storage-perl 7.0-8 - upgrade to the latest version - that should help you creating the VM successfully :)
 
Excellent!

How do you suggest doing that?

I was thinking:
Code: 
apt-get upgrade libpve-storage-perl

or just the whole lot:
Code: 
apt-get upgrade
 
  • Like
Reactions: renegade
Bingo - sorted. I am a bit surprised than an ISO burnt last week - of the latest ProxMox arrives in that kind of condition?

Many thanks!
 
renegade said:
Bingo - sorted. I am a bit surprised than an ISO burnt last week - of the latest ProxMox arrives in that kind of condition?
Click to expand...

The ISO was released on 06.07.2021 (PVE ISOs are only created on point releases)
Proxmox VE is a rolling release - meaning installing updates regularly is recommended (and sometimes necessary to fix issues that are reported after a particular version is released)

I hope this explains it!
 
Hi!

It does .... a bit -- but am I still not right in saying - anybody who currently downloads the iso created on 06.07.2021 - will hit the exact problem I did? Until they do a dist-ugrade?
 
renegade said:
It does .... a bit -- but am I still not right in saying - anybody who currently downloads the iso created on 06.07.2021 - will hit the exact problem I did? Until they do a dist-ugrade?
Click to expand...
Yes they will (if they try to create a VM on a LVM/LVM-thin storage - but as said the general recommendation (especially with a new system) is to run
`apt update; apt dist-upgrade` once after setting it up.

I hope this helps!
 
In a way that is comforting and unsettling! No regressing testing pre release!?

Nevertheless its not an issue - and I am very happy now - thank you.
 
You must log in or register to reply here.
Top Bottom