Search results

I recently ran into some odd issues with clustering. I migrated over a disk PRIOR to actually making the backend storage available to the new node. This caused some wonky things to happen including some disks being erased from their original location. I had disks in the original storage...

PVE 6.4-6 on both nodes I'm trying to set up ZFS over iSCSI to share disks in my cluster. I have followed the instructions from the official docs. I confirmed that I can log in to each node with ssh -i /etc/pve/priv/zfs/192.168.1.1_id_rsa root@192.168.1.1 replacing the IP with each node's...

It's because I had "protection" enabled in the options...

The only relevent conversation I could find was TASK ERROR: unable to restore VM 107 - - protection mode enabled but I don't speak German

PVE 6.4-5 I am trying to restore a VM from backups but get the following error error before or during data restore, some or all disks were not completely restored. VM 900 state is NOT cleaned up. TASK ERROR: unable to restore VM 900 - - protection mode enabled

I went to look for the service file in /etc/systemd/system but it's not in there, can you point me in the right direction? jon@TracheServ:~$ ls /etc/systemd/system ceph.target.wants smartd.service dbus-org.freedesktop.timesync1.service sockets.target.wants...

I'm fairly certain I used a VE 6.x installer, but what would be the right way to confirm this?

I recently updated to PVE 6.3-4 which brought along with it OpenZFS. I now need to upgrade my ZFS pools, but I want to check that there are no contraindications for ZFS root configs. pool: Nextcloud.Storage state: ONLINE status: Some supported features are not enabled on the pool. The pool...

I upgraded today just to see if that would make a difference. New (journalctl -b) log attached! https://pastebin.com/naJuaBcG

No. I see that as an option now under upgrades but it also shows no previous version installed. Looks like it's version 0.8.5

As requested: https://pastebin.com/hkEX4xnt https://pastebin.com/Gc0UCBxv https://pastebin.com/VA1cE0SZ https://pastebin.com/Bf4uEipa https://pastebin.com/yhmUtnkN

I failed to mention another detail - I had another ZFS issue recur after this latest upgrade. I have some directories mounted at a ZFS share (Nextcloud.Storage) with is_mountpoint 1 declared in the storage. I had worked with Aaron from your team prior when I first set up these directories...

I would love to dedicate some hardware to pfsense! Unfortunately, that's not in the budget currently. It hasn't been an issue at all until this last upgrade luckily.

I get the error "Failed to start Import ZFS pool new_ssd", but once Proxmox is up everything is available as expected. This is the only ZFS pool that throws errors. The error instructs me to check systemctl with the following command. root@TracheServ:~# systemctl status...

To be clear, this was fixed with a reboot so this is just for the sake of documentation. I have virtualized pfsense and Open vSwitch on the proxmox host for L3 switching of my VMs. After upgrade, proxmox host nor any of my VMs could resolve any DNS requests regardless if they were on a tagged...

That worked, thanks! So should I go and remove my mkdir flags from my other directories as well and just leave is_mountpoint? INFO: starting new backup job: vzdump 400 --node TracheServ --mode snapshot --remove 0 --storage NC.VM.Backups.dir --compress zstd INFO: Starting Backup of VM 400 (qemu)...

I was under the impression that the is_mountpoint 1 and mkdir 0 are necessary for making a directory at a zfspool. Here's what Aaron from your team told me in a separate discussion: https://forum.proxmox.com/threads/what-is-suddenly-taking-up-so-much-space-on-local.78967/page-2#post-353015 "If...

PVE 6.3-3 I created zfspool "NC.VM.Backups.zfspool" under the parent zfspool "Nextcloud.Storage". I then tried to mount a directory at that site, but cannot select it as a backup target. INFO: starting new backup job: vzdump 69420 --remove 0 --mode snapshot --node TracheServ --compress zstd...

Thanks for the reply Aaron, I migrated disk from zfspool to the corresponding directory I have mounted there and converted to qcow2. Problem solved.

I'm running PVE 6.3-3 and am trying to get snapshots as branches are per the documention: https://pve.proxmox.com/wiki/File:Screen-vm-snapshots.png I can't seem to get anything besides sequential snapshots, what am I doing wrong here? This disk and the snapshots are saved to a zfspool managed...