Edit: I have added the share name at the end of the IP address and now I’m getting mount error(115): Operation now in progress. I haven’t figured this one out yet either. My computer IP and the network drive IP are on the same network and within range. Both should be using the same gateway and DHCP.

I have tried just about every combination of parameters possible and nothing is working. It keeps spitting out a meaningless error and that error is the only thing in the log file too. I have tried a 100 different answers from across stack-overflow to no avail.

I’m running the command below:

sudo mount -t cifs //192.168.50.1/ /mnt/asus -o credentials=/home/user/.smbcredentials

and regardless of how many params I have removed it keeps spitting out : mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

I have referred to the manpage and verified that all of the args I’m using are valid. At this point I’m kind of at a loss. Are there file system args I need to add or something?

I can see the disk with all of the sharenames when I run smbclient -L 192.168.50.1, and I can navigate to it in the file browser, but I can’t mount it for some reason. I have the workgroup name set under /etc/samba/smb.conf. I have tried enabling and disabling NT1. Does anyone have any ideas as to why it might be spitting out an invalid args error even when I removed every single argument?

  • Sam Black@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    Sorry, I was thinking file browser mounts would appear in mount, but they don’t.

    You should be able to list file browser mounts in a terminal using gio mount -li after mounting via the file browser, and it will list the SMB mount it’s using, ie smb://SERVER/$share/

    This annoyingly doesn’t give us the username or domain for the SMB share, and to get that if the server and share looks OK we have to run gvfs (what the file browser for PopOS uses in the background) in debug mode and re-mount the SMB share; in a terminal run pkill gvfs; pkill nautilus; LANG=C GVFS_DEBUG=1 $(find /usr/lib* -name gvfsd 2>/dev/null) --replace 2>&1 ; this will unmount anything in the file browser but will show what username and domain the file browser is using to access the SMB share, for example after clicking on a share in the file browser, among other logs, I get;

    smb: do_mount - URI = smb://absolution.local/samshared
    smb: do_mount - try #0 
    smb: auth_callback - kerberos pass
    smb: auth_callback - out: last_user = 'samblack', last_domain = 'SAMBA'
    smb: do_mount - [smb://absolution.local/samshared; 0] res = -1, cancelled = 0, errno = [22] 'Invalid argument' 
    smb: do_mount - enabling NTLMSSP fallback
    smb: do_mount - try #1 
    smb: auth_callback - ccache pass
    smb: auth_callback - out: last_user = 'samblack', last_domain = 'SAMBA'
    smb: do_mount - [smb://absolution.local/samshared; 1] res = -1, cancelled = 0, errno = [22] 'Invalid argument' 
    smb: do_mount - try #2 
    smb: auth_callback - normal pass
    smb: auth_callback - reusing keyring credentials: user = 'samblack', domain = 'ABSOLUTION'
    smb: auth_callback - out: last_user = 'samblack', last_domain = 'ABSOLUTION'
    smb: do_mount - [smb://absolution.local/samshared; 2] res = 0, cancelled = 0, errno = [0] 'Success' 
    smb: do_mount - login successful
    smb: send_reply(0x55ea6ffe5450), failed=0 ()
    

    This should give the username and domain that connects and can be used in the credential file.

    Once this is done, you can exit the terminal with gvfs running and you should be able to close and re-open the file browser and the mounts should just re-appear normally.

    Hopefully this will give enough information as to why the file browser mount works and the mount command doesn’t.

    • SokathHisEyesOpen@lemmy.mlOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      This is amazing! Thank you very much. I’ll try this out tonight and hopefully get somewhere with it. I’ll let you know either way. Thanks again!