Search results

This seems to work

rsync from old proxmox to new one I created a subvolume and transfered the data inside the old subvolume to the new one the zfs-pool and dataset were created during installation.

we had to transfer the subvolume from rpool/data and the config file to a new proxmox on a new zfs pool

the disk has been transfered. apparently we are facing issues with the disks where acl are set to "enable". the container doesn't start if they are not set to default. I did it and the container started but it messes up everything with samba. the AD not working, people can't access their...

Hi everyone, After a crash I had to recover some container directly from the ZFS pool. I created a new proxmox from scratch, moved the subvolumes into the new zfs pool and created the config file. Some of the containers started with no issues, but the one who has the acl option set to 1 are not...

Hi everybody. We are having trouble to start containers that we imported from another node. They were not moved from backup/restore process, we transfered the disk and the config file from old to new server. here is the output when we try to mount the container: root@proxmox1:~# pct mount 112...

Thanks for reply, I know about the MAC change through GUI My issue is that everytime I reboot those containers I loose the conectivity. The only way to have it back after reboot is to manually delete the MAC through the GUI to get a new one otherwise I get a "network unreachable"

Hi everybody, I recently migrated a few containers to a new proxmox infrastructure. Some of those containers were configured with a wan ip and a static MAC given by my isp, the other were on a LAN behind a pfsense. They now are like the others configured on a LAN behind a pfsense. Since the...

Just to clarify for those who read this post: Read pricing conditions, they are much more advantageous than what I stated previously. I was to stressed to read correctly... Thanks to proxmox staff

Gosh ! You're my hero ! Cost me 467€ for paid support, 1 ticket used out of 3 for nothing. and a subscription valid on a server that will be out of prod by end of the week... Thank to you anyway

and nope, it doesnt get mounted: root@overlaps:~# zfs get mounted NAME PROPERTY VALUE SOURCE zfs-pool mounted yes - zfs-pool/subvol-101-disk-1 mounted yes - zfs-pool/subvol-102-disk-0 mounted yes -...

root@overlaps:~# zfs get all zfs-pool/subvol-111-disk-0 NAME PROPERTY VALUE SOURCE zfs-pool/subvol-111-disk-0 type filesystem - zfs-pool/subvol-111-disk-0 creation Sun Jan 13 13:13 2019...

Hi everybody, I did a "umount subvol-101-disk-0" and lost evrything in the container exscept "dev" folder. now I am unable to mount the container back, even after rebooting proxmox the container remains empty and down. Any suggestions to recover from that ? Thanks