Forums

Resolved
0 votes
I have several shares setup on my clearOS server which I can mount on a Win10 client with no problems, however, when I try to mount one of them from the fstab file on my linux mint client, it fails to mount. The line from my fstab file is:

//clear72gateway/shared /media/shared cifs username=shea1roh,rw,users 0 0


When I try to mount it

sudo mount -a
Password for shea1roh@//clear72gateway/shared: **********
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
s

I've done some reading that indicate that cifs is outdated, but the reading I've done here seems to indicate that is what I should use. Thanks
Thursday, October 24 2019, 12:46 AM
Share this post:
Responses (5)
  • Accepted Answer

    Tuesday, September 08 2020, 06:53 PM - #Permalink
    Resolved
    0 votes
    I found that I could open the shared folders through the file manager, & copy files back & forth which works fine, but I would still like to be able to mount them in my file system so that I can access them via cli or file dialog boxes. I am no loner getting the "Invalid argument" error, now the error is "No such file or directory". Here is my current line in fstab:

    //192.168.1.1/shared /media/shared cifs rw,username=shea1roh,domain=MORNINGSTAR,vers=3.11 0 0


    I have tried different vers arguments, 3.0, 3.11, & 3.1.1, as well as leaving the vers argument off, & I get the "no such file or directory" error each time. I have confirmed that the folder /media/shared exists on my client, & when I run smbclient -L \\hostname, it lists a shared folder called "shared". Any other suggestions? Thanks
    The reply is currently minimized Show
  • Accepted Answer

    Friday, October 25 2019, 11:44 AM - #Permalink
    Resolved
    0 votes
    From "man mount.cifs" on one of my Mint machines

    vers=arg
    SMB protocol version. Allowed values are:

    · 1.0 - The classic CIFS/SMBv1 protocol.

    · 2.0 - The SMBv2.002 protocol. This was initially introduced in Windows Vista Service Pack 1,
    and Windows Server 2008. Note that the initial release version of Windows Vista spoke
    a slightly different dialect (2.000) that is not supported.

    · 2.1 - The SMBv2.1 protocol that was introduced in Microsoft Windows 7 and Windows Server 2008R2.

    · 3.0 - The SMBv3.0 protocol that was introduced in Microsoft Windows 8 and Windows Server 2012.

    · 3.1.1 or 3.11 - The SMBv3.1.1 protocol that was introduced in Microsoft Windows Server 2016.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, October 25 2019, 07:06 AM - #Permalink
    Resolved
    0 votes
    If that were me, I'd try dropping the parameters one at a time to see when the message changed. I'd also check "man mount" which leads to "man mount.cifs", but to me the obvious thing is that I had "vers" in my line and you have "ver".

    [edit]
    Note also that "vers" does not seem to appear in all man pages on the internet so it may be O/S dependant. Check from your o/s's terminal.
    [/edit]
    The reply is currently minimized Show
  • Accepted Answer

    Friday, October 25 2019, 12:45 AM - #Permalink
    Resolved
    0 votes
    Thanks for the info, the error message is different, so that is progress, right? :-) This is what I have in fstab now, I'm trying the minimum options to get it working:

    //clear72gateway/shared /media/shared cifs rw,username=shea1roh,domain=MORNINGSTAR,ver=3.0 0 0


    The error has changed to

    mount error(22): Invalid argument
    Thanks
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 24 2019, 07:12 AM - #Permalink
    Resolved
    0 votes
    On my Pi I use the following line:
    //server.my.domain/videos /mnt/server_videos cifs x-systemd.automount,noauto,rw,iocharset=utf8,username=nick,password=********,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770,domain=home,vers=3.0 0 0
    x-systemd.automount should allow it to remount if it looses contact then becomes available again.
    uid, gid,file_mode and dir_mode are probably unimportant
    domain was critical. This is the workgroup in ClearOS. This is what you need.
    vers takes it away from using smb1 to the better and more secure smb3.
    The reply is currently minimized Show
Your Reply