Recent content by templar

  1. T

    [SOLVED] local-lvm became inactive after joining a cluster with different disk structure (no such logical volume pve/data)

    Yes, you are right. I have overseen, it wasn't "local-lvm", but "local-zfs". I tested same install in VM and found it out. Now, I (re)added ZFS "rpool/data" in the "Datacenter > Storage" and can use it again. So, case is solved :)
  2. T

    [SOLVED] local-lvm became inactive after joining a cluster with different disk structure (no such logical volume pve/data)

    I did, thanks. Now it exists only on older nodes. How to recreate it now on the new node? Both GUI and pvesm add ask for Volume Group, which I supposedly, don't have on a node with single ZFS formatted disk.
  3. T

    [SOLVED] local-lvm became inactive after joining a cluster with different disk structure (no such logical volume pve/data)

    I had a cluster with classical disk roles: one for Proxmox OS, another for VMs. It worked. Then I wanted to add a simple small node with single disk for DNS and Ngynx. I've installed Proxmox there, choosing to format disk as ZFS. It was installed and created "local" and "local-lvm" storage. Then...
  4. T

    V2V, Zeit NICHT aktualisieren

    Über args Zeile: args: -rtc base=2021-01-01,clock=vm https://pve.proxmox.com/wiki/Manual:_qm.conf

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!