Foxylink - not seeing HRD1

RobL

Member
Hi,

I had some fun and games last night attempting to get my HDRs to see each other. To cut a long story short, in the end I set Foxylink on HDR'B' to see HDR'A' (both HDRs have the virtual disk software installed) and recursive auto-decrypt is set on HDR'A' (and 'B' for that matter) at the top level. Anyhow, left it overnight and, if looking through the WEBIF for HDR'B', I can see HDR'A' as a folder / directory but cannot see this when exploring through the TV (i.e. Storage - only have HDD and Network as normal). Any ideas?
Side note: ideal world, I'd like HDR'A' to see HDR'B' and vice versa. I am happy to use network shares if this will do the trick, but just couldn't get this to work at all (guessing that my location 'name' was incorrect, albeit I did try almost every combination I could think of ... My Video, etc!!). I was using NFS rather than Samba. I'm only doing this so that I get FWD / RWD as both boxes see each other and play quite happily via the standard Network selection. I've read everything that I could on the forum, but got more confused not less!
FOR AF123 if you happen to see this: every time I log in to WEBIF for HDR'B' I get the 'restart' notification - thoughts?
Many thanks all who take the time to read (even better if I get a reply lol)
 

MontysEvilTwin

Well-Known Member
To see the remote HDR you need either virtual disk 2 (not virtual disk) installed or a USB drive of some description plugged in. The remote device is accessed through >storage>USB.
 

Ezra Pound

Well-Known Member
I'm wondering if the original virtual disk should be removed as an option from 'Package Management', are there any instances where the original virtual disk package MUST be used rather than virtual disk2 ?
 
OP
R

RobL

Member
Many, many thanks o for this - it's now working perfectly!
As a note for any other readers of this, if you already have virtual disk installed then you first need to to remove this (both boxes) and install virtual disk 2 from the package list. If you do not do this, virtual disk 2 will 'appear' to install but the (installed) package list will remain with just the normal virtual disk (this is what I hadn't noted originally). Once removed and VD2 installed, reboot both systems. As commented by others previously, Foxlink may take a minute or two to 'boot' but then you should be able to see (Storage, USB) and use (Resume play, FWD, RWD) as if you were at the main box. I am using 2 HDRs not a HDR and HD.
For myself, I may attempt to see if I can use Foxlink on both machines so that I have a '360 view' but not sure if this will work or whether I will have to use networkshares automount to achieve; I will update as as when I get round to it (unless someone else comments first :) )
Once again, really appreciate the time taken to reply (and, even more, resolve!). Now just to find why I keep getting the annoying restart message!
 
OP
R

RobL

Member
I'm wondering if the original virtual disk should be removed as an option from 'Package Management', are there any instances where the original virtual disk package MUST be used rather than virtual disk2 ?

Yep, thanks Ezra, as our posts overlapped, that's what I found. I'll soon find out if VD1 is used anywhere!
 

af123

Administrator
Staff member
I'm wondering if the original virtual disk should be removed as an option from 'Package Management', are there any instances where the original virtual disk package MUST be used rather than virtual disk2 ?
The original virtual-disk is useful for copying files to force decryption on a HD booted in HDR mode. Virtual-disk 2 has a side effect of popping up a 'media inserted' dialogue which isn't always desirable.
 

af123

Administrator
Staff member
Now just to find why I keep getting the annoying restart message!
I don't know. The flag is cleared on a reboot so something must be modifying your recording schedule on every boot. I would start by looking in the modinit log file to see if anything in there points to the cause. Have you ever scheduled anything to record on box B?
 
OP
R

RobL

Member
The original virtual-disk is useful for copying files to force decryption on a HD booted in HDR mode. Virtual-disk 2 has a side effect of popping up a 'media inserted' dialogue which isn't always desirable.

So, as I have 2 HDRs, there is no need / benefit of VD1? As I commented, it doesn't appear that one can have both simultaneously installed anyway so somewhat academic I guess.
 
OP
R

RobL

Member
I don't know. The flag is cleared on a reboot so something must be modifying your recording schedule on every boot. I would start by looking in the modinit log file to see if anything in there points to the cause. Have you ever scheduled anything to record on box B?

