[SOLVED] Problems mounting shares at boot with fstab

road hazard · 04-29-2020, 12:28 PM

I have a server running Linux Mint 19.3. It has various directories shared out via Samba. I can access those shares from anything in my house so I think that's good to go.

I have a headless box running Mint 19.2 that is an FTP server that people can log into and it has mounts that point to the 19.3 server box and all is well. Shares on the 19.2 headless FTP server are mounted via fstab:

Code:

//192.168.1.5/Classic\040cars /mnt/classic_cars cifs username=anonymous,password=anonymous,iocharset=utf8 0 0
//192.168.1.5/Friends /mnt/friends cifs username=anonymous,password=anonymous,iocharset=utf8 0 0
//192.168.1.253/crap /mnt/asus_test cifs username=anonymous,password=anonymous,iocharset=utf8 0 0

From the FTP box, Classic cars and Friends works fine. The only problem is the last one... the .253/crap share. 253 is my test Debian 10 box. Here is the SMB.conf file from my Debian 10 test box:

Code:

[crap]
        path = /mnt/crap/
        read only = yes
        guest ok = yes
        guest only = yes
        map to guest = bad user

I'm sharing out the /mnt/crap folder on the Debian 10 box (192.168.1.253). I can see this share from any and all boxes in my house. But when I try to map it via the fstab file on the headless FTP server, it's not mounting at boot. If I start X on the FTP server and login to the GUI and go to the Network icon, I can see my Debian 10 test box and I can see the 'crap' folder and I can open it up anonymously and see the files inside perfectly. What am I missing with the fstab mounting at boot?

I see this in dmesg on the FTP server when it boots:

Code:

[   15.257176] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[   15.263147] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[   15.270375] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.

So I tried adding vers=1.0 for the 'crap' mount and it made no difference. Heck, I get that same error for the other 2 shares and they seem to work fine so maybe that's a red herring?

The Squash · 04-29-2020, 01:44 PM

Please show me the contents of the file "/var/log/boot.log" on your Linux Mint headless server. I'm hoping that will shed some light on why this is happening.

