Right. I don’t 100% know that this will work, but I would try just removing the ,sec=ntlm from your fstab line.
TrueNAS Scale is linux based
TrueNAS Core is BSD based
And I know this is frustrating to deal with, but TrueNAS of both flavours are both quite capable of serving Network Shares via NFS, SMB, WebDAV, iSCSI and probably some other stuff, so it somewhat depends on how your TrueNAS shares are setup.
Right. I don’t 100% know that this will work, but I would try just removing the
,sec=ntlmfrom your fstab line.
Hmmm… That did something. The mount now appears under the network tab in Dolphin, it actually appears twice, one shows mounted and the other shows unmounted.
I can navigate the files but only read, no write.
Are you happy for any user on your Fedora machine to write files to the NAS? (Maybe an academic question if you are the only user.)
If so, you could add ,noperm as the last option in the fstab line (i.e. put it where ,sec=ntlm used to go).
That means all users on the Fedora machine have read-write access to the share. (The server side has its own permissions, but those checks will be passed whoever is logged into Fedora, because the right credentials were passed at mount time, taken from your .smbcredentials file.)
1 Like
Yeah, That works now. Thank you
My fstab now looks like this:
//172.16.0.201/SAS6T/user/ /mnt/tnas cifs credentials=/home/corny/.smbcredentials,iocharset=utf8,noperm 0 0
1 Like
SMB works under Linux (typically via the Samba software suite), but NTLMv1 has been deprecated. If your NAS supports NTLMv2, that should still work (for a while).
There can be a few gotchas with respect to the supported file names and how they may or may not be mapped to the right name if you are connecting multiple clients to the same NAS server. But as long as you don’t use any “unusual” characters in your file names like :, you probably won’t see any problems.
1 Like
If you right-click the “bad” one in Dolphin, do you get an option to hide it?
Yes.
I suppose I need to work on my OCD and just let it go but,…
I wish I knew why things do what they do.
Wow, thank you pg-tips. I was going to a bad place before you entered the chat 
1 Like
If you want to see a bit of what’s under the hood, look at the file ~/.local/share/user-places.xbel.
Search for your /mnt/smb in there and - I’m guessing a bit, but I think you’ll see two entries for it. The one from fstab should have <isSystemItem>true</isSystemItem>, and the other one (added manually in Dolphin) maybe doesn’t have that?
Beautiful, I will go investigate and try to increase my knowledge.
Here are the entries from “user-places”
<metadata owner="http://www.kde.org">
<UDI>/org/kde/fstab///172.16.0.201/SAS6T/user:/mnt/tnas</UDI>
<isSystemItem>true</isSystemItem>
</metadata>
</info>
</separator>
-and-
<metadata owner="http://www.kde.org">
<UDI>/org/kde/fstab///172.16.0.201/SAS6T/user/:/mnt/tnas</UDI>
<isSystemItem>true</isSystemItem>
<IsHidden>true</IsHidden>
</metadata>
</info>
</separator>
</xbel>
The only thing besides ishidden is the backslash after user.
Should I just delete the whole second entry or just leave it alone?
-edit- Nope, tried deleting it but it comes back on its own.
It shouldn’t do any harm to keep the currently hidden item, but you can delete it if you like.
If so, make sure to keep the structure of the XML correct. i.e. delete the <separator> tag at the beginning of the entry, the </separator> tag at the end of the entry, and everything in between them.
Does it make any difference if you have Dolphin closed while doing the edit?
I didn’t work. The file gets recreated somehow.
So, is this a genuine bug or am I still making some mistakes?
Does it make any difference if you have Dolphin closed while doing the edit?
No. I just tried that too.
Ah ha!
I figured something out on my own.
I took out that backslash in fstab and it fixed the duplicate entry.
-edit- Those are forward slashes. My bad.
3 Likes