Search results

  1. D

    increase zvol-partition in proxmox backup server

    Nobody else? I'm still stuck, so any idea would be much appreaciated.
  2. D

    increase zvol-partition in proxmox backup server

    Thank you, but unfortunately, export & import didn't change anything.
  3. D

    increase zvol-partition in proxmox backup server

    Hi. I have Proxmox-backup server installed as a VM in Proxmox. I am trying to increase the partition of the pbs. Proxmox Version: 7.2-4/ Proxmox Backup Version: 2.0-4 This is what I've done so far: I have increased the disk in the Proxmox GUI (+500GB). Used "resize2fs" to increase the...
  4. D

    ZFS: recover filesystem

    Thank you for the clarification and the support.
  5. D

    ZFS: recover filesystem

    Just making sure, I understand your comments: The damaged zpool can probably not get recovered. Only chance is to send the damaged images to a specialist. Is there a specific (affordable) service supplier, that you can recommend? Thank you.
  6. D

    ZFS: recover filesystem

    Hi, Thank you for diving into this. This is the command used to roll back the images to the newly created CEPH disk. pv <zfs-block-device> | zstd - --stdout --adapt -z | ssh <ceph-host> dd bs=16M of=/mnt/rbd_backups/<IMAGENAME>.img.zst It seems, we missed some """ - so source and destiny were...
  7. D

    ZFS: recover filesystem

    Am I posting in the wrong forum? Could you point me towards a forum where I might geht help with this?
  8. D

    ZFS: recover filesystem

    When testing the decompression of the images, they were fine. But piping that output to the original server... that's when things went wrong.
  9. D

    ZFS: recover filesystem

    Hi guys, I've a proxmox server with a ZFS Raid 1 pool (2x 18TB WD disks). I inteded to switch to CEPH, so I created an image of the 2 existing vm-disks, and stored the image files on a second proxmox server. Since the image proved to be fine, I destroyed the ZFS and initialized CEPH. Adding...
  10. D

    Server with proxmox crashes. Requesting help troubleshopoting.

    I assume that these daily crashes have to do with too little RAM.
  11. D

    Server with proxmox crashes. Requesting help troubleshopoting.

    Hello, I have an old server running Proxmox that I use solely as diskserver (ceph). So no VM's, and no Containers. It is a HP ProLiant MicroServer - Turion II Neo N54L: CPU(s) 2 x AMD Turion(tm) II Neo N54L Dual-Core Processor (1 Socket), with 8Gb of RAM. During the last couple of days, it has...
  12. D

    increase disk spave local lvm

    Hello iBug, It's a full VM. So the command to use is: qm resize <vmid> <disk> <size> Retreiving the ID: root@proxmox03:~# cat /etc/pve/.vmlist { "version": 135, "ids": { "105": { "node": "proxmox03", "type": "qemu", "version": 84 }, "107": { "node": "proxmox03", "type": "qemu", "version"...
  13. D

    increase disk spave local lvm

    Hi. One of my VM's (OPNsense) is desperate for more diskspace. Could you please guide me through the process? root@proxmox03:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT rbd0 252:0 0 8G 0 disk nvme0n1 259:0 0...
  14. D

    error occured during live-restore: MAX 8 vcpus allowed per VM on this node

    Thank you for you reply. I reduced the CPU core to 1 core, 1 socket. Backup still failed. I also had to install a missing Linux-bridge before I could start the VM. Afterwards, Thank you very much - absolutely new to backing up proxmox ;-) cat /proc/cpuinfo: Linux proxmox02 5.11.22-3-pve #1...
  15. D

    Container friert ein

    Es scheint, als würde der Container ceph nicht leiden können. Ich lasse den Container jetzt auf einer lokalen festplatte laufen, und nun gibt es seit 48 Stunden keine Probleme mehr.
  16. D

    error occured during live-restore: MAX 8 vcpus allowed per VM on this node

    Hello there! I receive a similar error when trying to backup my datacenter: ERROR: Backup of VM 101 failed - MAX 2 vcpus allowed per VM on this node The host itself has 2 x AMD Turion(tm) II Neo N54L Dual-Core Processor (1 Socket) I get this error even though the VM is currently not running...
  17. D

    Container friert ein

    Das Problem besteht auf Proxmox v7.0-11... Ein defekter RAM ist als Ursache eher unwahrscheinlich, weil es auf beiden Servern auftritt.
  18. D

    Node unsauber aus cluster entfernt

    Inzwischen sind die Fragezeichen bei proxmox03 verschwunden. Das GUI ergibt also wieder mehr Sinn. root@proxmox03:~# ceph --version ceph version 15.2.13 (de5fc19f874b2757d3c0977de8b143f6146af132) octopus (stable) root@proxmox03:~# systemctl status corosync ● corosync.service - Corosync Cluster...
  19. D

    Node unsauber aus cluster entfernt

    Hallo, Ich habe ein Cluster bestehend auf 3 nodes gehabt. Nachdem ich 2 der Server ("proxmox02" und "proxmox03") von pve 6.4 auf pve 7 geupdatet habe, wollte ich den Server der noch auf 6.4 lief ("proxmox01") aus dem cluster entfernen, und frisch von USB installieren. Dabei habe ich bei der...
  20. D

    Container friert ein

    Könnte letzteres folgende Einträge im log verursachen? Allerdings hatte ich den container ja auf andere Hardware migriert...und auf beiden servern die gleichen symptome gehabt.

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 yours easily in our online shop.

Buy now!