I only scheduled 1 programme to record (non-series) yesterday - it's a new box. I attach the modinit log if that helps.
>>> Contents of /var/log/modinit.log 6.89 KiB
=== Sat Jan 1 00:00:12 UTC 2000 - modinit - setup_hosts ===========================
=== Sat Jan 1 00:00:12 UTC 2000 - setup hosts ===========================
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.1.254 0.0.0.0 UG 0 0 0 eth0
[RR] Sat Jan 1 00:00:13 2000: Recording end 0.
[RR] Sat Jan 1 00:00:13 2000: Recording end 0.
Interface: [eth0]
[RR] Sat Jan 1 00:00:13 2000: Recording end 0.
[RR] Sat Jan 1 00:00:13 2000: Recording end 0.
IP: [192.168.1.94]
=== Sat Jan 1 00:00:13 UTC 2000 - complete ===========================
=== Tue Feb 18 11:00:22 UTC 2014 - modinit - ===========================
=== Tue Feb 18 11:00:22 UTC 2014 - diag ===========================
Filesystem Size Used Available Use% Mounted on
/dev/root 21.4M 21.4M 0 100% /
tmpfs 61.0M 32.0K 61.0M 0% /tmp
tmpfs 61.0M 0 61.0M 0% /media
/dev/mtdblock1 2.0M 532.0K 1.5M 26% /var/lib/humaxtv
/dev/mtdblock2 2.0M 544.0K 1.5M 27% /var/lib/humaxtv_backup
/dev/mtdblock2 2.0M 544.0K 1.5M 27% /usr/browser/opera_dir/url/url.txt
/dev/sda1 1011.4M 42.6M 917.5M 4% /mnt/hd1
/dev/sda2 447.6G 5.1G 419.7G 1% /mnt/hd2
/dev/sda3 9.8G 150.6M 9.2G 2% /mnt/hd3

eth0 Link encap:Ethernet HWaddr DC:D3:21:56:19:48
inet addr:192.168.1.94 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:762 (762.0 B) TX bytes:664 (664.0 B)
Interrupt:16

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


PID USER VSZ STAT COMMAND
1 root 1244 S init
2 root 0 SW [migration/0]
3 root 0 SWN [ksoftirqd/0]
4 root 0 SW [migration/1]
5 root 0 SWN [ksoftirqd/1]
6 root 0 SW< [events/0]
7 root 0 SW< [events/1]
8 root 0 SW< [khelper]
9 root 0 SW< [kthread]
10 root 0 SW< [kblockd/0]
11 root 0 SW< [kblockd/1]
12 root 0 SW< [khubd]
13 root 0 SW< [kseriod]
14 root 0 SW [pdflush]
15 root 0 SW [pdflush]
16 root 0 SW< [kswapd0]
17 root 0 SW< [aio/0]
18 root 0 SW< [aio/1]
19 root 0 SW< [ata/0]
20 root 0 SW< [ata/1]
21 root 0 SW< [ata_aux]
22 root 0 SW< [scsi_eh_0]
23 root 0 SW< [scsi_eh_1]
24 root 0 RW [mtdblockd]
25 root 0 SW< [kpsmoused]
26 root 1240 S {rcS} /bin/sh /etc/init.d/rcS
71 root 0 SWN [jffs2_gcd_mtd1]
72 root 0 SWN [jffs2_gcd_mtd2]
129 nobody 936 S /usr/bin/dnsmasq
135 root 812 S N /sbin/utelnetd -l /bin/tmenu -p 23 -d -B
167 root 1248 S {S90settop} /bin/sh /etc/init.d/S90settop start
218 root 329m S /usr/bin/humaxtv
377 root 1612 S udhcpc -t 5 -T 10 -p /var/lib/humaxtv/udhcpc.eth0.pid -i eth0
396 root 1204 S tinyftp -i HumaxFTP -p 0000 -c /media
425 root 0 SW< [kjournald]
438 root 1260 S < {run-and-gun} /bin/sh /etc/mdev/run-and-gun
463 root 0 SW< [kjournald]
466 root 1260 S < {run-and-gun} /bin/sh /etc/mdev/run-and-gun
476 root 1260 S < {run-and-gun} /bin/sh /etc/mdev/run-and-gun
493 root 0 SW< [kjournald]
576 root 1252 R < {modinit} /bin/sh /sbin/modinit
582 root 1228 S < sleep 1
593 root 1228 S < sleep 1
597 root 1236 R < ps -w

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default BThomehub.home 0.0.0.0 UG 0 0 0 eth0

