Hello! I have Proxmox VE running on a Dell R730 with an H730. Proxmox manages the disks in a ZFS RAID which is exactly how I want it. Because I intend for this server to have a NAS/file server, I want to set up a container or VM in proxmox that will provide network storage shares to domain-joined systems. Pretty much everything in my lab is joined to FreeIPA, so I’d like to use the IdM features with my file server. I have given TKL FileServer a shot but it really didn’t seem up to snuff with what I wanted. I am not looking for a NAS solution that will require me to pass through the RAID controller and disks to Proxmox, as I want Proxmox managing the ZFS pool. I can set up an NFS/Samba server in a container, however in trying to do so I was running into issues (due to it being an unprivileged container) that I can probably figure out but I want to see if anyone has any recommendations first.
I do it the other way round: proxmox leaves it’s hands away from the zpool. The 5 disks are passed through to a vm, everything ZFS starts there, and it offers the samba shares.
My directive is that the bare metal proxmox shall not offer any services to the world outside, only VM’s may do that.
That’s what I’ve done as well, hard drives passed through, RAIDZ created on the NAS itself. It’s worked great so far.
Same! Two zpools on one Debian VM, shares NFS etc for everything else. I pass through PCIe sata cards to the VM, too.
My go-to for this is a plain Debian or Ubuntu container with Cockpit and the 45Drives file sharing plugin. It’s pretty straightforward and works pretty well.
Removed by mod
Seconded on Cockpit project w File Sharing.
Probably not best practice, but it’s possible to install it on the PVE host itself since its ZFS manager and Identity manager plugins and other features fills some gaps in what Proxmox doesn’t do (or would have to drop to CLI to do).
Also recommend RClone in a systemd can take care of various file movements, syncs and backup tasks you may need against the host, vdumps or SMB file shares.
I’ve been happily running Open Media Vault in a Proxmox VM for some time now.
did you pass through the disks or straight on zfs?
I didn’t pass any phy disks through, if that’s what you mean. I’m using that system for more than OMV. I created disks for the VM like I would any other VM.
I don’t understand all the words you’re using but:
Having had Proxmox sort out my drives and having had failures and Proxmox refuse to start if the drive isn’t present (it was present but forgot it’s label so it wasn’t there for Proxmox) I recommend just passing through the drives to your NAS and having it handle the drives.
That way if they fail then your NAS fails but Proxmox boots.
Also if you’re mounting them directly use the “nofail” option so it doesn’t kill your Proxmox if you don’t just have the NAS handle it.
Hmm. If you are going to have proxmox managing zfs anyway then why not just create datasets and share them directly from the hypervisor?
You can do that in terminal but if you prefer a gui you can install cockpit on the hypervisor with the zfs plugin. It would create a separate web gui on another port. Making it easy to create, manage, and share datasets as you desire.
It will save resources and simplify zfs management operations if you are interested in such a method.
i think I’ll give that a shot
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters LXC Linux Containers NAS Network-Attached Storage NFS Network File System, a Unix-based file-sharing protocol known for performance and efficiency PCIe Peripheral Component Interconnect Express SMB Server Message Block protocol for file and printer sharing; Windows-native ZFS Solaris/Linux filesystem focusing on data integrity
6 acronyms in this thread; the most compressed thread commented on today has 13 acronyms.
[Thread #722 for this sub, first seen 29th Apr 2024, 11:55] [FAQ] [Full list] [Contact] [Source code]
deleted by creator