Mount error cifs filesystem not supported by the system mount error 19 no such device - Исправление ошибок и поиск оптимальных решений проблем

i try to mount a OneDrive Folder to my Linuxserver. However, as i try mout.cifs with XXX beeing the correct values…

root@XXX:~# mount.cifs //onedrive.live.com/about/en-us/signin/ /usr/plex/share -o user='XXX',password='XXX'

…it returns:

mount error: cifs filesystem not supported by the system
mount error(19): No such device

I installed cifs-utils without any errors. (version 2:6.8-1)

My dear friend google lead me to some websites telling me to check some things:

zgrep -i cifs /proc/config.gz

returns nothing.

modprobe cifs

returns:

modprobe: ERROR: ../libkmod/libkmod.c:514 lookup_builtin_file() could not open builtin file '/lib/modules/4.15.0/modules.builtin.bin'
modprobe: FATAL: Module cifs not found in directory /lib/modules/4.15.0

I tried updating packages, reinstalling cifs-utils, upgrading the kernel, rebooting and recompiling the kernel. Nothing worked for me.

uname -r

returns:

4.15.0

lsb_release -a

returns:

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:        18.04
Codename:       bionic

6.
the samba-service is up and running.

service smbd status

returns

● smbd.service - Samba SMB Daemon
   Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-02-03 05:19:03 CET; 29min ago
     Docs: man:smbd(8)
           man:samba(7)
           man:smb.conf(5)
 Main PID: 561 (smbd)
   Status: "smbd: ready to serve connections..."
    Tasks: 5 (limit: 165)
   CGroup: /system.slice/smbd.service
           ├─ 561 /usr/sbin/smbd --foreground --no-process-group
           ├─ 662 /usr/sbin/smbd --foreground --no-process-group
           ├─ 664 /usr/sbin/smbd --foreground --no-process-group
           ├─ 768 /usr/sbin/smbd --foreground --no-process-group
           └─1570 /usr/sbin/smbd --foreground --no-process-group

Feb 03 05:46:52 XXX.net smbd[2050]: pam_unix(samba:session): session closed for user nobody
Feb 03 05:46:52 XXX.net smbd[2052]: pam_unix(samba:session): session closed for user nobody
Feb 03 05:46:53 XXX.net smbd[2054]: pam_unix(samba:session): session closed for user nobody
Feb 03 05:46:56 XXX.net smbd[2055]: pam_unix(samba:session): session closed for user nobody
Feb 03 05:46:56 XXX.net smbd[2056]: pam_unix(samba:session): session closed for user nobody
Feb 03 05:46:58 XXX.net smbd[2057]: pam_unix(samba:session): session closed for user nobody
Feb 03 05:47:11 XXX.net smbd[2059]: pam_unix(samba:session): session closed for user nobody
Feb 03 05:47:15 XXX.net smbd[2064]: pam_unix(samba:session): session closed for user nobody
Feb 03 05:48:15 XXX.net smbd[2073]: pam_unix(samba:session): session closed for user nobody
Feb 03 05:48:20 XXX.net smbd[2076]: pam_unix(samba:session): session closed for user nobody

However, the last lines seem a bit strange to me.

So finally, i am left with no idear. I searched the web for hours but the only soloution i could find was recompilling the kernel. Obvoiusly that did not work for me.

I hope someone can help me. If you need more information, please give me the exact command line as i am relatively new to linux.

Thank you in advance!

Greeting
Smallmountains

PS: Please excuse my bad english. Thanks.

———UPDATE———-

The command

find /lib/modules/ -name cifs.ko

returs a buch of kernal names:

/lib/modules/4.15.0-1019-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1036-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1019-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-33-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1019-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1011-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-38-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1009-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1022-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1006-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1021-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1008-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1012-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1023-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1025-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1024-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-39-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-42-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1020-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-43-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1025-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-23-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1008-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1012-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1028-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1004-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1031-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1023-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1025-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-30-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1027-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1009-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1028-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1024-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1015-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1016-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-32-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1029-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-33-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1030-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1017-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1023-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1018-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1035-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1007-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-29-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1012-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1009-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1021-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1006-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1021-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1014-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1028-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1015-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-32-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1017-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-36-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1026-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1013-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1021-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-22-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1027-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-23-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1010-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1021-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1019-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1017-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-36-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1010-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1018-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1011-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-29-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1007-oracle/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-38-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-39-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1031-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1032-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-20-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1020-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1008-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1010-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1014-azure/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-42-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1030-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-24-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-43-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1016-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-30-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-34-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-24-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1018-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-22-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1025-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1023-aws/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-20-lowlatency/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1009-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-34-generic/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1026-kvm/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1026-gcp/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1017-oem/kernel/fs/cifs/cifs.ko
/lib/modules/4.15.0-1013-azure/kernel/fs/cifs/cifs.ko

Which one should i choose? And do i use the….

GRUB_DEFAULT='Example GNU/Linux distribution'

…in the file…

