You're missing the share name, //192.168.50.1/sharename
this post was submitted on 16 Aug 2023
24 points (96.2% liked)
Linux
47947 readers
1367 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
I tried with several share names and it didn't work. But I tried again just now for the first time since I moved the credentials to a file and it threw a different error: mount error(115): Operation now in progress. That's at least something I can work with. Thank you!
It may be a number of things, but I would try to restructure your command with the options first, then the share path with the mount point as the final arguments (this matches the examples given in the documentation).
I would also suggest not using a dot file for your credentials, as they are actually a bug and not a feature.
sudo mount -t cifs -o credentials=/home/user/smb.creds //192.168.50.1/sharename /mnt/asus/
Edit: Found this to better explain the structure of command line arguments: https://unix.stackexchange.com/questions/484152/how-to-distinguish-between-a-positional-parameter-and-an-option
Okay I just tried that and it throws the mount error(22): Invalid argument error again.
Does /mnt/asus exist on your system?
Please share the exact command you tried, maybe there's something we're missing.
Thanks! I'll give that a try tonight after work.
/home//.smbcredentials
This looks strange.
There's an outside chance they just don't want to show their username, but yeah OP should make sure they're properly pathing to their creds
Oh I guess it edited out the user variable I put there. Weird. I'll edit it again. It's correct in my terminal. Good eye though.
Have you tried:
smb://user@ip/sharename/
I haven't, but I will tonight. Thanks!
I'm also pretty sure that you have to specify a share. Like //192.168.50.1/$Share. IIRC.
I thought I could just map to the main drive since I have multiple shares on that drive, but I guess not. I did try with multiple share names before I moved the credentials to the file and it was throwing the same error. I tried again just now with a share name and it started throwing this error: mount error(115): Operation now in progress. That is at least something I can work with. Thank you!
Are you sure the path to your credentials file is correct and does it look like this?
username=value
password=value
domain=value
It's correct. I put it in greater than/less than brackets up above to indicate that it was a placeholder and Lemmy stripped it out for some reason. I have edited above to just say "user". Good eye though.
My file looks like that except for the domain value. I don't have that line. What would go there? It's a network drive connected directly to my router with a USB cable and then the router SMB client and mapping is configured. I know that's correct because I can map them in Windows, and I can list them in Pop in the terminal, as well as browse it in Pop in the file explorer. Alternatively I started out just using the user/password arguments for the terminal mounting command and only moved it to the file to get rid of those arguments since the error it's throwing is saying there are invalid arguments. I have the workgroup set in the config file and I'm explicitly declaring the IP in the mount command. There's no domain name, unless that means something I'm unaware of.
domain in this instance is the workgroup, and is optional according to the man page.
Have you tried adding --verbose before the -o? That might yield more information.
The workgroup is set in the cfg file. I got a little further now. Since moving the credentials to the file I am getting a different error. Now I get mount error(115): Operation now in progress which is some sort of connection error. I was actually just logging verbose right before I checked back here and it just spits out the options from the config file and the error message. Still trying to figure this new error out since both the computer and the drive are on the same network, and within the same range.
OK, you may want to check dmesg or journalctl if there are further errors from the kernel - there is also a -v argument for mount, eg mount -t cifs -v //SERVER/$share /mnt --verbose -o... that might help.
Don't know if you've found this already (and apologies if you have!) but this suggests some not obvious solutions https://superuser.com/questions/430163/cifs-share-mount-errors
Also (brain dumping) if you've successfully mounted it via the file browser, do so again and then check mount to see what arguments/options the CIFS mount is using - it might yield some important differences.
Thanks! That last option is something I thought of too, but I didn't know what to do to get that information. I tried properties in the file explorer, but that didn't work. Do I just type mount into the terminal to get a list of mounts? I'll definitely try all of this after work. For now I'm exhausted from staying up until 1:30 am trying to get this figured out.
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.
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!
I think the default domain is empty or WORKGROUP. It would be used if you had active directoy for the user authentication.
I read some more of the man page and this should be optional.
Pop goes the weasel! Lol! Best of luck on your tech issues.