[SOLVED] Can't create new VM with VirtIO Block

S

sirkope

Member
May 2, 2020
58
1
8
53
Hi,

After I deleted a VM, I can't create new VM with VirtIO Block, only with IDE.

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

And if i create with IDE, also can't add Hard Disk with VirtIO Block

lvcreate 'bigdata/vm-101-disk-0' error: Aborting. Failed to wipe start of new LV. at /usr/share/perl5/PVE/API2/Qemu.pm line 1424. (500)

root@pve:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 512M 0 part /boot/efi
└─sda3 8:3 0 232.4G 0 part
├─pve-swap 253:0 0 4G 0 lvm [SWAP]
├─pve-root 253:1 0 58G 0 lvm /
├─pve-data_tmeta 253:2 0 1.5G 0 lvm
│ └─pve-data 253:13 0 151.3G 0 lvm
└─pve-data_tdata 253:3 0 151.3G 0 lvm
└─pve-data 253:13 0 151.3G 0 lvm
sdb 8:16 0 931.5G 0 disk
└─sdb1 8:17 0 931.5G 0 part
├─bigdata-vm--100--disk--0 253:4 0 120G 0 lvm
├─bigdata-vm--103--disk--0 253:5 0 110G 0 lvm
├─bigdata-vm--103--disk--1 253:6 0 100G 0 lvm
├─bigdata-vm--103--disk--2 253:7 0 4M 0 lvm
├─bigdata-vm--104--disk--0 253:8 0 150G 0 lvm
├─bigdata-vm--104--disk--1 253:9 0 4M 0 lvm
├─bigdata-vm--100--disk--1 253:10 0 4M 0 lvm
├─bigdata-vm--102--disk--0 253:11 0 150G 0 lvm
├─bigdata-vm--102--disk--2 253:12 0 4M 0 lvm
└─bigdata-vm--101--disk--1 253:15 0 4M 0 lvm

there is no vm-101-disk-0 on bigdata
 
One more question: qm unlink might be help, but don't know what --idlist parameter is.
 
root@pve:~# pvs
PV VG Fmt Attr PSize PFree
/dev/sda3 pve lvm2 a-- 232.38g 15.99g
/dev/sdb1 bigdata lvm2 a-- <931.51g 301.49g
root@pve:~# vgs
VG #PV #LV #SN Attr VSize VFree
bigdata 1 9 0 wz--n- <931.51g 301.49g
pve 1 3 0 wz--n- 232.38g 15.99g
root@pve:~# lvs -a
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
vm-100-disk-0 bigdata -wi-a----- 120.00g
vm-100-disk-1 bigdata -wi-a----- 4.00m
vm-102-disk-0 bigdata -wi-a----- 150.00g
vm-102-disk-2 bigdata -wi-a----- 4.00m
vm-103-disk-0 bigdata -wi-a----- 110.00g
vm-103-disk-1 bigdata -wi-a----- 100.00g
vm-103-disk-2 bigdata -wi-a----- 4.00m
vm-104-disk-0 bigdata -wi-a----- 150.00g
vm-104-disk-1 bigdata -wi-a----- 4.00m
data pve twi-a-tz-- <151.30g 0.00 1.06
[data_tdata] pve Twi-ao---- <151.30g
[data_tmeta] pve ewi-ao---- <1.55g
[lvol0_pmspare] pve ewi------- <1.55g
root pve -wi-ao---- 58.00g
swap pve -wi-ao---- 4.00g
 
Hi,

I've made reboot several times, but not helped. Afternoon, at home, I'll make photos/video.
 
Looks for me like the lvm volume exists already... Like you didn't deleted it or something.

Probably the disk exists and isn't attached?

Try
lvremove /dev/bigdata/vm-105-disk-0
You can force it with -f
And then create again...
 
I don't want to delete the existed VM's. I think lvm is mounted:

root@pve:~# fdisk -l
Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: WDC WD2500AAKX-6
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9D80E195-E56A-4A7D-B8A2-CF1D91552904

Device Start End Sectors Size Type
/dev/sda1 34 2047 2014 1007K BIOS boot
/dev/sda2 2048 1050623 1048576 512M EFI System
/dev/sda3 1050624 488397134 487346511 232.4G Linux LVM


Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: TOSHIBA HDWD110
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x9a29fb42

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 1953525167 1953523120 931.5G 83 Linux


Disk /dev/mapper/pve-swap: 4 GiB, 4294967296 bytes, 8388608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-root: 58 GiB, 62277025792 bytes, 121634816 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/bigdata-vm--100--disk--0: 120 GiB, 128849018880 bytes, 251658240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 482856C9-8CA5-11EA-A1B2-A2E64DABC4AA

Device Start End Sectors Size Type
/dev/mapper/bigdata-vm--100--disk--0-part1 2048 1187839 1185792 579M Windows recovery environment
/dev/mapper/bigdata-vm--100--disk--0-part2 1187840 251451391 250263552 119.3G Microsoft basic data
/dev/mapper/bigdata-vm--100--disk--0-part3 251451392 251656191 204800 100M EFI System


