Comment

Comment on With the recent happenings with Synology/Plex, I’ve decided it’s time to make the move and up my self-hosting game, just need some input from the veterans to solidify my plan and put it into action.

<- View Parent

Lemming007@lemmy.dbzer0.com ⁨1⁩ ⁨day⁩ ago

Thanks for the reply! I’ll admit, I’m not familiar with HBA cards. So I’ll definitely look into that.

As to the nesting you called out, I could see that being an issue. Would that be the case though if you’re doing basically everything through Proxmox and only using TruNAS for disk management? I’m not sure if you watched his video on the setup, but it at least seemed to be okay. I could be wrong about that though, so I appreciate the input.

source

Sort:hotnew top

habitualTartare@lemmy.world ⁨17⁩ ⁨hours⁩ ago
I’ll be honest that I haven’t watched his videos so maybe it ends up stable. TrueNAS basically says in their docs you can end up with weird issues.

If you host it in proxmox directly there’s less overhead, as in it’s not going bare metal > proxmox > TrueNAS > application. You might run into issues but honestly try it and keep a configuration backup if it fails. Pcie passthrough instead of devices for the HBA card and any external graphics cards works the most stable but you won’t be able to “share” those resources.

I personally like docker for most everything I can with a few things hosted within proxmox. I originally started with portainer which gave me a web GUI for docker but honestly docker-compose files are a better approach. So proxmox > debian > docker Proxmox > trueNAS and proxmox > other VMs. This has its own challenges like passing storage from the NAS to jellyfin but works for me.

As for components, I’m stable on an old office desktop computer potato (albeit it does hit some limits with file transfers and transcoding multiple streams). I wouldn’t necessarily recommend going out and buying an equivalent but if you want to mess around, don’t be afraid of not enough resources in a test config.

source
- Lemming007@lemmy.dbzer0.com ⁨9⁩ ⁨hours⁩ ago
  Understood. I do think Im going to start out with Proxmox and kind of feel things out from there. I am also definitely planning to finally bite the bullet and dive into Docker as a primary driver. I’ve heard lots of good things about it and from a technical standpoint it just makes a ton of sense. Thanks again for the input! :)
  
  source
CmdrShepard42@lemm.ee ⁨1⁩ ⁨day⁩ ago
You might look at TechHuts previous tutorial on setting this all up from around a year ago where he instead used Cockpit to manage his ZFS pool shares rather than TrueNAS. I followed that one a few months ago with a minor amount of Linux experience and got everything set up on Proxmox quite easily. I do recall some people complaining about having issues with permissions or some such which is why he created this new tutorial, but I didn’t run into those issues for whatever reason.

This new Proxmox build has been rock solid after running everything on flaky laptops, mini PCs, and a Windows-based server build for the past 12+ years and I’ve also used it to now run things like Jellyseer, Immich, Frigate, and more which is awesome, but I did spend a good chunk of money for a lot of new hardware, redundant SSDs, RAM, etc so you may be better off starting with something more basic to tinker and learn with.

source
- Lemming007@lemmy.dbzer0.com ⁨9⁩ ⁨hours⁩ ago
  I will definitely check that out, thanks! Out of curiosity, since I don’t have the hardware to play with yet, do you know if you are able to use different sized drives with ZFS pools? I’ve seen that there have been some updates over the past year that should make expanding a ZFS pool doable now, do you know if that is the case? Thanks again for the insight :)
  
  source
  - CmdrShepard42@lemm.ee ⁨4⁩ ⁨hours⁩ ago
    AFAIK no you can’t use different sized drives. I have read about the update to allow you to expand existing pools but it hasn’t made its way to the version of ZFS that Proxmox uses, but I hope it does soon.
    
    Previously, I was using SnapRAID which does allow you to use any size drive provided your parity drives are equal or larger to the rest of the drives in the pool so you may check that out. It worked well for me on Windows.
    
    I would caution that if you plan to build a big library over time, to just bite the bullet and get matching drives to start with because I tried mismatched drives purchased over several years (whatever was a good deal when I needed to expand the pool) and it got to the point where it was becoming unmanageable once I hit about 8 drives as SATA ports became limited and HDD capacities on the market increased (why waste a port on a 6TB drive when you could have a 14TB-20TB drive instead?). With this new server build, I just bought several matching 14TB drives from serverpartdeals.com and had to transfer everything from the old SnapRAID pool to my ZFS pool which took about a week with rsync.
    
    source
    Lemming007@lemmy.dbzer0.com ⁨2⁩ ⁨hours⁩ ago
    Gotcha, thanks! In doing some more research, it looks like you could potential make mirrored vdevs of your smaller disks and then another for your larger drives and add them to the same pool. That may be a workaround to still be able to use ZFS, but I hadn’t heard of SnapRAID so I will definitely check that out, thanks!
    
    You make a good point about just sucking it up and getting all new drives at a much larger capacity though. I am definitely starting to think about that option more closely. Its just obviously expensive as hell when you are also getting a new, much better spec’d, NAS box, haha. Serverpartdeals does have pretty good prices though all things considered so maybe I will bite the bullet and just got for it. Not sure what I’ll end up doing with 4 other perfectly good drives that total 24 TBs though! haha. Although I sure I will find something to do with them, haha. Thanks again for the input and insight. Very much appreciated.
    
    source