Proxmox/Plex/Synology - Issue Mounting with fstab Method, But Folders Generating in NAS Folder

Aup808

New Member
Feb 15, 2024
6
0
1
Hello!

I am having some issues with my Synology / Proxmox / Plex setup; I thought maybe someone on the Proxmox forums here may have done a similar setup with their server as well and could provide insight on where I might be configuring some of my Proxmox settings wrong.

I currently am running a Synology NAS (named "Swan"), where within Swan, "volume1/Media" hosts all my current media files (movies, TV shows, etc.). With my Synology NAS, I enabled NFS service (with maximum NFS protocol at NFSv3), and have the below setting for the Media shared folder on my NAS I want to have Plex access:

Hostname: IP Address of Proxmox
Privilege: Read-Write
Squash: Map all users to admin
Security: sys
[✓] Enable asynchronous
[✓] Allow connections from non-privileged ports
[✓] Allow users to access mounted subfolders

On my Proxmox server, I went into the Datacenter and added an NFS Storage.

ID: Swan
Server: IP Address of Swan
Export: /volume1/Media
Content: Dist image, Container, ISO image, Container template
Path/Target (listed in the row item): /mnt/pve/Swan
Shared: Yes
Enabled: Yes

Within my Plex LXC that I created, I installed nfs-common ("sudo apt-get install nfs-common -y"), and went ahead in the Options section and within Features, checked the box for NFS.

Initially, I created a mount point "sudo mkdir /mnt/plex" that I would point the mounted Media to (from my NAS to my Plex). Going to "nano /etc/fstab", I attempted to add the following lines (with 1.1.1.1 just representing, for now, my Synology NAS IP) but got different errors once I looked to do "mount -a"...

1.1.1.1: /volume1/Media /mnt/plex nfs default 0 0
  • mount.nfs: Connection refused
1.1.1.1: /mnt/pve/Swan /mnt/plex nfs default 0 0
  • mount.nfs: Connection refused
1.1.1.1: /mnt/pve/Swan/volume1/Media /mnt/plex nfs default 0 0
  • mount.nfs: Connection refused

The above all didn't work, so I went and tried an alternative method where I go into the shell of my Proxmox, go to "cd /etc/pve/lxc", then typed in "ls" to see all the conf files across my nodes, and then "nano 102.conf" (into my Plex node), and went ahead and added:

mp0: /mnt/pve/Swan, mp=/mnt/plex

And that worked. Upon starting my Plex server, I can see all my Media files. Huzzah! :)

However, here is my question/problem... Now, in my Synology NAS, within the Media folder, I am getting "template," "private," "images," and "dump" folders automatically being added to my Media shared folder, and even when I delete them, they get recreated. I would love to avoid this, and I had thought because of the way I mounted my NAS right on my node like that versus going through the fstab method, it's creating those files.
  1. Is my assumption above correct? Is that is what creating those empty folders? That is what I hypothesized based on the few posts I found online, but I am not sure the way to fix it.
  2. If so, if I wanted to go back to the fstab method (which seems to work in every other guide I follow - I am not sure where I went wrong), what should I be doing differently, or checking? I am sort of new to Proxmox and Linux, so any detailed help would really be appreciated.

Sorry for the long post, but I wanted to provide as much detail as possible so folks can see how exactly I went ahead with this method so if there is anything I did wrong, it would be easy to troubleshoot. I really appreciate any help you can provide!
 
Last edited:
If you dont need NFS to actually store "Dist image, Container, ISO image, Container template" and only need it as a client mount for videos, then remove it as storage from Proxmox, mount it via PVE fstab to some place other the /mnt/pve, ie /mnt/mynfs. Then use the mp0 pointer to get access.

Or you can do as described here: https://forum.proxmox.com/threads/p...eation-before-manual-mount.31133/#post-155547
and man page for pvesm

As for mounting with container, someone else might be able to point you in the right direction


Blockbridge: Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Thanks for the reply!

So you're saying that the fact I have my NAS mounted within my Proxmox, that is causing the extra folders? It's just with the fstab method, I keep getting "connection refused" (I realized I copied the wrong error message and re-edited my post - not sure if that helps or give hints to my issue). Any issue why that issue is occurring?

I only did the mp0 pointer because the fstab method wasn't working, and but doing the mp0 pointer to the mounted NAS, that is how it worked.
 
So you're saying that the fact I have my NAS mounted within my Proxmox, that is causing the extra folders?
yes, as described here https://pve.proxmox.com/wiki/Storage:_Directory
It's just with the fstab method, I keep getting "connection refused"
The error verbiage implications are VERY different from the one you had before. Its my understanding from your original post, and whats remaining of it, that this is happening _inside_ LXC. If I am not mistaken, NFS mounts from containers require privilege and potentially other settings - search the forums, its been discussed many times.

I only did the mp0 pointer because the fstab method wasn't working,
I am suggesting that you can use "fstab" on the hypervisor host itself, instead of "storage" pool definition. That will work in conjunction with mp0 setting.


Blockbridge: Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Hey there! So - good news, is I figured it out. And silly news - I think it was something very simple. :)

Just if folks find this thread and looking for solution...

So, I unmounted my NAS from the Datacenter (which stopped the folders from populating). For those who want to learn more about the mp0 pointer method, I did follow this video (https://www.youtube.com/watch?v=Hsgc2BHpE-w) originally (around the 4:40 mark) which was helpful.

Anyway - thanks again to help steer me in the right direction!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!