Disk /dev/mapper/bigdata-vm--103--disk--0: 110 GiB, 118111600640 bytes, 230686720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6761560E-71D5-47AD-A875-F5F8B1BAACC9

Device Start End Sectors Size Type
/dev/mapper/bigdata-vm--103--disk--0-part1 2048 1050623 1048576 512M EFI System
/dev/mapper/bigdata-vm--103--disk--0-part2 1050624 230684671 229634048 109.5G Linux filesystem


Disk /dev/mapper/bigdata-vm--103--disk--1: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x8079c154

Device Boot Start End Sectors Size Id Type
/dev/mapper/bigdata-vm--103--disk--1-part1 2048 209715199 209713152 100G 83 Linux


Disk /dev/mapper/bigdata-vm--103--disk--2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/bigdata-vm--104--disk--0: 150 GiB, 161061273600 bytes, 314572800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F954CCF0-6F9B-4D9F-9774-11425ADD5F5D

Device Start End Sectors Size Type
/dev/mapper/bigdata-vm--104--disk--0-part1 2048 1050623 1048576 512M EFI System
/dev/mapper/bigdata-vm--104--disk--0-part2 1050624 314570751 313520128 149.5G Linux filesystem


Disk /dev/mapper/bigdata-vm--104--disk--1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/bigdata-vm--100--disk--1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/bigdata-vm--102--disk--0: 150 GiB, 161061273600 bytes, 314572800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: E67B4079-BBB4-4C1E-8B9C-FB5B5D59A0F0

Device Start End Sectors Size Type
/dev/mapper/bigdata-vm--102--disk--0-part1 2048 2099199 2097152 1G EFI System
/dev/mapper/bigdata-vm--102--disk--0-part2 2099200 14548991 12449792 5.9G Linux swap
/dev/mapper/bigdata-vm--102--disk--0-part3 14548992 314572766 300023775 143.1G Linux filesystem


Disk /dev/mapper/bigdata-vm--102--disk--2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/pve-vm--101--disk--1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--101--disk--0: 128 GiB, 137438953472 bytes, 268435456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 5A0B6A95-B5E2-4468-B4A7-463E41B9C524

Device Start End Sectors Size Type
/dev/mapper/pve-vm--101--disk--0-part1 40 409639 409600 200M EFI System
/dev/mapper/pve-vm--101--disk--0-part2 409640 268435415 268025776 127.8G Apple APFS

Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.
 
I don't want to delete lvm also because VM's are working:

I just can't create new one.

vm102.PNG
 
Last edited:
I don't know what you did before, but pve tryes to make vm-105-disk-0 and fails, because the disk exists (or the lvm volume).

I clearly don't see any vm-"105"-disk-0 in the above vm's or logs...

So this volume didn't got deleted anytime before, you deleted your vm. Dunno why this happened.

However, you can create a new vm, just use another id and not 105.

Make a new vm with id 106 or 206 or 555 xD
And that should work.
 
Ramalama said:
I don't know what you did before, but pve tryes to make vm-105-disk-0 and fails, because the disk exists (or the lvm volume).

I clearly don't see any vm-"105"-disk-0 in the above vm's or logs...

So this volume didn't got deleted anytime before, you deleted your vm. Dunno why this happened.

However, you can create a new vm, just use another id and not 105.

Make a new vm with id 106 or 206 or 555 xD
And that should work.
Click to expand...
There was VM101, and VM105, but I deleted them, with the proper way: detach and remove disks, then delete VM with purge.

create2.PNG

And no, it isn't work with other ID's :( Tryed with 106, 200, 123...
 
Last edited:
Hmm, bigdata lvm not in pool, should it be in it?

root@pve:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
vm-100-disk-0 bigdata -wi-a----- 120.00g
vm-100-disk-1 bigdata -wi-a----- 4.00m
vm-102-disk-0 bigdata -wi------- 150.00g
vm-102-disk-2 bigdata -wi------- 4.00m
vm-103-disk-0 bigdata -wi-a----- 110.00g
vm-103-disk-1 bigdata -wi-a----- 100.00g
vm-103-disk-2 bigdata -wi-a----- 4.00m
vm-104-disk-0 bigdata -wi-a----- 150.00g
vm-104-disk-1 bigdata -wi-a----- 4.00m
data pve twi-aotz-- <151.30g 19.17 1.99
root pve -wi-ao---- 58.00g
swap pve -wi-ao---- 4.00g
vm-101-disk-0 pve Vwi-a-tz-- 128.00g data 22.66
vm-101-disk-1 pve Vwi-a-tz-- 4.00m data 3.12
 
I don't know what the problem is.

But your sda drive looks weird. You have there before the efi partition an 1mb bios boot partition, never seen that.

However, sorry, I don't know what your problem is. Probably something messed up, but what exactly, dunno.

Maybe someone else can help.
 
Another note, the error says something with efi, but i guess bigdata is on dev/sdb which isn't efi.
Dunno if it has something todo with that or not, however, hopefully someone experienced can help out.

Cheers
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back