/etc/default/grub

to choose what kernal to boot into? Remember, i do have acces to the server only via ssh after the boot process ist sucessfull. I cannot choose a kernal during boot on a screen.

Thank you in advance.
Greetings: Smallmountain

Источник

Sometime ago I used to mount shared folders from my windows computer using the command :

sudo mount.cifs //computer/folder /mnt -o username=user

However now it bugs and yields :

mount error : cifs filesystem not supported by the system mount

error(19): No such device

Any idea on what might have happened in the meanwhile that prevents it from working ?

The package cifs-utils is installed..

zgrep -i cifs /proc/config.gz

Returns :

CONFIG_CIFS=m
CONFIG_CIFS_STATS=y
#CONFIG_CIFS_STATS2 is not set
CONFIG_CIFS_WEAK_PW_HASH=y
...

All yes except for STATS2 and DEBUG basically

asked Aug 28, 2016 at 0:09

ChiseledAbsChiseledAbs

2,13510 gold badges26 silver badges56 bronze badges

CONFIG_CIFS=m means the CIFS functionality is compiled into a kernel module.
If the cifs module isn’t loaded after a reboot, you can append a line

cifs

to the file /etc/modules. The file lists modules which will be loaded automatically at boot time. To check if the module is already loaded type:

lsmod | grep cifs

If you don’t see ‘cifs’ in the output, it isn’t loaded. To load it manually without a reboot:

modprobe cifs

answered Aug 29, 2016 at 6:49

I had a similar problem, the module location was changed because of rolling release arch distribution, so path was different. Reboot

jimmij

44.9k18 gold badges118 silver badges135 bronze badges

answered May 8, 2019 at 9:35

user351921user351921

1011 silver badge2 bronze badges

Here is yet another tip for mounting a Windows share:

sudo mount -t drvfs '\your computer IP address or computername hereshare'  /mnt

The key is to use the single quotes for the source drive.

Greenonline

1,7317 gold badges16 silver badges21 bronze badges

answered Oct 15, 2021 at 4:43

your Ubuntu can not find cifs in filesystem. it is not necessary to add cifs.ko to kernel. you can treat it in menuconfig in kernel and choose cifs in filesystem. after that copy the new zImage.

finally

sudo mount -t cifs //computer ip/sharedfolder /mnt

Archemar

30.6k18 gold badges69 silver badges104 bronze badges

answered Sep 30, 2021 at 8:39

Источник

Altlinux p7 64, cifs установлен

fstab:

//192.168.0.100/doc /media/doc cifs username=director,password=gznyjdsdjlbntkm,auto,nounix,noperm 4 4

mount -a 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) 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)
странно както. подскажите где ошибка

Записан

Altlinux p7 64, cifs установлен

Это вы как определили?

mount error: cifs filesystem not supported by the system
mount error(19): No such device

Показывайте вывод

rpm -V cifs-utils modprobe cifs dmesg | tail grep CIFS /var/log/messages | tail

Записан

Андрей Черепанов (cas@)

rpm -V cifs-utils [root@director ~]# apt-get install cifs-utils Чтение списков пакетов... Завершено Построение дерева зависимостей... Завершено Последняя версия cifs-utils уже установлена. 0 будет обновлено, 0 новых установлено, 0 пакетов будет удалено и 0 не будет обновлено. [root@director ~]# modprobe cifs modprobe: FATAL: Module etercifs not found. modprobe: ERROR: Error running install command for cifs modprobe: ERROR: could not insert 'cifs': Operation not permitted [root@director ~]# dmesg | tail [ 24.563428] wlp4s0: authenticate with d8:50:e6:93:bc:88 [ 24.584679] wlp4s0: send auth to d8:50:e6:93:bc:88 (try 1/3) [ 24.586743] wlp4s0: authenticated [ 24.590903] wlp4s0: associate with d8:50:e6:93:bc:88 (try 1/3) [ 24.594542] wlp4s0: RX AssocResp from d8:50:e6:93:bc:88 (capab=0x411 status=0 aid=4) [ 24.594592] wlp4s0: associated [ 24.594628] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [ 41.423229] fuse init (API version 7.22) [ 177.235127] FS-Cache: Loaded [ 177.249707] Key type dns_resolver registered [root@director ~]# grep CIFS /var/log/messages | tail

Записан

бновлено.
[root@director ~]# modprobe cifs
modprobe: FATAL: Module etercifs not found.
modprobe: ERROR: Error running install command for cifs
modprobe: ERROR: could not insert ‘cifs’: Operation not permitted

А что у вас за ядро?

# uname -r 3.10.11-std-def-alt1 [root@cas ~]# ll /lib/modules/$(uname -r)/kernel/fs/cifs/cifs.ko -rw-r--r-- 1 root root 721418 сен 12 13:14 /lib/modules/3.10.11-std-def-alt1/kernel/fs/cifs/cifs.ko

Записан

Андрей Черепанов (cas@)

