Linux Mint Cinnamon 21.1 using the default/current 5.19.0-43 kernel with CIFS-UTILS installed as part of the included items. 2 older NAS units that run SMB 1, one is a SnapServer 4100 and one is a Buffalo Terastation Pro TS-HTGL/R5 F/W 1.35 that both worked well under Windows 7 and Windows 10 22H2 with the SMB feature added. Mounts and is readable in LM 21.1 but when I right click the menu doesn't allow any write actions such as delete, paste, etc. Password file is correct and AFAIK I have the FSTAB correct but I might have something missing in the options. If I right click and use Open As Root and give the root password it allows me to do write actions. Is this normal to not allow write actions unless I open as root? I'm still fairly new to Linux other than basic stuff so please go easy on me
I have read the Man page on FSTAB but its not extremely thorough so I need some help from those of you familiar with the FSTAB setup for network devices using SMB1. Below are the lines applicable to my NAS units in the FSTAB
--------------------------------------------------------------------------------
# Snap4100 NAS
#
#//192.168.1.250/snapshare /media/snapnas cifs credentials=/home/russ/.smbcredentials,iocharset=utf8,vers=1.0,file_mode=0777,dir_mode=0777,domain=homeoffice 0 0
#
# Buffalo TeraStation NAS
#
//192.168.1.251/terashare /media/buffalo cifs credentials=/home/russ/.smbcredentials,iocharset=utf8,vers=1.0,file_mode=0777,dir_mode=0777,domain=homeoffice 0 0
------------------------------------------------------------------------------------
SMB1 devices in LM 21.1 auto mount in Fstab [SOLVED]
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
SMB1 devices in LM 21.1 auto mount in Fstab [SOLVED]
Last edited by LockBot on Sun Dec 03, 2023 11:00 pm, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: SMB1 devices in LM 21.1 auto mount in Fstab
Add another option to your mount:
nounix
//192.168.1.251/terashare /media/buffalo cifs credentials=/home/russ/.smbcredentials,iocharset=utf8,vers=1.0,file_mode=0777,dir_mode=0777,domain=homeoffice,nounix 0 0
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Re: SMB1 devices in LM 21.1 auto mount in Fstab
Unfortunately no change. Edited the fstab, did a sudo mount -a and no change so rebooted with no change. I did install a few other file managers to see if maybe it was an issue with Nemo but no change so not the file manager.
Re: SMB1 devices in LM 21.1 auto mount in Fstab
I can't reproduce this problem - although I'm not accessing your specific nas just a server that allows SMB1.
If replacing
Question: Is it only you
If it is you can just replace root with you:
If replacing
nounix
with noperm
doesn't fix it I'm out of ideas.Question: Is it only you
russ
that needs write access?If it is you can just replace root with you:
//192.168.1.251/terashare /media/buffalo cifs credentials=/home/russ/.smbcredentials,iocharset=utf8,vers=1.0,uid=russ,domain=homeoffice 0 0
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Re: SMB1 devices in LM 21.1 auto mount in Fstab
yes I am the only one on the machine username-wise. I will try that and see how things work out. Appreciate the help and patience from everyone.altair4 wrote: ⤴Sat Jun 03, 2023 11:46 am I can't reproduce this problem - although I'm not accessing your specific nas just a server that allows SMB1.
If replacingnounix
withnoperm
doesn't fix it I'm out of ideas.
Question: Is it only youruss
that needs write access?
If it is you can just replace root with you://192.168.1.251/terashare /media/buffalo cifs credentials=/home/russ/.smbcredentials,iocharset=utf8,vers=1.0,uid=russ,domain=homeoffice 0 0
Re: SMB1 devices in LM 21.1 auto mount in Fstab
cifs mount, windows protocol, doesn't support linux file permisions. You need to tell linux who owns it, either as altair4 suggested
uid=russ
or uid=1000,gid=1000
(mint assigns an id of 1000 to the first user created, normally you).An example mounting my synology nas with cifs:
Code: Select all
//diskstation.local/home/ /media/synology cifs credentials=/etc/samba/credentials,uid=1000,gid=1000,nofail 0 0
Thinkcentre M720Q - LM21.3 cinnamon, 4 x T430 - LM21.3 cinnamon, Homebrew desktop i5-8400+GTX1080 Cinnamon 19.0
Re: SMB1 devices in LM 21.1 auto mount in Fstab
Well the UID added fixed it. After I edited fstab and used the sudo mount -a it didn't but after a reboot it came up allowing me to do read and write functions. Appreciate the help greatly. I havent tried the most recent solution but will next.
EDIT: Just tried the UID=1000,GID=1000 in place of the UID=russ and it too works perfectly but it required a reboot as well, the sudo mount -a didn't change it. Thanks again
EDIT: Just tried the UID=1000,GID=1000 in place of the UID=russ and it too works perfectly but it required a reboot as well, the sudo mount -a didn't change it. Thanks again
Last edited by RussB257 on Sat Jun 03, 2023 5:15 pm, edited 1 time in total.
Re: SMB1 devices in LM 21.1 auto mount in Fstab [SOLVED]
I totally missed that part of the response regarding noperm, I may have overlooked it as a quote. While the uid=russ and the uid=1000,gid=1000 both worked well I re-edited the fstab file and lo and behold it works perfectly. Sorry I missed this in the beginning but I have 3 different options now, I printed the fstab file for each working scenario for my notebook.
Again thanks to everyone that helped on this, it is very much appreciated. I was considering doing a dual boot Win 10 and Linux Mint 21.x so I could do write operations to the 2 NAS drives and now I don't even have to consider Windows at all other than a dual boot on my office PC for only one program that doesn't work well in a VM since it's a driver/print manager for a Sawgrass sublimation printer. That printer is soon to go away though, I am in the process of replacing it with an Epson sublimation printer and selling the expensive (to run/maintain) Sawgrass.