Recent content by Bubbagump210

Any future Googlers, I have no idea the issue but updated kernel 6.5.13-3 works fine.

Those modules are already blacklisted (and have been for ages) along with ‘options nouveau modeset=0’. I would expect 6.2 or 5.15 to have failed ages ago had these modules been loaded along with the Nvidia driver. Also I’m using systemd-boot so the grub commands wouldn’t apply.

For what it's worth I installed pve-kernel-6.2 and kernel 6.2.16-20 works perfectly well.

I just updated a Dell T340 from PVE7 to 8. I went through all the pve7to8 --full checks and simply followed the documented procedure. I also installed systemd-boot per the docs as I am indeed running UEFI on ZFS. I can still boot into 5.15.143-1. pve7to8 --full still shows as clean with the...

Sigh, I figured it out. I am using a genericcloud image and there are no USB drivers included. I installed a different linux-image package and the world was happy.

I'm almost certain either syntax will work. Assuming the original disk is not already in a mirror, the command assumes you are adding the new disk to the data set as a mirror. Regardless, future Googlers, if my syntax doesn't work, try crc-error-79's.

I am trying to create a VM to run NUT. On the physical machine I also have a USB Bluetooth adapter I pass-through to another VM and this works perfectly. For whatever reason the UPS is not recognized in the VM. I have rebooted the entire host and no luck. NUT server acpi: 1 agent...

When creating a sync job, is there a way to *except* items from being replicated? I have a replica where I want to replicate everything except one host. The docs make it sound like group-filter is an include only filter but I'm hoping there is an "everything except" filter possibility.

No.

Is there a Bugzilla on this?

I figured my issue out. Somehow a snapshot related to the dataset was mounted for reasons I can’t explain.

I figured my issue out. Somehow a snapshot related to the dataset was mounted for reasons I can’t explain. Thanks for the hint.

My issue started after a failed backup snapshot. There is nothing else mounted in the path. Could a snapshot create a mount like this? Which doesn’t make sense as using lxc.mount.entry (as opposed to mpX syntax) should not snap that dataset.

Interestingly enough, if I create a new ZFS data set and migrate the data to it, it mounts fine (my current quick and dirty fix). What could possibly "taint" a data set to make it cause LXC to fail? Config for what its worth: arch: amd64 cores: 2 features: nesting=1 hostname: Downloader...

I woke up today with an odd cascade of events. First, one node of a cluster showed gray question marks for all objects. Interestingly enough the node showing all gray was also the one whose web console I was connected to. I rebooted the node and this issue resolved itself. Next, one LXC...