I had a longer reply typed out, but I guess the network ate it. The gist was to consider a second low power device for the always on services that don’t need the big noisy storage.
Comment on Putting HDDs to sleep
thecoffeehobbit@sopuli.xyz 3 weeks agoI’ll gladly take the advice on the NAS VM, I see so many tutorials virtualising TrueNAS and not a lot of the opposite viewpoint. If it’s not a good practice I’d indeed rather recycle that setup while I’m at it.
I don’t need to keep using Proxmox, or TrueNAS for that matter. If I need to DIY this with bare metal Debian, I will. My constraint is to have both always-on services and on-demand HDD backed services on the same machine. Sky is the limit after that…
Scheduling doesn’t sound the best indeed, which is why I’d ideally want a simple button that I can click from a GUI.
frongt@lemmy.zip 3 weeks ago
thecoffeehobbit@sopuli.xyz 3 weeks ago
I currently have exactly this setup but I really want to migrate to a single machine :)
frongt@lemmy.zip 3 weeks ago
I think you have two goals at odds with each other.
tofu@lemmy.nocturnal.garden 3 weeks ago
I think it’s mostly advised against virtualizing because of problems with virtual filesystems, passing through your drives eliminats most reasons against it. I think this thread links most of the points. I think it was also in TrueNAS docs, but I can’t find it rn.
truenas.com/…/absolutely-must-virtualize-truenas-…
thecoffeehobbit@sopuli.xyz 3 weeks ago
Thanks - from what I see myu CPU doesn’t support VT-d, only VT-x, which at a glance makes it not suitable for passing through these drives safely. I’ll get to dismantling the NAS VM setup actually.