Search results

  1. T

    “Primary GPT table is corrupt” error on (some) restored containers

    Hello experts :) I just upgraded to a new server and I'm currently restoring containers. Some of them have GPT corruption warnings. Example: Disk /dev/mapper/pve-vm--100--disk--0: 8 GiB, 8589934592 bytes, 16777216 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical)...
  2. T

    martian source from itself

    Hello experts! I'm seeing a lot of martian sources in my pve syslog log which has me rather confused as it seems to be from a host to the same host: IPv4: martian source 192.168.20.102 from 192.168.20.102, on dev eth1 ll header: 00000000: 4e a8 57 59 29 13 e4 11 5b 9b 99 81 08 00 IPv4: martian...
  3. T

    Config locked (backup) problem

    Hello experts! I have a CT that got caught in Config Locked (Backup) which I fixed by unlocking it (hoping it was a fluke) but it still does it. I have no idea why since the storage doesn't seem to be the problem (all other CT/VM run backup without getting locked). I do see an error in the log...
  4. T

    [SOLVED] Adding HDD ends in dead network and "Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw"

    UPDATE for anyone finding this via a search: The solution is in the last post. TLDR; use UUIDs in fstab. For some reason proxmox uses the old /dev/sdx system and it breaks boot. I just tried to add new drives to my Proliant server but it boots up with all network interfaces as DOWN and an error...