Also does the directory "/mnt/asus_test" even exist? If not, you need to create it manually. (In case you didn't already know that.)

road hazard · 04-29-2020, 02:43 PM

Quote:

Originally Posted by The Squash

Please show me the contents of the file "/var/log/boot.log" on your Linux Mint headless server. I'm hoping that will shed some light on why this is happening.

Also does the directory "/mnt/asus_test" even exist? If not, you need to create it manually. (In case you didn't already know that.)

Yep, "/mnt/asus_test" exists.

I have a boot.log file in that dir but it's empty. I sorted by timestamp on that dir and here's the newest to oldest (snipped off the very bottom). If you need to see any of these, just let me know.

Code:

asus@asusftp:/var/log$ ls -halt
total 5.0M
-rw-r-----   1 syslog            adm              80K Apr 29 15:18 auth.log
drwxrwxr-x  11 root              syslog          4.0K Apr 29 15:18 .
-rw-rw-r--   1 root              utmp            287K Apr 29 15:17 lastlog
-rw-rw-r--   1 root              utmp            121K Apr 29 15:17 wtmp
-rw-r-----   1 syslog            adm             1.7M Apr 29 15:17 syslog
-rw-r-----   1 syslog            adm             1.3M Apr 29 14:13 kern.log
-rw-r--r--   1 root              root            2.4K Apr 29 13:30 mintsystem.log
-rw-r--r--   1 root              root             113 Apr 29 13:30 ubuntu-system-adjustments-adjust-grub-title.log
-rw-r--r--   1 root              root              26 Apr 29 13:30 ubuntu-system-adjustments-start.log
-rw-r--r--   1 root              root              26 Apr 29 13:30 ubuntu-system-adjustments-stop.log
-rw-r--r--   1 root              root             69K Apr 29 12:53 dpkg.log
-rw-r--r--   1 root              root             527 Apr 29 12:50 alternatives.log
drwxr-xr-x   2 root              root             240 Apr 29 12:47 apt
-rw-r--r--   1 root              root             34K Apr 29 12:43 Xorg.0.log
-rw-r--r--   1 root              root             23K Apr 29 12:42 Xorg.0.log.old
-rw-r--r--   1 root              root            1.3K Apr 29 12:42 gpu-manager.log
drwxr-xr-x   2 root              root             109 Apr 29 12:31 lightdm
-rw-r-----   1 root              adm              156 Apr 29 09:15 vsftpd.log
-rw-r-----   1 syslog            adm             151K Apr 29 00:07 syslog.1
drwxr-xr-x   2 root              root            4.0K Apr 29 00:07 cups
-rw-r-----   1 syslog            adm              26K Apr 28 00:10 syslog.2.gz
-rw-r-----   1 syslog            adm              26K Apr 27 00:09 syslog.3.gz
-rw-r-----   1 syslog            adm              26K Apr 26 00:09 syslog.4.gz
-rw-r-----   1 syslog            adm              37K Apr 25 23:17 auth.log.1
-rw-r-----   1 syslog            adm             516K Apr 25 15:00 kern.log.1
-rw-r-----   1 syslog            adm              26K Apr 25 00:05 syslog.5.gz
-rw-r-----   1 syslog            adm              26K Apr 24 00:05 syslog.6.gz
-rw-r-----   1 syslog            adm              26K Apr 23 00:07 syslog.7.gz
-rw-r-----   1 root              adm             2.4K Apr 22 11:03 vsftpd.log.1
-rw-r-----   1 syslog            adm             5.1K Apr 19 23:17 auth.log.2.gz
-rw-r-----   1 syslog            adm             139K Apr 19 14:38 kern.log.2.gz
-rw-r-----   1 root              adm             1.7K Apr 19 10:52 vsftpd.log.2
-rw-rw----   1 root              utmp            1.2K Apr 15 13:22 btmp
-rw-r--r--   1 root              root            101K Apr 13 21:34 dpkg.log.1
-rw-r--r--   1 root              root            3.8K Apr 13 21:33 alternatives.log.1
-rw-r-----   1 syslog            adm             2.3K Apr 11 23:17 auth.log.3.gz
-rw-r-----   1 syslog            adm              94K Apr 11 16:46 kern.log.3.gz
-rw-r-----   1 root              adm              158 Apr 11 02:03 vsftpd.log.3
-rw-r-----   1 root              adm              490 Apr 10 13:13 vsftpd.log.4
-rw-r-----   1 syslog            adm             3.1K Apr  5 23:17 auth.log.4.gz
-rw-r-----   1 syslog            adm             125K Apr  5 14:26 kern.log.4.gz

JeremyBoden · 04-29-2020, 04:08 PM

Isn't

Code:

//192.168.1.5/Classic\040cars /mnt/classic_cars cifs username=anonymous,password=anonymous,iocharset=utf8 0 0

going to cause trouble one day?

michaelk · 04-29-2020, 04:20 PM

Quote:

[crap]
path = /mnt/crap/
read only = yes
guest ok = yes
guest only = yes
map to guest = bad user

map to guest = bad user is a global directive. I also agree that you should avoid using spaces in share names.

road hazard · 04-29-2020, 06:08 PM

Quote:

Originally Posted by JeremyBoden

Isn't

Code:

//192.168.1.5/Classic\040cars /mnt/classic_cars cifs username=anonymous,password=anonymous,iocharset=utf8 0 0

going to cause trouble one day?

I might be able to push that day back a few years if I get all this working and replace Mint with Debian considering their (Debian's) slow/stable roll out cadence.

road hazard · 04-29-2020, 06:10 PM

Quote:

Originally Posted by michaelk

map to guest = bad user is a global directive. I also agree that you should avoid using spaces in share names.

WE HAVE A WINNER! Wow, that simple change (removing map to guest in the share section) fixed it! Thank you so much!!!!

JeremyBoden · 04-29-2020, 06:14 PM

Mint do a Debian version (LMDE4), just Mint + Debian 10 repositories currently (no Ubuntu packages).
It's very stable.

road hazard · 04-29-2020, 06:25 PM

Quote:

Originally Posted by JeremyBoden

Mint do a Debian version (LMDE4), just Mint + Debian 10 repositories currently (no Ubuntu packages).
It's very stable.

That brings up a very good discussion. I've looked very closely at LMDE 4. As a newbie, I've been struggling the past few days with Samba sharing in Debian 10. In LMDE 4, it's beyond simple..... just right click and share a folder. If prompts you to install Samba and reboot. Making shares read only/full access is just point and click. I guess that is part of the polish the Mint team puts on Debian. I could have given up but I wanted to learn how to do the same in pure Debian. Another weird thing though, when I do the simple/easy sharing in Mint, I don't see any of the shared directories in their smb.conf file so I don't know where they're hiding the magic but hey, Samba sharing works perfectly in Mint and is VERY easy to get going.

I also noticed that when Debian 10 hit, I don't think Mint released LMDE 4 until several months later. When a new version of Debian drops, I'd like to switch to it sooner vs. later.

My last concern with using LMDE 4 is Plex. LMDE (even though it's pure Debian just with an updated Cinnamon desktop and a few other minor tweaks) isn't an officially supported distro according to the mods/devs over on the Plex forums so if I run into problems, I'd like to be using a fully supported distro. ie, Debian.

michaelk · 04-29-2020, 06:57 PM

The testparm utility checks the smb.conf file for correct syntax... It runs as a regular user.

Adding "right click and share a folder" is possible using the usershare directive and nautilus should detect it I believe. Never have tried.

https://wiki.archlinux.org/index.php...ble_Usershares

road hazard · 04-29-2020, 07:11 PM

Quote:

Originally Posted by michaelk

The testparm utility checks the smb.conf file for correct syntax... It runs as a regular user.

Adding "right click and share a folder" is possible using the usershare directive and nautilus should detect it I believe. Never have tried.

https://wiki.archlinux.org/index.php...ble_Usershares

When doing all this playing around, I would often run testparm and don't recall it ever spitting out some obvious "You did something silly, it will cause problems" type of message on the screen.

As for Thunar, looks like it can be customized a bit in Debian to do some 'right click sharing' type of commands. Will have to look into that. Thanks!!

michaelk · 04-29-2020, 07:21 PM

In this case you should of seen the message

Quote:

Global parameter map to guest found in service section

road hazard · 04-29-2020, 07:25 PM

Quote:

Originally Posted by michaelk

In this case you should of seen the message

Hmmm, now that you mention it, I think I did see that. But since it wasn't preceded with an: ERROR ERROR ERROR!!!!!!! THIS IS IMPORTANT AND WILL CAUSE PROBLEMS type of label, I didn't think anything of it. Thought it was just informational.