[SOLVED] how to mount cifs ??

[dony71]

I follow this wiki https://github.com/RMerl/asuswrt-merlin/wiki/Mounting-remote-CIFS-shares
but get this error below

mount: can't find \\10.168.1.69\backup /tmp/mnt/NAS/backup in /etc/fstab

Then I make /jffs/scripts/init-start

#!/bin/sh
mkdir /tmp/mnt/NAS
mkdir /tmp/mnt/NAS/backup

and /jffs/configs/fstab

\\10.168.1.69\backup /tmp/mnt/NAS/backup cifs username=x,password=x 0 0

and after reboot /etc/fstab content shows

\\10.168.1.69\backup /tmp/mnt/NAS/backup cifs username=x,password=x 0 0

However executing

mount \\\\10.168.1.69\\backup\ /tmp/mnt/NAS/backup -t cifs -o "username=x,password=x"

still give error

mount: can't find \\10.168.1.69\backup /tmp/mnt/NAS/backup in /etc/fstab

what could be wrong??

 

[dony71]

I try

mount \\\\10.168.1.69\\backup /tmp/mnt/NAS/backup -t cifs -o "username=x,password=x"

now I get error message

mount: mounting \\10.168.1.69\backup on /tmp/mnt/NAS/backup failed: No such device

 

[ColinTaylor]

Router model? Firmware version?

 

[dony71]

Router model? Firmware version?

RT-AC68U Firmware Version: 384.14

 

[ColinTaylor]

mount \\\\10.168.1.69\\backup /tmp/mnt/NAS/backup -t cifs -o "username=x,password=x"

now I get error message

mount: mounting \\10.168.1.69\backup on /tmp/mnt/NAS/backup failed: No such device

That error message usually means that you have mis-typed the first part. So either "10.168.1.69" is the wrong address or "backup" isn't a shared directory.

Are you sure "10.168.1.69"? It looks like that ought to be "192.168.1.69".

 

[dony71]

now I get error message

That error message usually means that you have mis-typed the first part. So either "10.168.1.69" is the wrong address or "backup" isn't a shared directory.

Are you sure "10.168.1.69"? It looks like that ought to be "192.168.1.69".

I can ping that IP address
I use router with openwrt before I switch to Asus and has no problem mounting that "backup" directory

 

[Salles]

I have not used the guide myself.
But Ioticed that your are missing the first part of the second commandline in the guide, "/cifs1".

If that could help...

 

[dony71]

I have not used the guide myself.
But Ioticed that your are missing the first part of the second commandline in the guide, "/cifs1".

If that could help...

my understanding is"/cifs1" the directory where it should be mounted. It should not matter the mounting location as long the directory exist. Am I wrong on this?


Sent from my iPhone using Tapatalk

 

[dony71]

anybody in this forum ever successfully mounting cifs on RT-AC68U router? I'm starting to suspect maybe the compiled firmware does not have cifs module in kernel.


Sent from my iPhone using Tapatalk

 

[ColinTaylor]

anybody in this forum ever successfully mounting cifs on RT-AC68U router? I'm starting to suspect maybe the compiled firmware does not have cifs module in kernel.

Yes many people have done that, myself included (on an RT-AC68U). I'm not using the latest firmware as you are so I can't say whether or not some sort of bug has crept in.

admin@RT-AC68U:/# mount \\\\192.168.1.10\\backup /cifs1 -t cifs -o "username=colin,password=xxxx"
admin@RT-AC68U:/# df -h /cifs1
Filesystem             Size  Used Avail Use% Mounted on
\\192.168.1.10\backup  877G  747G   86G  90% /cifs1

 

[dony71]

Yes many people have done that, myself included (on an RT-AC68U). I'm not using the latest firmware as you are so I can't say whether or not some sort of bug has crept in.

admin@RT-AC68U:/# mount \\\\192.168.1.10\\backup /cifs1 -t cifs -o "username=colin,password=xxxx"
admin@RT-AC68U:/# df -h /cifs1
Filesystem             Size  Used Avail Use% Mounted on
\\192.168.1.10\backup  877G  747G   86G  90% /cifs1

what firmware version are you using?
i will try same version to debug this problem


Sent from my iPhone using Tapatalk

 

[ColinTaylor]

I'm using John's firmware which is looks a lot different than the current Merlin as it is based on a much older code base. But you would need to install it by putting your router into recovery mode as you cannot flash it through the GUI.

If you suspect there's an issue with the current Merlin firmware I suggest you just go back one release as nobody has reported this problem before.

 

[dev_null]

I am having the same problem on 384.14.

It appears that 384.14 is missing cifs.ko, required to mount.

Issuing a "modprobe cifs" returns "modprobe: module cifs not found in modules.dep".

It was working on 384.13.

 

[dony71]

Yes many people have done that, myself included (on an RT-AC68U). I'm not using the latest firmware as you are so I can't say whether or not some sort of bug has crept in.

admin@RT-AC68U:/# mount \\\\192.168.1.10\\backup /cifs1 -t cifs -o "username=colin,password=xxxx"
admin@RT-AC68U:/# df -h /cifs1
Filesystem             Size  Used Avail Use% Mounted on
\\192.168.1.10\backup  877G  747G   86G  90% /cifs1

do you need to put something on fstab?
if yes, can you share your fstab?

 

[ColinTaylor]

You could try something like this in fstab:

\\192.168.1.10\backup /cifs1 cifs username=colin,password=xxxxx

But as noted in the wiki the mount point must already exist at boot up. If it doesn't then you would have to create one in an init-start script otherwise it will fail.

 

[dony71]

I am having the same problem on 384.14.

It appears that 384.14 is missing cifs.ko, required to mount.

Issuing a "modprobe cifs" returns "modprobe: module cifs not found in modules.dep".

It was working on 384.13.

yeah... cifs working on 384.13

 

[dev_null]

yeah... cifs working on 384.13

You may consider removing the [Solved] in the title because rolling back is really not a fix for a broken 384.14.

I posted in the 384.14 release thread, but apparently only you and I are the ones that found it broken, and it may be helpful to leave it "unsolved" so others can view this topic.

 

[RMerlin]

CIFS is an obsolete protocol that is being phased out. Mac dropped CIFS support last year, and Windows is also no longer supporting it out of the box.

 

[dev_null]

CIFS is an obsolete protocol that is being phased out. Mac dropped CIFS support last year, and Windows is also no longer supporting it out of the box.

That's fine, but up until 384.13 AsusWrt-Merlin supported this *nix mapping schema and now it has disappeared without being reported.

The only thing this thread is asking is "why doesn't it work for me on .14" to which I answered "because it's missing the functionality."

Is cifs support gone for good on AsusWrt-Merlin? If so, that should be added to the changelog. I know the OEM didn't (or hasn't) supported it, so it was helpful in some specific instances.

Cheers,

 

[dev_null]

Update: If anyone needs cifs in 384.14 - I extracted cifs.ko from the 384.13 image (/lib/modules/<kernelversion>/kernel/fs), placed it into it's own folder in jffs and issued an "insmod /path/to/cifs.ko" and it seems to work. Cheers,