Recent content by binarian

Gotcha. I'm using the systemd option. I'll assume it's safe to ignore!

Thanks a lot for this! Those instructions worked perfectly for the first disk. However: I notice that the instructions describe how to handle partition 3 (the data), and partition 2 (the EFI stuff). There's no mention of partition 1. Does anything have to be done there? ALL of my original...

All, I am very soon doing a zfs drive replacement on my proxmox server. I have a question about what paths to use. The physical drive is /dev/sdv. However, zpool status shows that the member drives are using the /dev/disk/by-id nomenclature, and specifically are using partition 3 (so zpool...

Ah, OK. That I didn't know. I'll stick with the bridge then (which honestly, I like more anyway). CPU/memory won't be a problem...at least it darned well better not be. Latest-gen Epyc cpu which has 8-channel memory. Thank you!

Simple question, but perhaps a not-so-simple response. I am creating a new proxmox rig that will support 40GBE networking. I've read that OVS is better for >10GBE scenarios, but I've also read that OVS can tend to be unstable. Everything I've read is from at least 2 years ago. I've been...

It looks like that's what I'll have to do. As for encryption, this machine is already an abomination (both a raid controller and an HBA, because apparently an r710 won't boot from an unsupported HBA). I'm not in any high-security-risk scenario; I just want encryption so that in the event of a...

Baaahhhh I was afraid of that. That requires knowing in advance what the ordering and IDs are supposed to be. Still, good to know there's an easy way to start them in general, thanks. Anyone else have any suggestions?

Hi all, I have a question about the Start At Boot functionality. I have a fully-functional proxmox 6.1-11 machine that, until this morning, was running everything off of an unencrypted zfs dataset. As of this morning, I have moved everything over to an encrypted zfs dataset, and things...

Did you remember to restart the syslog-ng service? And also to change the ip address to whatever one is showing up in your logs?

@nowoe already touched on this: it's not a bug, it's expected, if unfortunate behavior. Fortunately, there's an easy fix on the FreeNAS side that doesn't involve crippling either FreeNAS or Proxmox. Taken from an ixsystems thread (can't link since I'm a new user): I added the following at the...