Hi everybody,
I have 2 HP MicroProliant Gen8 Servers in my house both with PVE 9.1.6 one with 3 VMs and other without vms and stopped for Bakup.
All woked fine, no problems with my vms I decide update and upgrade vms and PVE hosts, vms upgraded well, I have 2 or 3 Bakups made in a exernal NAS
First I upgraded the backup server whitout vms and restarted it, all seems fine with PVE 9.2.5 so I shut it down, Then I upgraded the main PVE server without problems and reboot it.
When the Server startup, I realized that one of my vms was stopped I tried start it manually but when grub loaded the vm stops
I tried restoring backups of my vm but noones works. A few minutes later I realized that other started vms fails... I saw the Syslog and I get I/O Errors in my Disks, in my nvme disk, in my sata disk and in my RAID........
I turned On my second server and tried to restore vm backup and get I/O error restoing in my nvme...
Anyone had I/O problems with 9.2.5?
Can Somebody help me?
I have 2 HP MicroProliant Gen8 Servers in my house both with PVE 9.1.6 one with 3 VMs and other without vms and stopped for Bakup.
All woked fine, no problems with my vms I decide update and upgrade vms and PVE hosts, vms upgraded well, I have 2 or 3 Bakups made in a exernal NAS
First I upgraded the backup server whitout vms and restarted it, all seems fine with PVE 9.2.5 so I shut it down, Then I upgraded the main PVE server without problems and reboot it.
When the Server startup, I realized that one of my vms was stopped I tried start it manually but when grub loaded the vm stops
I tried restoring backups of my vm but noones works. A few minutes later I realized that other started vms fails... I saw the Syslog and I get I/O Errors in my Disks, in my nvme disk, in my sata disk and in my RAID........
Bash:
Jul 24 14:42:56 pve kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 24 14:42:56 pve kernel: ata3.00: failed command: WRITE DMA EXT
Jul 24 14:42:56 pve kernel: ata3.00: cmd 35/00:f8:30:fd:fc/00:00:34:00:00/e0 tag 0 dma 126976 out
res 50/00:00:80:20:27/00:04:0e:00:00/e0 Emask 0x40 (internal error)
Jul 24 14:42:56 pve kernel: ata3.00: status: { DRDY }
Jul 24 14:42:56 pve kernel: ata3.00: configured for UDMA/133
Jul 24 14:42:56 pve kernel: ata3: EH complete
Jul 24 14:49:14 pve kernel: sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jul 24 14:49:14 pve kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : Aborted Command [current]
Jul 24 14:49:14 pve kernel: sd 0:0:0:0: [sda] tag#0 Add. Sense: No additional sense information
Jul 24 14:49:14 pve kernel: sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 04 10 00 00 01 00 00
Jul 24 14:49:14 pve kernel: I/O error, dev sda, sector 266240 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2
Jul 24 14:49:14 pve kernel: md/raid10:md0: sda1: rescheduling sector 0
Jul 24 14:49:14 pve kernel: md/raid10:md0: sda1: redirecting sector 0 to another mirror
Jul 24 14:51:37 pve pvedaemon[28168]: <root@pam> successful auth for user 'root@pam'I turned On my second server and tried to restore vm backup and get I/O error restoing in my nvme...
Bash:
restore vma archive: zstd -q -d -c /mnt/pve/SynologyProxmox/dump/vzdump-qemu-111-2026_07_24-13_15_23.vma.zst | vma extract -v -r /var/tmp/vzdumptmp2263.fifo - /var/tmp/vzdumptmp2263
CFG: size: 833 name: qemu-server.conf
DEV: dev_id=1 size: 18253611008 devname: drive-scsi0
DEV: dev_id=2 size: 21474836480 devname: drive-scsi1
DEV: dev_id=3 size: 10737418240 devname: drive-scsi2
DEV: dev_id=4 size: 10737418240 devname: drive-scsi3
DEV: dev_id=5 size: 10737418240 devname: drive-scsi4
CTIME: Fri Jul 24 13:15:25 2026
Logical volume "vm-102-disk-0" created.
Logical volume nvme/vm-102-disk-0 changed.
new volume ID is 'nvme:vm-102-disk-0'
Logical volume "vm-102-disk-1" created.
Logical volume nvme/vm-102-disk-1 changed.
new volume ID is 'nvme:vm-102-disk-1'
Logical volume "vm-102-disk-2" created.
Logical volume nvme/vm-102-disk-2 changed.
new volume ID is 'nvme:vm-102-disk-2'
Logical volume "vm-102-disk-3" created.
Logical volume nvme/vm-102-disk-3 changed.
new volume ID is 'nvme:vm-102-disk-3'
Logical volume "vm-102-disk-4" created.
Logical volume nvme/vm-102-disk-4 changed.
new volume ID is 'nvme:vm-102-disk-4'
map 'drive-scsi0' to '/dev/nvme/vm-102-disk-0' (write zeros = 0)
map 'drive-scsi1' to '/dev/nvme/vm-102-disk-1' (write zeros = 0)
map 'drive-scsi2' to '/dev/nvme/vm-102-disk-2' (write zeros = 0)
map 'drive-scsi3' to '/dev/nvme/vm-102-disk-3' (write zeros = 0)
map 'drive-scsi4' to '/dev/nvme/vm-102-disk-4' (write zeros = 0)
progress 1% (read 719454208 bytes, duration 1 sec)
progress 2% (read 1438842880 bytes, duration 1 sec)
progress 3% (read 2158231552 bytes, duration 1 sec)
progress 4% (read 2877685760 bytes, duration 1 sec)
progress 5% (read 3597074432 bytes, duration 1 sec)
progress 6% (read 4316463104 bytes, duration 1 sec)
progress 7% (read 5035851776 bytes, duration 1 sec)
progress 8% (read 5755305984 bytes, duration 1 sec)
progress 9% (read 6474694656 bytes, duration 1 sec)
progress 10% (read 7194083328 bytes, duration 1 sec)
progress 11% (read 7913537536 bytes, duration 1 sec)
progress 12% (read 8632926208 bytes, duration 2 sec)
progress 13% (read 9352314880 bytes, duration 2 sec)
progress 14% (read 10071703552 bytes, duration 2 sec)
progress 15% (read 10791157760 bytes, duration 2 sec)
progress 16% (read 11510546432 bytes, duration 4 sec)
progress 17% (read 12229935104 bytes, duration 6 sec)
progress 18% (read 12949389312 bytes, duration 10 sec)
unable to cleanup 'nvme:vm-102-disk-4' - no such logical volume nvme/nvme
unable to cleanup 'nvme:vm-102-disk-3' - no such logical volume nvme/nvme
unable to cleanup 'nvme:vm-102-disk-2' - no such logical volume nvme/nvme
unable to cleanup 'nvme:vm-102-disk-0' - no such logical volume nvme/nvme
unable to cleanup 'nvme:vm-102-disk-1' - no such logical volume nvme/nvme
no lock found trying to remove 'create' lock
error before or during data restore, some or all disks were not completely restored. VM 102 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && zstd -q -d -c /mnt/pve/SynologyProxmox/dump/vzdump-qemu-111-2026_07_24-13_15_23.vma.zst | vma extract -v -r /var/tmp/vzdumptmp2263.fifo - /var/tmp/vzdumptmp2263' failed: interrupted by signal
Bash:
restore vma archive: zstd -q -d -c /mnt/pve/SynologyProxmox/dump/vzdump-qemu-300-2026_07_24-12_33_18.vma.zst | vma extract -v -r /var/tmp/vzdumptmp11343.fifo - /var/tmp/vzdumptmp11343
CFG: size: 830 name: qemu-server.conf
DEV: dev_id=1 size: 19327352832 devname: drive-virtio0
DEV: dev_id=2 size: 10737418240 devname: drive-virtio1
CTIME: Fri Jul 24 12:33:18 2026
Logical volume "vm-102-disk-0" created.
Logical volume pve/vm-102-disk-0 changed.
new volume ID is 'local-lvm:vm-102-disk-0'
Error writing device /dev/sdb3 at 4096 length 512.
Failed to write mda header to /dev/sdb3.
Logical volume "vm-102-disk-0" successfully removed.
temporary volume 'local-lvm:vm-102-disk-0' successfully removed
no lock found trying to remove 'create' lock
error before or during data restore, some or all disks were not completely restored. VM 102 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && zstd -q -d -c /mnt/pve/SynologyProxmox/dump/vzdump-qemu-300-2026_07_24-12_33_18.vma.zst | vma extract -v -r /var/tmp/vzdumptmp11343.fifo - /var/tmp/vzdumptmp11343' failed: lvcreate 'pve/vm-102-disk-1' error: Failed to write metadata area headerAnyone had I/O problems with 9.2.5?
Can Somebody help me?