ядро уже посмотреть не могу, т.к. появились аппаратные проблемы, сейчас ставлю P6, но я всетаки надеюсь на соем ноуте установить P7/

Записан

Сейчас словил

[root@srv sysconfig]# modprobe cifs modprobe: FATAL: Module etercifs not found. modprobe: ERROR: Error running install command for cifs modprobe: ERROR: could not insert 'cifs': Operation not permitted [root@srv sysconfig]# rpm -qa | grep cifs etercifs-5.4.8-alt1 cifs-utils-5.7-alt2 [root@srv sysconfig]# uname -r 3.12.15-std-def-alt1Что делать?

Записан

Сейчас словил
[root@srv sysconfig]# modprobe cifs modprobe: FATAL: Module etercifs not found. modprobe: ERROR: Error running install command for cifs modprobe: ERROR: could not insert 'cifs': Operation not permitted [root@srv sysconfig]# rpm -qa | grep cifs etercifs-5.4.8-alt1 cifs-utils-5.7-alt2 [root@srv sysconfig]# uname -r 3.12.15-std-def-alt1Что делать?

Пересобирать etercifs под новое ядро при любом обновлении ядра.

Записан

Андрей Черепанов (cas@)

Уже понял, только заголовки ядра уже для 3.12.16
Вечером перегружу сервер уже с новым ядром

Записан

С этими заголовками непонятная ситуация.
Стояло ядро 3.10. Ставлю заголовки модулей ядра — ставятся для ядра 3.14. Для 3.10 поставить не удалось.
Ладно, обновил ядро до 3.14. Пытаюсь собирать etercifs — ошибки какие-то слишком мало переменных куда-то передается. В репах kernel-souces-etercifs- 3.12 самый последний, для 3.14 нету. Как быть.

Записан

Андрей Черепанов (cas@)

Странно. cifs.ko ведь в kernel-image. У меня, в p6 правда, cifs работает без etercifs.

Записан

Спросить у Этерсофт.

Спросить когда будет под 3.14?
А откатить ядро и таки найти заголовки для 3.10 возможно?

Странно. cifs.ko ведь в kernel-image. У меня, в p6 правда, cifs работает без etercifs.

Дык он работает, если ethercifs не установлен. если установлен, то, видимо, модуль cifs заменяется на тот, что требует еще модуль ethercifs, которого в системе то нету, и который надо собирать командой service etercifs build (каждый раз при обновлении ядра?)

Записан

Действительно, виноват etercifs. У меня Simply 7.04. Пути прописаны в fstab, но пока не удалил этот etercifs, не хотели монтироваться ни в какую.

Записан

Источник

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):

Code: Select all: #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):

Code: Select all: #//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:

Code: Select all: #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:

Code: Select all: # 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:

Code: Select all: # 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 :/

Источник

First off, I apologize if this issue has already been covered. I could not find any references on the forums that worked for my situation.

When trying to mount a Samba share on my Archlinux host, I receive the following error:

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)

Now, some back story… My laptop runs Archlinux and I am trying to connect to a Samba share on my Raspberry Pi (running Archlinux ARM). Here is the Raspberry Pi’s ‘smb.conf’ settings for the share in question:

security = user
...
[shares]
comment = Network Shares
path = /path/to/share
browsable = yes
writable = yes
guest ok = yes
guest user = <myguestacct>
guest only = yes

<myguestacct> exists in the ‘smbpasswd’ database as well as the Raspberry Pi’s ‘/etc/passwd’ file. The folder on the Raspberry Pi has the following permissions: drwxrwxrwx. It is a folder located on an external USB harddrive formatted in NTFS. ‘ntfs-3g’ is installed on the Raspberry Pi and my laptop.

My fiance is using elementaryOS on her laptop and I was able to mount the same share by using the following command:

sudo mount -t cifs //<ipaddress>/shares /mnt/netshares -o guest

Using the same command on my laptop produces the error shown above. The only access issue with this share is from my laptop AND in the terminal. I can access the share from my fiance’s laptop via her file manager and terminal, as well as from my laptop via Thunar. ‘/mnt/netshares’ is created on my laptop and also has the following permissions: drwxrwxrwx.

I have tried manipulating the ‘mount’ command to get it to mount, but to no avail. Adding ‘sec=ntlm’ to the end of the options did not work. I tried using ‘mount.cifs’ instead of ‘mount’ and that didn’t work. I also tried to connect to another, secured, share on the Raspberry Pi via the terminal; I supplied my credentials, and it failed the same way. Yet again, I have no access issues with the secured share via Thunar on my laptop; or on my fiance’s laptop. Any help is appreciated. I’d rather not change my settings drastically since it only affects me connecting on my laptop via the terminal, however, I want to get people’s thoughts on the matter to see if I’m overlooking something trivial.

Let me know if I need to post any other configs or outputs. Thanks.

P.S. I hope I’m not wasting anyone else’s time. This one just has me completely stumped

Last edited by Orlin (2013-10-16 10:42:51)

Источник