Recent content by SysAx

  1. S

    systemctl status degraded, apparmor.service fails, in fresh Ubuntu 18.04 container

    Thanks Fireon, it works for me on Ubuntu 16.04. Regards, Christian
  2. S

    systemctl status degraded, apparmor.service fails, in fresh Ubuntu 18.04 container

    I have the same problem on Ubuntu 16.04 containers after upgrading from proxmox-ve: 5.2-2 (running kernel: 4.15.17-3-pve) to proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve). These containers worked before upgrade and when I move a container on an old node proxmox-ve: 5.2-2, apparmor start...
  3. S

    ZFS thin

    Perfect, it's noted. Best regards, Christian
  4. S

    ZFS thin

    Hi, I have a Proxmox server with a bunch of local disks (10 + SSD for ZIL and L2ARC) mounted in ZFS Raidz2 for the VMs. When I have mounted the storage I forgot to enable the Thin Provision. I have many VMs running on this storage and I want to know if it's possible to enable now without...
  5. S

    Move nodes between two clusters

    Thanks for your replies. I will follow Wolfgang's solution and upgrade the old cluster. Best regards, Christian
  6. S

    Move nodes between two clusters

    Hi, I have two clusters: old_cluster Promox 4.4 with 4 nodes new_cluster Proxmox 5.2 with 1 node I want to migrate all nodes in new_cluster and I know how to do that: backup all VMs of a node remove node from old_cluster upgrade node to Proxmox 5.2 add node to new_cluster I just have a...
  7. S

    What is the Right Way™ to backup to FreeNAS (preferably iSCSI)?

    I am using NFS with FreeNAS for the backup schedule and it works well. I think your problem is related to the reverse DNS lookup done by NFS. Found on a forum: During the mount process, NFS apparently does a reverse DNS lookup to see if the address is valid. You have to add information about...
  8. S

    Conversion LVM to LVM thin

    Hi, I have a cluster Promxox 4.2 with 4 nodes. One of this nodes is installed under ZFS local storage and the others under LVM default storage. The snaphot backup mode are working well with ZFS but it is not possible with LVM. On another independant host (not a part of the cluster), i tried...
  9. S

    Shared storage and dedicated NIC

    pvecm delnode NODENAME worked. Everything seems to be fine now. Might've missed something the first time. I'm almost sure I did this command....or perhaps I forgot with all the other problems. Thanks again. Christian
  10. S

    Shared storage and dedicated NIC

    I will put the NFS storage on the same card than the VMs (not with corosync) to avoid problems in the future. I restarted pve-cluster/pveproxy, but unfortunately, the node is always showned in the Proxmox web console. It seems that it's not completely deleted from the cluster and I can see it...
  11. S

    Shared storage and dedicated NIC

    Hi, I have a 3 nodes cluster with Proxmox 4.2. Each network card (eth0) of the hosts is in a dedicated VLAN used to sync the cluster. I also have a shared storage through NFS on a FreeNAS for the Promox backup on the same card and VLAN. VMs are on other cards and other VLANs. I have a...

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!