e2 boxes no access to recordings on duo internal hdd.

[cactikid]

whats listed on the vu duo in recorded list.when going to solo to view location of vu duo recordings

[abu baniaz]

On your solo, you are still looking at the internal HDD of that receiver.

Press yellow for location, you should see the network device (duo). You can then create a bookmark to it.

[cactikid]

yes i had to remount the duo as i had to reboot yesterday and as usual i do press yellow for choice of viewing points but i keep getting that message no directory found so cannot create bookmark

[s1m0nw]

Use nfs for both boxes.

Sent from my GT-I9300 using Tapatalk

[chaser]

Yes. As I suggested earlier, use nfs. Make sure nfs is installed on all machines. Setup as below:

Mount Using: AUTOFS
Active: enable
Local share name: WhateverNameYouWant
Mount type: NFS Share
Server IP: IPAddressOfTheRemoteBoxYouWantToReadFrom (eg 192.168.0.10)
Server share: media/hdd/movie
Use as HDD replacement: No
Mount options: rw,nolock,tcp

This assumes that you've got the movie folder at media/hdd. That should work for you and get rid of your red x problem.

Also worth having a look at this post (note the subtle changes in the settings above, compared to what I suggested in my earlier posts):

http://www.world-of-satellite.com/sh...592-NFS-Shares

[cactikid]

ok will try that and report back,thought i did it that way but will double check to see

[chaser]

If you're still having problems, it's worth being aware that there are a couple of system network files that sometimes get out of sync with the Vix mount manager. I'm not sure why this happens, but sometimes old corrupt network mount details can remain in these files, even though you've deleted them from the Vix mount manager. Trying to remount with the same alias can then cause mount issues. The only way I've managed to fix this is by deleting the corrupt network mount entries from the system files. The two system files are fstab and auto.network both of which can be found in /etc.

The example below is from my auto.network file. Note the incorrect mmovie entry for the Livingroom mount. Deleting the Livingroom mount from Vix mount manager wouldn't remove this file entry, and every time I tried to re-create a Livingroom mount via Vix, this file would never get updated with the correct info.

# automounter configuration
Livingroom -fstype=nfs,rw,nolock,tcp,rsize=8192,wsize=8192,soft 192.168.0.52:/media/hdd/mmovie
Bedroom -fstype=nfs,rw,nolock,tcp,rsize=8192,wsize=8192,soft 192.168.0.53:/media/hdd/movie

Once I had deleted the Livingroom mount from Vix, I then manually removed the Livingroom line from the auto.network file. Once I had done this I could then create the correct Livingroom mount in Vix.

[cactikid]

nope not worked xxx in all,is that ip ok?

[chaser]

I get the same when I check mounts via Network Browser, but I get the following if I go into Mount Viewer (via Mount Manager):

mount view hr.jpg

[cactikid]

would new images not cleanse the system as starting from scratch,from which i did

[chaser]

Yes it should. However, I managed to corrupt my system network files trying to create network mounts after doing a fresh install when going from Apollo build 32 to build 37. In your case it's probably not a corrupt file, but if all else fails it might be worth checking.

[abu baniaz]

Here is a video of process. Excuse the slight pauses as was reading manual and doing it at same time.