Jump to content

Recommended Posts

Posted

I'm not sure whether this is the correct place. Sorry if it isn't and please move it to where it belongs - thanks!

 

The problem is:

in our community (forum.iobroker.net) came up problems with mounting to a nas by cifs.

 

ioBroker is a smart home management, and a new module ("adapter") has been designed to provide automated backups to a nas.

in most cases this works fine, but on some platforms with armbian it fails with the message:

cifs filesystem not supported by the system

I'm not that linux crack, but i tried to find out what could cause this, I found at this site

https://www.linuxquestions.org/question ... 175593855/

some help.

 

In all versions the message mentioned above occured 

/proc/filesystems

didn't contain cifs

 

in the versions the backup worked, cifs was included.

 

 

At the moment we have confirmed it at orangePi plus2e (ARMBIAN 5.38 stable Ubuntu 16.04.5 LTS 4.14.4-sunxi) and I could reproduce it on a Rock64 (nightly Ubuntu 16.04.5 LTS 4.4.131-rk3328) ( I know it's nighly!!)

The platforms will have different age of images, and the users will not have updated/upgraded

 

It seems that the problem occurs only at Ubuntu based images (cifs-utils already installed and at newest version), not at Debian based.

 

on A Tinkerboard Ubuntu image (Ubuntu 16.04.5 LTS 4.4.120-rockchip) all is ok, so it is not at all ubuntu images.

 

calling:

sudo modprobe cifs

on my rock64 installation, the response was

modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.131-rk3328/modules.dep.bin'
modprobe: FATAL: Module cifs not found in directory /lib/modules/4.4.131-rk3328

 

 

Is this a common issue and known?

And the more imortant question:

What can be done?

 

thanks for every help in advance

Rainer

Posted
On 8/20/2018 at 5:37 PM, Homoran said:

http://ix.io/1kLX
 

Is this what you wanted to have???

 

Yep. What happens if you call 'sudo depmod'? If it succeeds then another time 'sudo modprobe cifs' would be interesting.

 

On Rock64 the cifs module should be built as module and therefore modprobe should work. Unfortunately our settings are not consistent accross kernels:

macbookpro-tk:kernel tk$ egrep "CONFIG_CIFS |CONFIG_CIFS=" * | grep -v 'CONFIG_CIFS=m'
linux-mvebu-dev.config:CONFIG_CIFS=y
linux-mvebu-next.config:CONFIG_CIFS=y
linux-mvebu64-dev.config:# CONFIG_CIFS is not set
linux-mvebu64-next.config:# CONFIG_CIFS is not set
linux-odroidc1-next.config:# CONFIG_CIFS is not set
linux-qcomlt-default.config:# CONFIG_CIFS is not set
linux-rockchip-dev.config:CONFIG_CIFS=y
linux-rockchip-next.config:CONFIG_CIFS=y
linux-s5p6818-default.config:# CONFIG_CIFS is not set
linux-sun4i-default.config:CONFIG_CIFS=y
linux-sun5i-default.config:CONFIG_CIFS=y
linux-sun7i-default.config:CONFIG_CIFS=y
linux-sun8i-default.config:CONFIG_CIFS=y
linux-udoo-default.config:# CONFIG_CIFS is not set

 

Posted

In the meanwhile something happens.

we do not know what and why but....

 

a lot of reboots and tries later it works (at both installations)

 

many times I did a reboot and immediately looked into /proc/filesystems -> no cifs.

tried to install cifs-utils -> already latest version

 

trying to mount with

 mount -t cifs -o user=meinUser,password=meinPasswort,rw,file_mode=0777,dir_mode=0777,vers=1.0 //192.168.178.123/Backups/ioBroker/Rock01 /opt/iobroker/backups

always failed.

 

Changing mod and ver no success.

 

But suddenly it worked.

looking into /proc/filesystems -> cifs included at the last row.

And all went well :o

 

 

On the OPi install a try to change the smb package via armbian-config at 3.-Party-Software didn't help.

the apt purge cifs-utils and apt install cifs-utils again helped.

 

At that point all went well again.

 

 

Thank you for your help.

I personally do not like healing by speaking a spell - I would like to know what went wrong.

 

In the next days I will look at my Installations B)

installs.thumb.png.66368145132ba7a006c34332fd638403.png

 

whether I can find another System with this Issue. My yesterday newly installed OPi+2e with ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.18-sunxi went well.

 

Or will it make sense to try to find anything in the (now working) Installation?

 

Greetings

Rainer

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines