Search results

This procedure worked. I did have to install systemd-boot to init the efi partition.

I have a 2 way SATADOM mirror today in ZFS that I use as my boot devices. I kept /var/log on them, and they've now worn out after a few years. Since deploying this system I've added 3x 1TB Intel SSDs. Right now all they're being used for is a single 100G partition in a 3 way mirror as the...

I was able to resolve this. It was a problem with the cache file. For auto-unlock at boot to work, the cache file needs to contain the dataset. For some reason on system B the cache file didn't have the dataset (or was it the pools? not sure). I followed a procedure posted here to rebuild the...

That didn't work unfortunately. The service attempts to load the keys between zfs import and zfs mount. IDK why, but for some reason the system is not aware of sata1/encrypted prior to mounting the known datasets, but after the system boots the dataset it present and I can load the keys no...

I'm trying to implement the following systemd service to auto load the key on boot. cat << 'EOF' > /etc/systemd/system/zfs-load-key@.service [Unit] Description=Load ZFS keys DefaultDependencies=no Before=zfs-mount.service After=zfs-import.target Requires=zfs-import.target [Service] Type=oneshot...

Interesting, did ifreload -a not work?

That was how I ran my upgrades. The only major version upgrade I've done was from 7 to 8, which I followed the admin guide for. https://pve.proxmox.com/wiki/Upgrade_from_7_to_8

I tried running zpool iostat and found that I couldn't run most options with it. I went and asked the ZFS community about this, and they pointed out that I was running different userland and kernel versions of ZFS and that it was the likely reason for the issue. I've followed all of the admin...

Just moments later I managed to resolve this a post i found via page 3 of duckduckgo. I had to add rdns=false to [libdefaults] in /etc/krb5.conf I had an old rDNS mismatch with the hostname of the domain controller, so turning on this switch fixed it. Reverse DNS being configured...

I used this procedure on a host I had built back in 2020 running 6.2 without issue. On My new host running 8.0.3 I'm getting the following error. I haven't been able to find much in the way of searching the web. The DC it's authenticating against is Windows 2016 with a 2016 functional level...

On my first Proxmox deployment I screwed this up, so this time I'm looking for some advice before I move forward with my new host. I'm migrating from an old Proxmox host to a new one. On this old host I'm running Proxmox as the OS with ZFS, and Samba directly on the host. I also have a couple...

I was able to get this to work through the CLI. Is is possible to do this through the GUI?

Marvelous, thank you!

I'm having the exact same issue. Did you ever find a solution to this? https://forum.proxmox.com/threads/linux-vlan-interface-on-host-prevents-guest-traffic-on-same-vlan.124733/

I have a host with a Linux Bond that I use for inband management and guest traffic. I have a Linux VLAN interface as part of the bridge which I use to access the host. All is well with this part of the config and everything works as expected. The trouble starts when I have a guest that I want...

I've had nothing but problems with OVS and RSTP. There are some pretty serious known bugs that haven't been fixed for years. My recommendation would be to avoid OVS entirely if possible and use Linux Bonds instead.

I was able to replicate this specific issue in a completely separate environment on brand new hardware with different NICs, running a very current version of proxmox. It only affects OVSInt ports when RSTP is enabled. root@J4125-01:~# cat /etc/network/interfaces # network interface settings...

I'm still not sure what this bug is exactly, but I was thinking about it the other day and I'm pretty sure whatever the issue was it ended up crashing our entire L2 infrastructure for a whole datacenter a while back. I was running Proxmox with OVS on a VFIO workstation / server at my desk and...

I'm still having the problem. I gave up and kept the host interface / gateway on the native VLAN. Good to know I'm not the only one. I'm doing some rathe esoteric stuff in this environment, it's a lab. Ooooh it's tied to RSTP. That explains why a near identical environment didn't have this...

I mean ARP certain seems to be a factor. There's no ARP entry in OVS before I try pinging out, and after I do there's an ARP entry. That doesn't explain why OVS doesn't seem to be replying to ARP broadcasts. Not following where you're going with NDP