I asked for help previously, but the same issue is happening, so I will repost and ask my question another way.
In TrueNas Scale latest version, If I want to create ONE user account and ONE mount point, and have MULTIPLE computers access the same point with the same account, HOW do I set this up?
I want to use it with a multiprotocol SMB and NFS so both my WIndows and Linux machines can access the same things.
Everyone tells me to look in the documentaiton and provides links to the documentation, however the documentation isn’t telling me (A COMPLETE NOOB), exactly HOW to accomplish this.
(i.e. Click this to go here, select this, do that, click this to go there, click this, do that, etc.).
Once I am given SPECIFICS on HOW, this will also help me LEARN for the next time, and it will make sense.
Can anyone please help me make sense of it all?
Thank you so much in advance.
(You might like to bolster the information you have provided in this immediate post with advice written here: it’ll help people better skilled than me to help you).
In trueNAS you first have to create a pool …go into the "storage" menu item on the left hand side (LHS) here:
and then, top RHS of screen, press the blue button called "create pool".
At this stage you’d ideally need to read the documents to decide which options are best for you but you could gamble on setting up using defaults and select a “generic” pool.
Then go to "datasets" and similarly create a dataset called (let’s assume) “documents”.
Then go into "shares" and add an SMB and an NFS share which point to the dataset on the pool which you’ve just created.
In your client machines, get them to point at those shares so if you’re using a NAS server called truenas.local for example, you might have your nfs mounting details (in my linux boxes I have an fstab entry in /etc which looks something like this):
so your truenas.local box is sharing out of a pool called “wizard” and a dataset called “documents” and it’s read/write etc. which gets mounted on your client machine as if it is a local directory. Something similar with Windows, but I don’t recall how to do SMB right now.
Your best approach might be to mock up something to share out (create a “testpool” and a “testdocument” dataset with a few PDFs in it), then play around with names until you get it just how you want it to be, then share the real thing. Less frustrating and less chance of losing data!
Linux has a pretty good SMB client. There’s no reason to try to complicate things with multiple protocols (especially one that will generally lower your overall security if you don’t configure it properly).
I didn’t even know Linux had this, I was always told it had to be NFS. Let me get SMB working first LOL.
I don’t worry about security at all because it is just myself and my wife, I am setting up 6 servers with TrueNAS Scale to use as individual NAS boxes, and a few off site backups as well when I get things working properly.
@WW1ZRD@awalkerix I didn’t know about SMB and linux either, so I too might need to re-think my setup!
My wife has a Chromebook which needs to be SMB when looking at our TrueNAS shares. Everything else needing visibility of TrueNAS is running on a linux OS and hence I assumed NFS was the correct approach, but perhaps not.
The creating a pool or share isn’t the problem, very easy stuff there.
It’s the PERMISSIONS that are killng me LOL.
At the start I was creating a “user” account for each machine that would access the NAS, and (I thought) everyone had full read write access, but that wasn’t the case.
For example, I created the first user account (ww1zrd) and gave it full access, and it worked, no problem.
I made an account for the study computer, gave it the same full permisisons, but it doesn’t want to point to the same mount point because ww1zrd has it.
This is where I am stuck… and I don’t NEED a different account for each computer, I would love for everthing to have full access with just one account.
I tried that once and I think the connection “was rejected by the server” because only one user can access it?
I don’t know why you started a new thread, but this is part of your problem. User accounts are for users (i.e., people), not for computers.
This is the second problem, which you were also told in your other thread: don’t use home directories for this purpose. Create a share, and give the relevant users (people) permissions to it. Leave the home directory at its default of /var/empty.
Just because information is given, doesn’t mean it makes sense to the one receiving it.
The information didn’t fully work, which is why my issue still existed, so I reposted in a different way to hopefully get clearer information that did make sense to someone who never set up TrueNas before.
I just wiped my sever, reinstalled TN Scale, and will start again with a clean slate.
That’s not how things work though… this way you waste the time of 1) the people who tried to help you in the first thead and 2) the people who will try to help you in the second thread.
If you don’t understand an answer, clarify that in the same thread; if you REALLY want to open a new threads for X reasons, either link the old one at the start of the new one or leverage discourse’s feature “Reply as a linked topic”.
Opening a new thread after you are given an answer can be also seen as asking the same question until you get an answer you like… but that will be for mods to judge; this is basic netiquette.
So, what do you exaclty want to do? What do you not understand? Explain datasets, users, and what those users should be able to do in which datasets.
Also, do note that there are good tutorials about SMB peemissions on YouTube by @lawrencesystems.
Thank you for shedding a bit more light on this for me.
Nowhere was I seeing what settings to enter in the ACL, etc.
I finally did figure it out, but THANK YOU for showing a simpler way.
Sometimes experts who work with something all the time fail to stop and think what it is like for someone who never touched TrueNAS before… it presents a lot of options, which can be very confusing and intimidating if you aren’t familiar with what each one does.
After wiping Terabytes off my drives, starting with a clean slate and a new install, your method worked, and I am able to use ONE “user” account from various computers around my house to access the server.
I can now repopulate my drives, then replicate the process on 5 more servers to insure my data is safe, thanks to your simple pointer.
Thank you so much.
I prefer to leave things with a positive outlook. Yes, the permisisons of everything were set to wide open (full control, read/write/execute/, etc.) and nothing was working.
A clean sweep deleting all my data, fresh install, and following Awalkerix pointer did the trick.
I pointed out that all I wanted to do was have one user account that any of my computers could access from around the house, as before the connection was being denied by the server because only one user could be connected at a time, etc. (This was the error I was receiving).
I just connected to the same user account from 3 different computers and I am happy, so it works, and that’s all that matters.
