Can't start VM - Input/output error - TASK ERROR: start failed: QEMU exited with code 1

[mikegodin23]

Hi.
Since this morning I can´t start a VM. I get this error:

kvm: -drive file=/mnt/pve/BACKUP_DADOS/images/103/vm-103-disk-0.raw,if=none,id=drive-sata0,discard=on,format=raw,cache=none,aio=io_uring,detect-zeroes=unmap: Could not open '/mnt/pve/BACKUP_DADOS/images/103/vm-103-disk-0.raw': Input/output error
TASK ERROR: start failed: QEMU exited with code 1

________________________

root@pve:/# df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 4.7M 1.6G 1% /run
/dev/mapper/pve-root 94G 25G 65G 28% /
tmpfs 7.8G 51M 7.8G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
efivarfs 192K 33K 155K 18% /sys/firmware/efi/efivars
/dev/nvme0n1p2 1022M 344K 1022M 1% /boot/efi
/dev/sdc1 2.7T 847G 1.8T 33% /mnt/pve/BACKUP_DADOS
DISCO2 10G 128K 10G 1% /DISCO2
/dev/fuse 128M 44K 128M 1% /etc/pve
/dev/sdb1 1007G 56K 956G 1% /mnt/pve/DISCO1
tmpfs 1.6G 0 1.6G 0% /run/user/0


Can anyone please help me?
Thanks.

Miguel

 

[bbgeek17]

Hi @mikegodin23 , welcome to the forum.

Could not open '/mnt/pve/BACKUP_DADOS/images/103/vm-103-disk-0.raw': Input/output error

The message does mean that there was an IO error trying to open the file. The error likely comes from the Kernel and can be caused by a few things:
- actual disk read error
- slow enough disk that the IO gives up
- bad disk interface (usb/etc)
- less likely - io_uring complication

You can try a few things:
- read the whole file: dd if=[filepath/name] of=/dev/null
- move the file to another location, change the config and try to start
- check the hardware stats of the disk
- check the "dmesg"

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[mikegodin23]

Hi @mikegodin23 , welcome to the forum.


The message does mean that there was an IO error trying to open the file. The error likely comes from the Kernel and can be caused by a few things:
- actual disk read error
- slow enough disk that the IO gives up
- bad disk interface (usb/etc)
- less likely - io_uring complication

You can try a few things:
- read the whole file: dd if=[filepath/name] of=/dev/null
- move the file to another location, change the config and try to start
- check the hardware stats of the disk
- check the "dmesg"

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @bbgeek17
I'm trying this now.
I'll post the output.
Thanks