Search results

  1. J

    Proxmox shutdown last night, again.

    So basically what you are stating is that the errors had to do with your storage. Did you use ZFS ? Did you have LXC and VMs ?
  2. J

    Proxmox restarts randomly

    No, it is not. I'm planning to setup now a cluster with HA as I'm fed up seeing everything go down without any reason.
  3. J

    Proxmox shutdown last night, again.

    @thusband were you able to sort this out in the end ?
  4. J

    Proxmox restarts randomly

    If I look in the syslogs, I see only the following entries just before it reboots Nov 09 05:17:01 pve CRON[1415670]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Nov 09 05:17:01 pve CRON[1415671]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 09 05:17:01...
  5. J

    Proxmox restarts randomly

    I restarted a while back and didn't see the behaviour anymore till a few days ago. I see in the syslog --reboot-- but can't figure out what it causes.
  6. J

    PBS Storage / Disks No Disks unused? I have disks 2T unused

    I have a similar problem. Not able to use the disks. Here is Any idea how to use the disks correctly ?
  7. J

    [SOLVED] Backup fails with exit code 255

    I'm having the same issue. I wonder if you could be a bit more specific as to what you exactly done so I can replicate. Thank you so much, Jens
  8. J

    Problems with the backup of my LXC - exit code 255

    Dear all, I'm really struggling with the backup of my LXC. Not sure what is the problem and how to sort it. INFO: starting new backup job: vzdump 2000 --storage PBS --mode stop --notes-template '{{guestname}}' --node pve --remove 0 INFO: Starting Backup of VM 2000 (lxc) INFO: Backup started at...
  9. J

    LXC Backup to PBS stopped working

    I've been backing up my LXCs/VMs with PBS for the last month or so without problems. Today, however, at the scheduled time, my backups failed. For my VM, I was able to do a manual backup, but for LXC I wasn't. Here is what I got : INFO: starting new backup job: vzdump 2000 --remove 0 --node...
  10. J

    GPT PMBR size mismatch will be corrected by write.

    It looks like the message now disappeared.
  11. J

    GPT PMBR size mismatch will be corrected by write.

    Dear all, I'm running PVE8 with a ZFS pool (raidz1-0). One of the drives when running fdisk -l show GPT PMBR size mismatch (4294967294 != 15628053166) will be corrected by write.. Not sure if I should be worried and how I potentially can fix it.
  12. J

    ERROR: Backup of VM failed - command 'rsync .... ' failed: exit code 23

    @glitchwitch this method worked also for me ! Thank you so much. For future reference, the last step is effectively uncommenting and adjusting the following line tmpdir: /mnt/vztmp in /etc/vzdump.conf
  13. J

    ERROR: Backup of VM failed - command 'rsync .... ' failed: exit code 23

    Dear all, I'm trying to do a backup of my LXC and get the following error message : ERROR: Backup of VM 2000 failed - command 'rsync --stats -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*'...
  14. J

    Error installing Proxmox 7.1 on my system "bootloader setup errors: unable to init ESP and install proxmox-boot loader on '/dev/sdc2'"

    Hello after, disabling most of the EFI options, plus cleaning the nvme drives, I got it finally to work.
  15. J

    Error installing Proxmox 7.1 on my system "bootloader setup errors: unable to init ESP and install proxmox-boot loader on '/dev/sdc2'"

    I'm facing the same issue. I tried to install PVE 6.4 but I'm getting another error message : unable to bind the codec. Any other ideas ?
  16. J

    Proxmox restarts randomly

    Hello, I have the same issue as the folks listed above, with one exception that the reboot brings the server down. So the only solution is to manually reboot. My specs are : CPU(s) 16 x 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz (1 Socket) with 128G Memory and 8 TB SSD in RAID 5 Kernel...
  17. J

    SYSTEM DOWN : Proxmox constantly crashes after upgrade to version 5.15.60-1

    I made a change to the BIOS - CPU C States to disabled and now the system is up again, but still would like to know what is causing this and if I should be concerned for the future.
  18. J

    SYSTEM DOWN : Proxmox constantly crashes after upgrade to version 5.15.60-1

    in journalctl, I found the following errors : - acpi PNP0C14:01: duplicate WMI GUID - MMIO Stale Data CPU bug present and SMT on, data leak possible - ENERGY_PERF_BIAS: Set to 'nomal', was 'performance' - device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will...
  19. J

    SYSTEM DOWN : Proxmox constantly crashes after upgrade to version 5.15.60-1

    Hello, I need your help, I don't know where to start. My system crashed and can't be recovered. The only way, I currently, can access it is via the recovery mode. Even if I change the kernel in the GRUB to a lower version, I'm experiencing the same problem. Observation : moving from the GRUB...
  20. J

    Errors in my ZFS Pool

    Is it a fair assumption if I remove 104, the error will disappear ?