I am currently experimenting with cloudinit, following this guide.
When trying to attach a disk by importing from an ubuntu cloud image, I get this lvcreate error:
In this case, the disk shall be created on
I tried this command it multiple times, it also showed me another error:
There is more than enough space left (>1TB) on the volume group, though.
If I run this command and replace the storage with
If I then try to move the disk (via UI):
If I create a template from this VM (with disk on
I am at a loss.
Manually creating a VM via the UI still allows me to create a disk on
When trying to attach a disk by importing from an ubuntu cloud image, I get this lvcreate error:
Code:
# qm set 9000 --scsi0 rackstation-iscsi-lvm:0,import-from=/mnt/pve/rackstation/template/iso/noble-server-cloudimg-amd64.img
update VM 9000: -scsi0 rackstation-iscsi-lvm:0,import-from=/mnt/pve/rackstation/template/iso/noble-server-cloudimg-amd64.img
Failed to initialize logical volume rackstation-iscsi-lvm-vg/vm-9000-disk-0 at position 0 and size 4096.
lvcreate 'rackstation-iscsi-lvm-vg/vm-9000-disk-0' error: Aborting. Failed to wipe start of new LV.
rackstation-iscsi-lvm
(of type lvm
and with content
set to images
), a shared lvm on a remote Synology machine, shared between multiple pve nodes.I tried this command it multiple times, it also showed me another error:
Code:
# qm set 9000 --scsi0 rackstation-iscsi-lvm:0,import-from=/mnt/pve/rackstation/template/iso/noble-server-cloudimg-amd64.img
update VM 9000: -scsi0 rackstation-iscsi-lvm:0,import-from=/mnt/pve/rackstation/template/iso/noble-server-cloudimg-amd64.img
Logical volume "vm-9000-disk-0" created.
transferred 0.0 B of 3.5 GiB (0.00%)
qemu-img: error while writing at byte 0: No space left on device
Logical volume "vm-9000-disk-0" successfully removed.
copy failed: command '/usr/bin/qemu-img convert -p -n -O raw /mnt/pve/rackstation/template/iso/noble-server-cloudimg-amd64.img /dev/rackstation-iscsi-lvm-vg/vm-9000-disk-0' failed: exit code 1
If I run this command and replace the storage with
local-lvm
, it works (but it's not desired in this case).If I then try to move the disk (via UI):
Code:
create full clone of drive scsi0 (rackstation:9000/vm-9000-disk-0.raw)
Failed to initialize logical volume rackstation-iscsi-lvm-vg/vm-9000-disk-0 at position 0 and size 4096.
TASK ERROR: storage migration failed: lvcreate 'rackstation-iscsi-lvm-vg/vm-9000-disk-0' error: Aborting. Failed to wipe start of new LV.
If I create a template from this VM (with disk on
local-lvm
) and try to clone it (full clone and target storage set to rackstation-iscsi-lvm
):
Code:
create full clone of drive ide2 (local-lvm:vm-9000-cloudinit)
Logical volume "vm-623-cloudinit" created.
create full clone of drive scsi0 (local-lvm:base-9000-disk-0)
Failed to initialize logical volume rackstation-iscsi-lvm-vg/vm-623-disk-0 at position 0 and size 4096.
Logical volume "vm-623-cloudinit" successfully removed.
TASK ERROR: clone failed: lvcreate 'rackstation-iscsi-lvm-vg/vm-623-disk-0' error: Aborting. Failed to wipe start of new LV.
I am at a loss.
Manually creating a VM via the UI still allows me to create a disk on
rackstation-iscsi-lvm
and install a OS on it.