• 2 Posts
  • 4 Comments
Joined 1Y ago
cake
Cake day: Jun 16, 2023

help-circle
rss

Hi, thanks for your reply.

when I run mount -a -vvv I get the following:

mount.nfs: timeout set for Tue Aug 8 16:14:10 2023

mount.nfs: trying text-based options 'vers=4.2,addr=192.168.0.188,clientaddr=192.168.0.116' mount.nfs: mount(2): Permission denied

mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.0.188,clientaddr=192.168.0.116'

mount.nfs: mount(2): Permission denied

mount.nfs: trying text-based options 'vers=4,addr=192.168.0.188,clientaddr=192.168.0.116'

mount.nfs: mount(2): Permission denied

mount.nfs: trying text-based options 'addr=192.168.0.188'

mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying 192.168.0.188 prog 100003 vers 3 prot TCP port 2049

mount.nfs: prog 100005, trying vers=3, prot=17

mount.nfs: trying 192.168.0.188 prog 100005 vers 3 prot UDP port 661

mount.nfs: mount(2): Permission denied

mount.nfs: access denied by server while mounting 192.168.0.188:/mnt/store/test-share


Hi, thanks for your reply.

Lets call the original Proxmox container CT1 and this has the *arrs Dockers that can access and interact with the NFS share on TrueNAS

Lets call the new Proxmox container CT2 and this is the one giving me the can’t access error

Lets call the cloned Proxmox container CT1Clone, this one can access the NFS share.

I think the NFS share is not restricted to any IP address, this is a screenshot of the NFS permissions. https://i.imgur.com/9k5jnw4.png I can also access if from my Windows machine that also has a different IP address.

CT1 & CT1Clone work fine, CT2 doesn’t work.


[SOLVED] Help With NFS Share To Proxmox Container
*****EDIT***** I found the issue, it was me!! LOL I thought it had to be a setting I had forgotten and it was, I forgot to enable NFS & Nesting under Features in the Otions of the cotainer, see this image - https://imgur.com/bSiozKS Thank you to everyone that took the time to reply and offer their suggestions. Hi All, Let me start with some basic basic background on my set up, I have a server running Proxmox with some Ubuntu containers. I have a separate server running TrueNas with a share that has both NFS & SMB set up. I can see this share in Windows 11 and read and write to it. One of the Ubuntu containers is able to see this share via NFS and read and write to it too. I am testing Sonarr, Prowlarr & Qbittorrent Docker containers and got the basics set up, Sonarr can find episodes via Prowlarr of a TV show, hand it off to Qbittorrent to download and then move it from the download folder to the TV folder. Both the download folder and the TV folder are on the TrueNas server. I then set up a Docker container for AudioBookShelf in the same Ubuntu CT and that can also read and write to the NFS share. My issue is that I tried to set up another Ubuntu CT on the Proxmox server but cannot seem to access the NFS share on the TrueNas server. This is what I did (which I think was the same process as the working CT) - 1/Create a privileged conatiner - 2/ Update and upgrade the CT - 3/ Install nfs-common - 4/ Create a directory in the CT in the /mnt directory for the NFS share - 5/ added this line to the fstab file in /etc `192.168.0.188:/mnt/store/test-share /mnt/test-share nfs defaults 0 0` However, when I run `mount -a` I get this error message `mount.nfs: access denied by server while mounting 192.168.0.188:/mnt/store/test-share` Running `df -h` does not show the mount obviously but it does in the working CT As a further test, I cloned the working CT, deleted all the Docker containers and I can still see the NFS just fine. I have probably missed a step while setting up the new CT but I'm not sure what. Can anyone offer some help?
fedilink

My Raspberry Pi’s are named after planets and large bodies on the Solar system.

My servers are named after The Expanse characters and ships.

VM’s and CT’s after their usage with a tag in Proxmox for the OS used.


Dell Optiplex 7060 MFF Faulty Motherboard
cross-posted from: https://lemmy.world/post/953492 > I have a Dell Optiplex 7060 MFF that wont boot, according to the power LED flash sequence it has a faulty motherboard. > > The motherboard has a model number of IPCFL-BS 65W. > > It had a decent i7 processor so I removed it and put it in a lower spec 7060 that I bought, I then installed the i5 from the other 7060 but it still wouldn't boot, no surprise there!! > > I suppose I can do one of the following: > > - sell it as is for spares or repairs on eBay (the CPU (i5-8500T) has got to be worth at least £30 on it's own) > - get a replacement MB from eBay or an AliExpress clone > - try and work out what has failed on this MB and fix it (this is way above my skill level) > > Anyone have any other ideas or suggestions?
fedilink