Recent content by danielb

  1. WARNING! Upgrade to 7 network problem, do not upgrade!!!

    Before ranting, please take a closer look at the license under which PVE is released (and look for the warranties). Keep in mind a lot (most ?) users were able to handle the upgrade with no issue (including myself, on several servers). Major upgrades of any system requires basic administration...
  2. VM Backup fails with "ERROR: Backup of VM 100 failed - job failed with err -5 - Input/output error"

    Hard to tell. Could be a failing disk on either the source or the destination. You should check the system logs
  3. virtnbdbackup - backup utility for libvirt, using the latest changed block tracking features.

    You can install PBS on PVE already, it's not required to install it on a separate host
  4. May have ruined data of one of my nodes...

    You should delete the actual RAID configuration (delete the VD again), then re-create the VD exactly as it was previously (same set of physical drives, in the same order, with the same chunk size etc. Everything must be exactly the same). Be careful not to initialize the VD when recreating it...
  5. May have ruined data of one of my nodes...

    Depends on your RAID card if you'll be able to expand the RAID6 array with more PD. But at least, you might be able to get your data available, back them up, wipe and recreate the array on all the disks, and restore
  6. May have ruined data of one of my nodes...

    You should recreate the RAID array with the exact configuration as it was previously (same PD, same order, same chunk size etc.)
  7. huge dirty-bitmap after sunday

    This is most likely because you have a weekly fstrim job running, which will mark all the trimmed sectors as dirty. It shouldn't affect backup speed that much as all those "dirty" sectors will not really be red from disk
  8. Fencing and "isolation response"

    In the doc, but also already tried ;-)
  9. Fencing and "isolation response"

    Proxmox will self-fence the isolated host : host1 will be forcibly rebooted, so VM100 is for sure not running anymore. While host1 is rebooting, VM100 will be relocated to either host2 or host3
  10. Very frustrated with Proxmox

    You can also check/replace the SATA cable. A bad one could also explain this kind of errors. In any case, it's most likely a hardware problem.
  11. Very frustrated with Proxmox

    Your HDD or SSD /dev/sda is failing, you should replace it
  12. VMs freezing and unreachable when backup server is slow

    That'd requier a lot of spare space, cpu and memory resources, and overall doesn't look like the proper way to handle the problem
  13. LXC Slow update (CentOS 7)

    Lastlog can't be rotated, and it's a binary file. If it's removed, it'll be recreated with the same size (and still sparse). IMHO the only reasonable thing to do is to exclude it from backups
  14. LXC Slow update (CentOS 7)

    You can do it creating /var/log/.pxarexclude containing a single line : lastlog (haven't tried, just red the doc)

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!