I haven’t used TrueNAS but from what I’m reading it has an option to import existing pools. If you have spare SSD I would yank your windows drive out of the system and try installing Proxmox on the spare drive first. There’s a truenas installation script on that community page I linked in my other post, it says to follow this discussion after it runs. That might be a good starting point.

I hope that barracuda was shucked from a Seagate Expansion lol (that’s where I got all of my barracudas).

good bot

Yes, you can. https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#HyperV

Edit: Also yeah you should be able to dual-boot but I wouldn’t recommend it. Linux and Windows bootloaders don’t like to play nice with eachother.

2nd Edit: Added the official PVE Hyper-V migration documentation, but that blog covers it in more detail.

3rd Edit: It looks like there are some important caveats when virtualizing TrueNAS, which I assume you’re familiar with since you have it virtualized already but I wanted to add the TrueNAS virtualization guide just in case. https://www.truenas.com/blog/yes-you-can-virtualize-freenas/

You should be able to migrate most or all of your existing Hyper-V VMs to Proxmox, which would be relatively straight forward. My recommendation would be backing up everything to your TrueNAS (that has the dedicated HBA) then you can wipe your Windows boot drive and install Proxmox. Then you could start by migrating your TrueNAS VM over and passing it’s HBA back to it.

Once you have your NAS working in PVE then you could either migrate/rebuild your other VMs, or look into splitting your services into containers (Proxmox uses LXC natively, but Docker is another option.) There are some great helper scripts to get services spun up quickly so you can minimize downtime.

You didn’t mention how much, if any, experience you have with PVE/Debian and I know from a friend recently switching that some things are a bit more “difficult” than TrueNAS so hit me up if you need anything. The PVE admin documents will be helpful as well.

https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#HyperV

Concerns about the condition may result in anxiety, with sufferers often fearing that the pain is a sign of a more serious condition. Similar anxieties in those who experience the syndrome on a regular basis may manifest as a worry of the syndrome itself happening, with patients feeling scared to take fuller breaths in fear of triggering a spell.

damn anxiety a sunuvabitch

It really depends on how it was originally encded to x264 and what your goals for transcoding are in the first place (save space, playback compatibility, etc etc). there’s a pretty good little post on stackexchange that goes into more detail about the ffmpeg flags.

https://unix.stackexchange.com/a/248711

If you have the skills to setup a Jellyfin server you also have the skills to setup wireguard.

They appear to offer a guided installation for windows users.

uhhh did i? https://github.com/ZoeyVid/NPMplus is the link I meant to post for npmplus. its a fork of npm.

Jeez, so it’s meant to be a literal home media server. Able, but not designed, to be used for sharing.

Primarily for the CrowdSec integration (one less thing to set up manually)

https://www.virtualizationhowto.com/2025/09/nginx-proxy-manager-vs-npmplus-which-one-is-better-for-your-home-lab/

I run pretty much all my stuff through NPMplus. Then I have a firewall between my public and private networks in case something does get compromised. But I’ve had Plex exposed (on a non-default port) for literally years and nothing ever happens.

Yeah I had to convince them to try RustDesk so they would stop using RDP. Like I said, a lot of people just know enough to be dangerous.

They also do some SSL shenanigans to get every user a unique, valid public certificate created during setup. https://words.filippo.io/how-plex-is-doing-https-for-all-its-users/

also fyi starlink has public ipv6 available if you DO wan’t to set it up. been hosting a minecraft server off a starlink connection lol.

I had to explain to one of them why RDP is a bad idea lol. Thats kind of my point - average people tend to only know enough to be dangerous, not to do things safely. Or as Shakespeare said - "The fool doth think he is wise, but the wise man knows himself to be a fool.”

When I set up wireguard it was just more complicated when one side didn’t have a public IP. Whyyyy can’t we adopt ipv6 already.

I’m talking average enough to see an article, or hear about it from a friend/coworker, then follow the insanely easy setup directions for Windows. I know plenty of people who aren’t really “computer people” but know enough to open a port because they had to to get a game working at some point or another. Those people probably wouldnt notice “hey this thing is going to http maybe i should rethink this…”

Sure, but being mostly secure by default isn’t one of them. One advantage of running a service that offers optional subscription services is that they can offer security features like built-in SSL and AAA that just work. Any average user can install it and have a reasonably secure service running. Hell, until a few months ago you didn’t even need to open a port to have remote access to your content, whether you paid or not. Now they’ve made that a paid feature though.

Sounds like a great reason to use Plex instead!

edit: to add something constructive to my snarky comment, what kind of attack surface are we talkin here? Multiple ports? Lots of separate services running? no authentication?