Network Mount Bug?

[Rahat786786]

Hi,

Just updated to the new Vix image and can't seem to set up network mount.

I have installed Samba.

What happens is the network browser finds the drive (a external hdd connected to my router) and mounts it successfully. However, when I go to the recordings list, select locations and then click on the mounted drive it says something like autofs/... does not exist.

So it is mounting the drive but then saying the mount directory does not exist.

This was fully working in Hades, Zeus, Apollo and all other versions.

Any help please?

[ArowonA]

This post is not really going to help Rahat786786's issue, but it may be useful if the mount was actually tested before allowing you to save them.

[Huevos]

Have you restored a backup from a Hades image?

[abu baniaz]

If you have used a settings restore, there were two files that need to be replaced. Rob uploaded them as well as a telnet command by arrowna

[Rahat786786]

If you have used a settings restore, there were two files that need to be replaced. Rob uploaded them as well as a telnet command by arrowna


I did a completely fresh flash and install.

[Rahat786786]

Also, when mounting the green globe shows on the drive so I guess the link is active but for some reason it says doesnt exist when I click on it in locations.

[birdman]

I have installed Samba.POI: you only need Samba if you want an external system to access a file-system which is on the OpenVix system, so it's not relevant to what you are trying to do here.

[Rahat786786]

Ok so any idea on how I can get this sorted. When I flash back to Hades it works..

[abu baniaz]

Try this:

http://www.world-of-satellite.com/showthread.php?47613-Accessing-Root-amp-HDD-after-flash-of-3-2&p=371895&viewfull=1#post371895

[birdman]

What happens is the network browser finds the drive (a external hdd connected to my router) and mounts it successfully. However, when I go to the recordings list, select locations and then click on the mounted drive it says something like autofs/... does not exist.FWIW, I've just tried this on my box and it all worked OK. So I can't help much as to what is going wrong.

I'm assuming that you configured it to use "AUTOFS (mount as needed)"

Login to the box and see whether automount is running:
root@mbtwin:/media# ps -ef | grep auto
root 447 1 0 17:57 ? 00:00:00 automount
root 704 689 0 18:00 pts/0 00:00:00 grep autoAssuming it is (if it isn't then that would be a problem), check that it has the right files open (you need the pid for the process - which is the first number on the ps line for automount):

root@mbtwin:/media# ls -l /proc/447/fd
lrwx------ 1 root root 64 Sep 12 18:00 0 -> /dev/null
lrwx------ 1 root root 64 Sep 12 18:00 1 -> /dev/null
lr-x------ 1 root root 64 Sep 12 18:00 10 -> /media/autofs
lrwx------ 1 root root 64 Sep 12 18:00 2 -> /dev/null
lr-x------ 1 root root 64 Sep 12 18:00 3 -> /dev/autofs
lr-x------ 1 root root 64 Sep 12 18:00 4 -> pipe:[1598]
lrwx------ 1 root root 64 Sep 12 18:00 5 -> socket:[1814]
l-wx------ 1 root root 64 Sep 12 18:00 6 -> pipe:[1598]
lr-x------ 1 root root 64 Sep 12 18:00 7 -> pipe:[1599]
l-wx------ 1 root root 64 Sep 12 18:00 8 -> pipe:[1599]
lrwx------ 1 root root 64 Sep 12 18:00 9 -> /run/autofs.fifo-media-autofs

[Rahat786786]

Try this:

http://www.world-of-satellite.com/showthread.php?47613-Accessing-Root-amp-HDD-after-flash-of-3-2&p=371895&viewfull=1#post371895

That thread goes over how to get samba running. Mine is already running.

Also, birdman sorry I am a bit out of my depth here. Can you please explain in laymen terms?

Help really appreciated.

Thanks

[birdman]

That thread goes over how to get samba running. Mine is already running....and is irrelevant to the problem at hand, as Samba is an SMB/CIFS server process and you have a problem with an NFS client process.


Also, birdman sorry I am a bit out of my depth here. Can you please explain in laymen terms?Hmmm - I was trying to....

Q1 - do you know how/are you able to login to your box and get a command line prompt?

[Rahat786786]

Thanks for your help, really appreciated.

I managed to fix the problem. I did a reflash of router firmware and mounted the drive and it worked!

[Rahat786786]

Hmm, does seem like a bug afterall.

I just upgraded today to a ASUS AC3200 router and connected my storage. I can map it to windows etc but again get the error message in Vix.

[Rahat786786]

FIXED! Found an old post where this was recommended


Had to reflash to Apollo 123, was having trouble again but I changed my mount options from "rw,iocharset=utf8" to "rw,sec=ntlm" and everything works for me with this option. It changes the security mode back to the old protocol, which my NAS drive uses, and was the default in the older kernels.

I don't know why but a £200 router's usb storage does not work by default and I have to do this tweak to get it to work.