You are not logged in.
I have a home server running ArchLinux, hosting an SMB share. My client box is also ArchLinux, both are up to date, running Linux-ck 3.9.2-2-ck. Prior to rebooting both machines around twenty minutes ago, the share mounted fine for months.
Here is the extent of the "verbosity" I receive from mount:
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Here is my fstab:
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# UUID=71066ae2-40ec-4125-9db7-d04b6a04f712
UUID=71066ae2-40ec-4125-9db7-d04b6a04f712 / ext4 rw,relatime,data=ordered 0 2
# UUID=172faa6a-9cca-4d9e-a0b9-a5da3ea81922
UUID=172faa6a-9cca-4d9e-a0b9-a5da3ea81922 /boot ext2 rw,relatime 0 2
# UUID=65023815-33fc-4ebd-b245-65683201fbcf
UUID=65023815-33fc-4ebd-b245-65683201fbcf /home ext4 rw,relatime,data=ordered 0 2
UUID=1a23d461-fa2b-4ea4-8e58-e7efba3f3bed /media/Storage ext3 rw 0 2
//ARRAY/Array /media/Array cifs credentials=/home/xaero/.smbpasswd,iocharset=utf8,uid=1000,gid=1000,nounix,sec=ntlm 0 0
I have tried any number of different options on that final line defining this share now:
I have tried //array/array (which is what it was originally) and //ARRAY/Array (which is case-sensitive) as well as any combination of using my credentials file (which used to work) or user=,pass= as well changing my credentials file to use quotation marks around my password as it has special characters. I've also read of using sec=ntlm fixing mount issues, but in my case it did not. I'm kind of scratching my head here as passing --verbose to mount yields zero additional information... the uid and gid entries were necessary in the past to mount this share, however I have tried both with and without them, to no avail.
I rely on SMB in lieu of sshfs as there isn't a stable sshfs implementation for Windows users, which there are some on my network; I also find for whatever reason SMB happens to be faster.
Last edited by Xaero252 (2013-05-19 21:45:30)
Offline
Did you jsut do about a month's worth up updates? Because samba changed versions, so things need to be reconfigured if so.
Offline
I'm not exactly sure what fixed this... I looked at the configuration file to make sure I hadn't missed it being updated, and it was in the new format; everything setup correctly (I remember having to edit it not long ago to fix something, probably for the update which you mentioned) I reverted my fstab back to the way it was before (making backups is good) and restarted the smbd on the server numerous times... at some point it just started working again. I wish I had a more concrete answer for documentation sake, but I was literally just rebooting/restarting services in desperation with little to no config hacking between and suddenly things clicked. I'm also no longer running the sec=ntlm option..
Thanks for reminding me to check my config though, when I updated I had forgotten to enable user restriction (guest was enabled, and certain directories weren't user-specific)
Offline