mount.cifs "mount error 20 = Not a directory"
mebe
i just bought a lan drive with a smb server running on it.
As soon as it is connected to the network, i am able to add and browse
the network folders using Konqueror (System->Remote Places).
But if i try to mount it using
mount -t cifs //x.x.x.x/audio /mnt/audio
i get the error message:
mount error 20 = Not a directory
Now the question is: How can i mount the land disk?
Please let me know if you have any ideas...
Don Raboud
Do you have a directory 'audio' under /mnt?
This mount point needs to exist. The mount command will not create it for
you.
--
Don
mebe
yes, there's a 'audio' directory at /mnt.
i really don't understand what's wrong here, so please let me know if
you have any other ideas what could cause the problem or how to solve
it.
Thanks.
Don Raboud
Mebe, Please always quote what you are responding to (enough to get the
point across at least). I know its not the default in Google groups, but
that is really beside the point.
Besides, if you are replying to someone and don't bother quoting anything...
then by default you are topposting.
In your case, can you try adding the --verbose option to your mount command
and see if any other information is given.
--
Don
mebe
> Mebe, Please always quote what you are responding to (enough to get the
> point across at least). I know its not the default in Google groups, but
> that is really beside the point.
>
> Besides, if you are replying to someone and don't bother quoting anything...
> then by default you are topposting.
Don, thx for the info.
> In your case, can you try adding the --verbose option to your mount command
> and see if any other information is given.
This nas drives me crazy. I still ain't able to mount it on the shell,
however i can easily access it through konqueror's 'system->remote
places' folder.
Here's the verbose output:
# mount -t cifs //10.10.0.2/Audio /mnt --verbose -o guest,ro
parsing options: ro,guest
mount.cifs kernel mount options unc=//
10.10.0.2\Audio,ip=10.10.0.2,user=root,ver=1,ro,guest
mount error 20 = Not a directory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
Here's also the output of dmesg | tail:
CIFS VFS: cifs_mount failed w/return code = -112
CIFS VFS: Send error in SETFSUnixInfo = -5
CIFS VFS: Send error in SETFSUnixInfo = -5
CIFS VFS: Send error in SETFSUnixInfo = -5
SFW2-OUT-ERROR IN= OUT=ath0 SRC=10.10.0.8 DST=72.14.221.91 LEN=52
TOS=0x00 PREC=0x00 TTL=64 ID=9004 DF PROTO=TCP SPT=21892 DPT=80
WINDOW=865 RES=0x00 ACK FIN URGP=0 OPT (0101080A00019037459EA87E)
CIFS VFS: Send error in SETFSUnixInfo = -5
CIFS VFS: Send error in SETFSUnixInfo = -5
SFW2-OUT-ERROR IN= OUT=ath0 SRC=10.10.0.8 DST=10.10.0.2 LEN=40
TOS=0x00 PREC=0x00 TTL=64 ID=62173 DF PROTO=TCP SPT=1429 DPT=139
WINDOW=9648 RES=0x00 ACK FIN URGP=0
CIFS VFS: Send error in SETFSUnixInfo = -5
CIFS VFS: Send error in SETFSUnixInfo = -5
Do you have any ideas how to interpret this messages?
I've tried to disable ipv6, but without success, tried smbtree but did
not get any (usefull) output (even with debuglevel set to maximum).
I'm running out of ideas how to get this landrive mounted, so please
let me know if you have any ideas.
Don Raboud
> This nas drives me crazy. I still ain't able to mount it on the shell,
> however i can easily access it through konqueror's 'system->remote
> places' folder.
Konqueror uses CFIS differently. Not the same as mounting.
> Here's the verbose output:
> # mount -t cifs //10.10.0.2/Audio /mnt --verbose -o guest,ro
> parsing options: ro,guest
>
> mount.cifs kernel mount options unc=//
> 10.10.0.2\Audio,ip=10.10.0.2,user=root,ver=1,ro,guest
Don't know if this is important, but
10.10.0.2/Audio
became
10.10.0.2\Audio
(slash got changed around in the output). There was another thread here
recently with similar behavior. You might wnat to check that out.
> mount error 20 = Not a directory
> Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
>
> Here's also the output of dmesg | tail:
> CIFS VFS: cifs_mount failed w/return code = -112
> CIFS VFS: Send error in SETFSUnixInfo = -5
> CIFS VFS: Send error in SETFSUnixInfo = -5
> CIFS VFS: Send error in SETFSUnixInfo = -5
You could google for these error messages. I have no idea.
> SFW2-OUT-ERROR IN= OUT=ath0 SRC=10.10.0.8 DST=72.14.221.91 LEN=52
> TOS=0x00 PREC=0x00 TTL=64 ID=9004 DF PROTO=TCP SPT=21892 DPT=80
> WINDOW=865 RES=0x00 ACK FIN URGP=0 OPT (0101080A00019037459EA87E)
Your IP address is 10.10.0.8, correct?
> CIFS VFS: Send error in SETFSUnixInfo = -5
> CIFS VFS: Send error in SETFSUnixInfo = -5
> SFW2-OUT-ERROR IN= OUT=ath0 SRC=10.10.0.8 DST=10.10.0.2 LEN=40
> TOS=0x00 PREC=0x00 TTL=64 ID=62173 DF PROTO=TCP SPT=1429 DPT=139
> WINDOW=9648 RES=0x00 ACK FIN URGP=0
OK. Here you're trying to contact 10.10.0.2 but there is an error from the
firewall.
Have you tried this with the firewall off, just to be sure?
Is your interface name really "ath0"? What is the output from
"/sbin/ifconfig"?
> Do you have any ideas how to interpret this messages?
Very little, but see above.
> I've tried to disable ipv6, but without success, tried smbtree but did
> not get any (usefull) output (even with debuglevel set to maximum).
> I'm running out of ideas how to get this landrive mounted, so please
> let me know if you have any ideas.
Shot in the dark, but CIFS doesn't work quite the same with all versions of
Windows, particularly Windows 98. Maybe this device is emulating the Win
98 protocols.
If you Google along these lines you may find some advice about connecting to
Win 98 machines which may be of some help. Other than that I am not sure
what to suggest.
--
Don
mebe
> Konqueror uses CFIS differently. Not the same as mounting.
Don, thank you verry much for the quick support!
> Don't know if this is important, but
> 10.10.0.2/Audio
>
> became
>
> 10.10.0.2\Audio
>
> (slash got changed around in the output). There was another thread here
> recently with similar behavior. You might wnat to check that out.
I've noticed that the verbose output is the same, regardless if i
use / or \ in the path name, so i assumed it doesn't matter, but i'll
try to find the other thread.
> You could google for these error messages. I have no idea.
Sorry, i havn't had the time to google about it yet.
> Your IP address is 10.10.0.8, correct?
Yes it is.
> OK. Here you're trying to contact 10.10.0.2 but there is an error from the
> firewall.
/ath0 was assigned to internal zone, so the firewall "shold" not have
any impact, but i disabled the firewall anyway.
> Have you tried this with the firewall off, just to be sure?
> Is your interface name really "ath0"? What is the output from
> "/sbin/ifconfig"?
I disabled the firewall, but still have the same errors. The name of
the network interface (which seems to work well in all other
situations) is "ath0" (Its the wireless network adapter of an intel
mac mini. I suppose the name comes from the madwifi driver)
ifconfig displays the following:
ath0 Link encap:Ethernet HWaddr 00:16:CB:BF:5F:E5
inet addr:10.10.0.8 Bcast:10.10.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25424 errors:0 dropped:0 overruns:0 frame:0
TX packets:13106 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:28636531 (27.3 Mb) TX bytes:1157256 (1.1 Mb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:84 errors:0 dropped:0 overruns:0 frame:0
TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4960 (4.8 Kb) TX bytes:4960 (4.8 Kb)
wifi0 Link encap:UNSPEC HWaddr 00-16-CB-BF-5F-
E5-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:795592 errors:0 dropped:0 overruns:0 frame:216685
TX packets:16142 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:95198378 (90.7 Mb) TX bytes:1709269 (1.6 Mb)
Interrupt:16
> Shot in the dark, butCIFSdoesn't work quite the same with all versions of
> Windows, particularly Windows 98. Maybe this device is emulating the Win
> 98 protocols.
> If you Google along these lines you may find some advice about connecting to
> Win 98 machines which may be of some help. Other than that I am not sure
> what to suggest.
Thanks for the info, i'll try to find some informations about mounting
a windows 98 share.