Recent content by hosting

  1. H

    Proxmox VE 8.1 auf Netapp H300S/H300E

    Ich hab es geschafft. Supermicro haben mir v14.31.xx für AOC-MH25G-M2S2T geschickt, ich habe sie hier hochgeladen https://file.io/HqVbkxW6Pnp3 Nach dem Update alles wieder funktioniert. PS> ich habe auch die letzte mst software von nvidia verwendet...
  2. H

    [TUTORIAL] MD3200SAS / Proxmox + OCFS2 (Not supported by the Proxmox Team)

    Did you manage to add members to the cluster online?
  3. H

    Proxmox VE 8.1 auf Netapp H300S/H300E

    Ich habe genau gleiches Problem. 3 Karte mit FW 14.25.xxx und 14.23.xxx- funktioniert, 2 Karte mit 14.21.xxx - nein.
  4. H

    Proxmox VE 8.1 auf Netapp H300S/H300E

    haben Sie es geschafft?
  5. H

    Sudden filesystem errors

    Faced this today also when tried to run docker under ubuntu20. On the first run it works, after reboot VM has ext4_dirblock_csum_verify:377: inode #278015: comm containerd: No space for directory leaf checksum Using OCSF2 cluster over ISCSI. Rolled back all hosts to stable kernel...
  6. H

    Centos 7 crashes on pve 5.4.78-1

    Issue is still there on 5.4.106-1, after first setup of vm with Centos 7 on reboot: [ 29.762903] XFS (sda1): First 128 bytes of corrupted metadata buffer: [ 29.764044] ffff9f36f2b0b000: 00 00 00 00 00 00 00 00 88 d9 1a 00 00 00 00 00 ................ [ 29.765676] ffff9f36f2b0b010: 07 00...
  7. H

    Centos 7 crashes on pve 5.4.78-1

    Same thing on 5.4.78-2, during deployment of cloud image: [ 129.207689] cloud-init[1086]: Cleanup : glib2-2.56.1-7.el7.x86_64 76/78 [ 129.238270] cloud-init[1086]: Cleanup : freetype-2.8-14.el7.x86_64 77/78 [ 148.053169]...
  8. H

    Centos 7 crashes on pve 5.4.78-1

    Hello, We have 4 nodes running in cluster. 2 are with 5.4.78-1, 2 with 5.4.73-1. Centos 7 (xfs) is always crashing on the first reboot on 5.4.78-1 while is absolutely fine on 5.4.73-1. Not storage related, all nodes are connected to same storage, we are running OCFS2 on top of ISCSI on 10...
  9. H

    permission denied - invalid PVE ticket (401)

    Got exactly same issue on 1 out of 4 nodes now. Definitely a bug. proxmox-ve: 6.2-2 (running kernel: 5.4.65-1-pve) pve-manager: 6.2-15 (running version: 6.2-15/48bd51b6) pve-kernel-5.4: 6.2-7 pve-kernel-helper: 6.2-7 pve-kernel-5.3: 6.1-6 pve-kernel-5.4.65-1-pve: 5.4.65-1...