mount.cifs error 19

[lhacky]

Hi all,

I know. I know that this problem has been cropping up for various people on various distros for the last few years, and I am ready to accept that I'll be kicking myself once the answer is found. But I spent about 5 hours on this last year, then gave up; I've now done a full system upgrade again and spent another 5 hours, and I'm no closer.

It used to work.

I'm running arch linux on my raspberry pi. I have an external hard-drive plugged into my router which serve it as a samba share. I cannot mount this share from my raspberry pi. Relevant info (let me know if I miss anything):

$this->bbcode_second_pass_code('', '#uname -a
Linux rpi 3.10.33-1-ARCH #1 PREEMPT Sat Mar 8 02:21:59 MST 2014 armv6l GNU/Linux

# mount /mnt/smb
mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
')

the contents of my fstab (commented out lines show the other things I've tried):
$this->bbcode_second_pass_code('', '#//192.168.0.1/sharename /mnt/smb cifs rw,username=admin,noauto,nounix,sec=ntlm,password=realpassword 0 0
#//192.168.0.1/sharename /mnt/smb cifs users,nofail,rw,sec=ntlm,guest 0 0
#//192.168.0.1/sharename /mnt/smb cifs users,nofail,rw,guest 0 0
#//192.168.0.1/sharename /mnt/smb cifs users,comment=systemd.automount,nofail,rw,guest 0 0
#//192.168.0.1/sharename /mnt/smb cifs guest 0 0
#//192.168.0.1/sharename /mnt/smb cifs user=admin,pass=realpassword,uid=1000,gid=100,domain=WORKGROUP,rw 0 0
#//192.168.0.1/sharename /mnt/smb cifs user=admin,pass=realpassword,uid=1000,gid=100,domain=WORKGROUP,sec=ntlm,rw 0 0
#//192.168.0.1/sharename /mnt/smb cifs guest,x-systemd.automount,uid=1000,gid=100 0 0
//192.168.0.1/sharename /mnt/smb cifs user=admin,pass=realpassword,x-systemd.automount,uid=1000,gid=100 0 0
')

The share is accessible fully guest accessible so shouldn't need a password, but the only way my housemate was able to mount it from his Debian system was the following:
$this->bbcode_second_pass_code('', '#mount -t cifs -o sec=ntlm,username=admin,password=realpassword //192.168.0.1/sharename /mnt/mountpoint')
(which also doesn't work for me).

here's what smbclient has to say about the existence of said share:
$this->bbcode_second_pass_code('', '# smbclient -L 192.168.0.1
smbclient: Can't load /etc/samba/smb.conf - run testparm to debug it
Enter piuser's password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.13]

Sharename Type Comment
--------- ---- -------
sharename Disk read:all-no password;write:all-no password
IPC$ IPC IPC Service (readyshare)
ADMIN$ IPC IPC Service (readyshare)
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.13]

Server Comment
--------- -------
READYSHARE readyshare

Workgroup Master
--------- -------
WORKGROUP READYSHARE
')

pacman query on cifs-utils:
$this->bbcode_second_pass_code('', '# pacman -Qi cifs-utils
Name : cifs-utils
Version : 6.4-1
Description : CIFS filesystem user-space tools
Architecture : armv6h
URL : http://wiki.samba.org/index.php/LinuxCIFS_utils
Licenses : GPL
Groups : None
Provides : None
Depends On : libcap-ng keyutils krb5 talloc libwbclient pam
Optional Deps : None
Required By : smbclient
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 217.00 KiB
Packager : Arch Linux ARM Build System <builder+xu4@archlinuxarm.org>
Build Date : Tue 13 Jan 2015 02:28:49 PM GMT
Install Date : Sat 14 Mar 2015 11:04:43 AM GMT
Install Reason : Explicitly installed
Install Script : No
Validated By : SHA256 Sum
')

I'm really sorry if the answer is obvious; all I've been able to find I have tried.

TIA :/

[moonman]

Are you fully up to to date? Your kernel seems really old. Did you mount /boot?

[lhacky]

Gah! Now you mention it, I remember having other problems where something like that was the solution. I never remember to mount /boot; because I always blythely follow "all you need to do to upgrade your system is pacman -Syu" (and reboot). Will look into it when i get home and let you know, thank you!

[lhacky]

Oh My God.

Well that was painful, but was eventually solved. In case anyone as special as me ever comes across exactly the same set of problems:

1) ensure boot partition is mounted when updating
2) if you're already ballsed that up, see viewtopic.php?f=33&t=6049 to copy the right kernel into the right place
3) reboot
4) the line in fstab looks like this:
$this->bbcode_second_pass_code('', '//192.168.0.1/sharename /mnt/smb cifs users,nofail,rw,sec=ntlm,guest 0 0
')

(not sure if sec=ntlm is needed if I'm logging in as guest, but anyway it works).