Recent content by proxbear

Well, that's relative: the OP wants to rollback => the most interesting thing for him is to rollback. When he is using ZFS snapshotting, it's an easy thing. When not, he can start doing it and rollback later.

I do ZFS snapshoting every 5 minutes and it saved my butt quite a few times already with Proxmox ;-). In worst case it's even possible to attach your boot-disk(s) to another comp and rollback everything there.

Much appreciated, merci vielmal und Grüezzi us de Schwiz :D!

Nope, I/O is ZERO in all the CTs.

I have to be more precise: - My CTs are more protected, because when stealing the host physically, the CTs are not accessible anymore, as they're living in an enc ZFS volume, which has to be manually mounted after each host-reboot - The root can only then read my CT, when I mounted the enc ZFS...

Thank you! Hm, the issue here is, that Proxmox is not run on a secured ZFS (booting from enc ZFS is a big ugly hack-around) and so I try to avoid host-mounted filesystems, as taking the machine physically away means all the secured stuff (scripts, mounts..) is readable from outside. That's why...

When I click the "Summary" in the web-admin UI at a container, I see no DiskIO, i.e. both the read/write == 0. The filesystem is ZFS, both for the VM and for the mount-point, being the target for the heavy IO work. The CT is running a quite exhausting task for both the CPU and IO and normally...

I'm running a CT which mounts a CIFS and a SSHFS mounts (not mounting-point, but mounted inside the privileged CT). When the nightly backup runs (mode: snapshot) it stalls; in the morning it says "Config locked (snapshot)" and I can't SSH into the box. Question-1: Is the problem because of...

Ok, I'll post everything after the next reboot - but this can take up to 1 week, as currently a lot of backup tasks are initially running. The symptoms: the PVE even doesn't realize something went wrong: sometimes it even creates a corrupted backup as "OK" (like being 20MB big, instead of...

Of course I have no autostart ;-). I'm attaching the log-file, thank you!

I've solved it at the end myself: the error can be seen when executing the post-installation script manually, like this: /var/lib/dpkg/info/samba-common-bin.postinst --configure And in my case it was a misconfiguration in /etc/samba/smb.conf :)

Ok, so I've tested it - and it sucked somehow :(.. It had a problem with "samba-common-bin" package, what I've tried to ignore.. I've added the no-subscription pve repo to the sources, made apt update/upgrade, rebooted: now I can't connect CIFS from the UI. Remembering the "samba-common-bin"...

I'm running my VMs & CTs from image files stored on an encrypted ZFS pool - it's the same pool, which I boot from; the boot partition is not encrypted. There is a separate data-set called "encrypted" for this. Everything works nicely, after reboot I just run a zfs-mounting script, which asks...

Hello, I've a similar problem: I was running successfully FreeNAS in a VM, with LSI-3008 passthrough, everything ok. Now I want to get rid off the FreeNAS and have the Proxmox do the ZFS/CIFS stuff - but removing the passhtrough of LSI-3008 and stopping the VM did not reveal the 8 SATA disks to...

The issue is, that OMV can not use the mount share-points when I understand it correctly: I've tried it a bit and it asked for /dev raw devices, not the file-system. Pretty strange I think = unusable. I'm playing with LXC TurnKey-FileServer (from the templates-storage); the only nasty thing was...