Recent content by omueller

  1. O

    Additional confirmation: guest disk EIO / MariaDB InnoDB failures with Proxmox 7.x host kernel, mitigated by booting 6.17.13-13-pve

    Thanks a lot for your updates @fiona and @uzumo, I will test this a bit later this summer. Kind regards, Olivier
  2. O

    Additional confirmation: guest disk EIO / MariaDB InnoDB failures with Proxmox 7.x host kernel, mitigated by booting 6.17.13-13-pve

    Hi @fiona, thanks for your reply ! For the LUKS setup, it is a simple setup where a encryption is mounted manually on boot, and RAW or QCOW2 disk volumes are located there. cryptsetup open /dev/mapper/pve-data volume1 mount /dev/mapper/volume1 /volume1/ VM config is pretty standard, but...
  3. O

    Additional confirmation: guest disk EIO / MariaDB InnoDB failures with Proxmox 7.x host kernel, mitigated by booting 6.17.13-13-pve

    A quick confirmation that booting to Linux host 6.17.13-14-pve #1 SMP PREEMPT_DYNAMIC PMX 6.17.13-14 (2026-06-23T12:24Z) x86_64 GNU/Linux apparently fixes the issue for now. (manual kernel selection in Grub on boot). I would still be very interested to know how this could be fixed for...
  4. O

    Additional confirmation: guest disk EIO / MariaDB InnoDB failures with Proxmox 7.x host kernel, mitigated by booting 6.17.13-13-pve

    Hi, Just a +1 from my side, forum post discovered thanks the error messages. Latest no-subscription PVE 9.2.3 with kernel, 7.0.12-1-pve, single node mode, data on an encrypted LUKS partition, VM = latest Ubuntu LTS 24.04.4, mariadb (10.11.14-0ubuntu0.24.04.1) unable to start with similar...
  5. O

    hardware compatibility - HP server & SAN

    Hi Francesco, Just a quick question a few months later : is your solution based on Gen8 servers running fine, or have you chosen another concept ? I would just like to make sure the compatibility with a server like the HP ProLiant ML350p Gen8, 1P E5-2630 (470065-661) is ok. Thanks in...