=== Tue Feb 18 11:00:23 UTC 2014 - reset all ===========================
=== Tue Feb 18 11:00:23 UTC 2014 - rma ===========================
=== Tue Feb 18 11:00:23 UTC 2014 - ugprade bootmod ===========================
=== Tue Feb 18 11:00:23 UTC 2014 - setup directories ===========================
=== Tue Feb 18 11:00:24 UTC 2014 - create modenv ===========================
=== Tue Feb 18 11:00:24 UTC 2014 - migrate bootmod ===========================
=== Tue Feb 18 11:00:24 UTC 2014 - setup hostname ===========================
=== Tue Feb 18 11:00:24 UTC 2014 - setup hosts ===========================
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default BThomehub.home 0.0.0.0 UG 0 0 0 eth0
Interface: [eth0]
IP: [192.168.1.94]
=== Tue Feb 18 11:00:24 UTC 2014 - run init ===========================
killall: bootstrapd: no process killed
Loaded CIFS module into kernel.
Tue Feb 18 11:00:24 UTC 2014 - S01cifs (elapsed: 0s)
Tue Feb 18 11:00:24 UTC 2014 - S01crond (elapsed: 1s)
Loaded FUSE module into kernel.
Tue Feb 18 11:00:25 UTC 2014 - S01fuse (elapsed: 0s)
Loading config file /mod/etc/mongoose.conf
Tue Feb 18 11:00:25 UTC 2014 - S01mongoose (elapsed: 0s)
Anacron 2.3 started on 2014-02-18
Tue Feb 18 11:00:25 UTC 2014 - S02anacron (elapsed: 0s)
Normal exit (0 jobs run)
Tue Feb 18 11:00:25 UTC 2014 - S02portmap (elapsed: 0s)
Restoring scheduled events from /mod/boot/schedule.ab...
Restoring --- Auto Update ---
Restoring favourite channels...
Tue Feb 18 11:00:25 UTC 2014 - S03autoschedule (elapsed: 1s)
Tue Feb 18 11:00:26 UTC 2014 - S10screensaver (elapsed: 0s)
Tue Feb 18 11:00:26 UTC 2014 - S30posttvcrash (elapsed: 0s)
Tue Feb 18 11:00:27 UTC 2014 - S40ir (elapsed: 0s)
Tue Feb 18 11:00:27 UTC 2014 - S60parseepg (elapsed: 0s)
Tue Feb 18 11:00:28 UTC 2014 - S80mdnsd (elapsed: 0s)
MDNS interface: [eth0]
An FTP Server is already running, not starting betaftpd.
Tue Feb 18 11:00:28 UTC 2014 - S89betaftpd (elapsed: 1s)
Tue Feb 18 11:00:29 UTC 2014 - S89virtual-disk (elapsed: 1s)
Tue Feb 18 11:00:30 UTC 2014 - S91samba (elapsed: 0s)
Tue Feb 18 11:00:30 UTC 2014 - S98nfs-server (elapsed: 1s)
Tue Feb 18 11:00:31 UTC 2014 - S99auto-unprotect (elapsed: 0s)
=== Tue Feb 18 11:00:31 UTC 2014 - complete ===========================
 

Black Hole

May contain traces of nut
I may attempt to see if I can use Foxlink on both machines so that I have a '360 view' but not sure if this will work
It should work. NFS does not also "mount" external drives; with SMB one has to be careful not to set up an infinite recursion (HDR1 sees HDR2 and also HDR1 mounted on HDR2...). network-shares-automount can mount NFS and SMB, foxlink mounts NFS.

Regarding virtual-disk2, like I said I prefer to keep a UPD fitted (or a USB HDD). Virtual drives used to be handy for decryption (and still are on the HD-FOX), but developments in CF decryption on the HDR-FOX made them unnecessary (except for tricking the HDR into thinking it has a drive fitted).

Why did you install virtual-disk in the first place? Just for the sake of it??
 
OP
R

RobL

Member
It should work. NFS does not also "mount" external drives; with SMB one has to be careful not to set up an infinite recursion (HDR1 sees HDR2 and also HDR1 mounted on HDR2...). network-shares-automount can mount NFS and SMB, foxlink mounts NFS.

Regarding virtual-disk2, like I said I prefer to keep a UPD fitted (or a USB HDD). Virtual drives used to be handy for decryption (and still are on the HD-FOX), but developments in CF decryption on the HDR-FOX made them unnecessary (except for tricking the HDR into thinking it has a drive fitted).

Why did you install virtual-disk in the first place? Just for the sake of it??

I (probably!) installed it when I first installed the CF on my first box last January (for whatever reason that would now escape me!) and replicated the same on this box.
I shall give the Foxlink a go on HDR'A' later, but will have to leave it a while as just listening to my lad do his reading homework now - 3 books this week :)
 

