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.

0 points
Deleted by creator
permalink
report
reply
2 points

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.

permalink
report
reply
2 points

i think I’ll give that a shot

permalink
report
parent
reply

I’ve been happily running Open Media Vault in a Proxmox VM for some time now.

permalink
report
reply
1 point

did you pass through the disks or straight on zfs?

permalink
report
parent
reply

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.

permalink
report
parent
reply
3 points

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.

permalink
report
reply
9 points

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.

permalink
report
reply
1 point
*

To add to this, here is a tutorial with video that goes into the permissions. One of the cockpit modules has had an update, so make sure you bump the version number.

  • I had to make it a privileged container to get NFS working. If you only need SMB, unprivileged is fine. There’s nfs-utils for userspace nfs setups, but I haven’t futz with it yet.

https://www.apalrd.net/posts/2023/ultimate_nas/

I replaced a TrueNAS install with this and haven’t been happier. It was such a bloated resource hog for what an LXC and a podman/dockge install can do.

permalink
report
parent
reply
1 point

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.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 5K

    Monthly active users

  • 3.6K

    Posts

  • 81K

    Comments