qemu-img input/output errors at 0%

[E_Mouws]

We're trying to migrate a machine from VMware to Proxmox 5 but we're getting input/output errors:
qemu-img convert -f raw -O raw -p /mnt/lun139/server/server-flat.vmdk /mnt/ssd/vm-921-disk-0
qemu-img: error while reading sector 0: Input/output error
qemu-img: error while reading sector 4096: Input/output error
qemu-img: error while reading sector 8192: Input/output error
qemu-img: error while reading sector 12288: Input/output error
qemu-img: error while reading sector 16384: Input/output error
qemu-img: error while reading sector 20480: Input/output error
qemu-img: error while reading sector 24576: Input/output error
qemu-img: error while reading sector 28672: Input/output error

The disk is a thick provisioned VMDK.
Converting using format vmdk does not work also:
qemu-img convert -f vmdk -O raw -p /mnt/lun139/server/server-flat.vmdk /mnt/ssd/vm-921-disk-0
qemu-img: Could not open '/mnt/lun139/server/server-flat.vmdk': Could not read from file: Input/output error

Since it's a input/output error we tried to use another LUN but that gave the same errors.

Also making a clone and trying to import that specific (other) file gave the same errors.

We could succesfully migratie other VM's from the same storage-device (EMC VNX); same LUN so I guess we can exclude the storage-network and/or storage-device.

Trange thing here is that all errors are at 4K boundaries.

Exporting to ovf and import that will not work since that takes much longer to import / convert so that 's not really a valid option.

Someone any thoughts?

 

[Moayad]

Hi,

since Proxmox VE 5.x is already EOL you can migrate the VMs to Proxmox VE 6.x. However, you can check the vmdk file using qemu-img tool:
qemu-img check -f vmdk /mnt/lun139/server/server-flat.vmdk

 

[E_Mouws]

Hi Moayad,


We did. It starts, waits a few seconds and:
qemu-img: Could not open '/mnt/lun139/server/server-flat.vmdk': Could not read from file: Input/output error

So basically the same error.
Migration of our environment to VE 6.x is on the roadmap for Q3 but is not a alternative right now for this migration.

 

[E_Mouws]

We can migratie other VM's without problems so it seems it has something to do with the layout of the VMDK. I guess we can assume there is no (storage-)network or storagedevice issue.
Any ideas ?