af123

Administrator
Staff member
Restoring scheduled events from /mod/boot/schedule.ab...
Restoring --- Auto Update ---

You have auto-schedule-restore installed. On boot it's finding an empty recording schedule and running a restore which sets the 'reboot required' flag.
 
OP
R

RobL

Member
You have auto-schedule-restore installed. On boot it's finding an empty recording schedule and running a restore which sets the 'reboot required' flag.

Super; I shall leave in place for now as no doubt little man will set up lots of Sooty, Dennis and Gnasher, etc., etc., to start filling up the disk soon enough and then the message will disappear. (Already looking to put the 1tb drive in at some future stage!).
Thank you for taking the time and resolving. Definitely time for me to donate to the cause I think (albeit I have one extra 'idea' which I believe would make this truly great .. may have to 'crowdfund' that request if it's possible as I'm sure if would have some interest ... anyhow, that's for another day!!). Cheers.
 

Black Hole

May contain traces of nut
It's not recordings that make this go away, it's schedule items.

The question that occurs to me is why the auto-restore is doing this perpetually - after a reboot it should have restored the schedule and shut up about it.
 
OP
R

RobL

Member
Just to say thank you once again to everyone for their help and input earlier today. All appears to be working well and I have, also, now installed FoxLink on HDR'A' so that I have a '360 view' (which, to coin a phrase, is 'cool'! ...not that I really want to watch Sooty necessarily; Ice Age is a good possibility however:) ).
I had one issue whereby the whole of HDR'B' locked up and I could only turn off via a WEBIF reboot of the device, but not sure if that was more of a coincidence; I shall do some testing later on to see what happens if (when) the 'mounted' device turns off and also check if there is a, periodic, 'ping' or equivalent when the device becomes available ... no doubt already some comments on here if I do the rounds, but may be easier to do some checking myself.
Well, the sun is setting over a very flooded river here, so time to close for now and then, perhaps, a little more playing later. Cheers.
P.S. AF and BH, I have removed the autoschedule backup from 'B' for the time being as not important on that box (he says until his 7 year old kicks him when it's lost after a retune lol)
 

Ezra Pound

Well-Known Member
I have removed the autoschedule backup from 'B' for the time being as not important on that box (he says until his 7 year old kicks him when it's lost after a retune lol)
You will still be able to restore your scheduled and faviorites from the back-up manually
 

MontysEvilTwin

Well-Known Member
The original virtual-disk is useful for copying files to force decryption on a HD booted in HDR mode. Virtual-disk 2 has a side effect of popping up a 'media inserted' dialogue which isn't always desirable.
I wouldn't remove virtual disk from the package list, but it is not needed for decryption on a HD-FOX. In HDR mode, the USB drive is mounted as both an internal HDD and as an external drive (drive1). I just have a 'recordings' folder set up on drive1 and in HDR mode you can copy to this folder from the simulated internal drive, decrypting in the process.
 
OP
R

RobL

Member
Ah well, my earlier 'fear' seems that it may have some substance - it appears, if you turn off HDR'B' (standby mode) the 'other' HDR locks (VIDEO displayed on the front display). I'm guessing, but it is only a guess at this stage, that the mounted drive suddenly becomes unavailable (as no unmount command is sent to the client side at server off) and the system locks. As soon as it is turned back on again, everything springs back to life (after a couple of minutes). My questions, therefore, before removing Foxlink and just living without the FWD, RWD, etc., are:
1. Has anybody else come across this (may be what is occurring is a red herring?)
2. Does / will network shares automount negate this issue?
3. ...and, most importantly, does what I have said make any sense at all??!!
Cheers.
 

Black Hole

May contain traces of nut
I don't use foxlink, but it shouldn't do that. Have you mapped the share into the video folder, or are you accessing it as a virtual USB as instructed?
 
OP
R

RobL

Member
I don't use foxlink, but it shouldn't do that. Have you mapped the share into the video folder, or are you accessing it as a virtual USB as instructed?

Setup Foxlink via the WEBIF settings (IP address and 'name'); as for VD2, just installed - is there something else i was meant to do? On the boxes, via WEBIF, I see 'drive1' (the virtual) and the named 'mounted' drive of the other HDR (which i can happily play from, etc. via the USB selection from media). All, ostensibly at least, seems to be in order - apart from the locking when you turn one off!
 
Top