2 x V2s not able see each other's movie folder contents

[dRdoS7]

HI,

I received the second V2 this week, and am not able to see the contents of movie folder of one on the other.

I can see them both, and all files, on a Win 10 & a Win 8 PC.

This is one (from OpenWebIf):

EDDYSV2_Movie: SMBv2.1 using autofs: //192.168.1.174/Movie (192.168.1.174)
CAROLSV2_Movie: SMBv2.1 using autofs: //192.168.1.171/Movie (192.168.1.171)

This is the other:

CAROLSV2_Movie: SMBv2.1 using autofs: //192.168.1.171/Movie (192.168.1.171)
EDDYSV2_Movie: SMBv2.1 using autofs: //192.168.1.174/Movie (192.168.1.174)

Neither can see their own mount's files. That usually indicates a problem.

I have tried using root & pw, but no difference. Re-boots in between.

This is the T2:

MovieEDDYSV2: SMBv1.0 using autofs: //192.168.1.174/Movie (192.168.1.174)
MovieCAROLSV2: SMBv1.0 using autofs: //192.168.1.171/Movie (192.168.1.171)

I can't see any files from the top one, I only just added the 2nd V2 and can't see any files, but am unable to reboot due to a current recording.

Checking in Mounts on one V2:

Looks OK.

Mounts (one each side on) appear in File Commander OK, no files:

Both V2s are beyonwiz-19.3 20201121.

Any help much appreciated.

dRdoS7

EDIT: I should add that I thought I could see the files on the first V2 on the T2 early on, but it seems to have stopped working after an update. That may have been on my T2, but that lost it's HDMI output, so it's not used anymore, & HDD removed.

[prl]

The screenshot of the File Commander screen doesn't show anything useful. To see mounts, you need to view the contents of <List of Storage Devices>, by pressing OK when the screen focus is on it.

[Grumpy_Geoff]

Try using FSTAB instead of AUTOFS for one of the mounts in Mountpoint management and see how you go with that.

[dRdoS7]

Hi,

The screenshot of the File Commander screen doesn't show anything useful. To see mounts, you need to view the contents of <List of Storage Devices>, by pressing OK when the screen focus is on it.

It was to show they are empty. They both appear OK in the list of mounts.

Any ideas as to why the mounts appear, but not show files?

I've a quick look back at my posts, and last time I had problems was 2016/17 after upgrade from 4.4 to 16.1

dRdoS7

[MrQuade]

I've a quick look back at my posts, and last time I had problems was 2016/17 after upgrade from 4.4 to 16.1

That used to happen if the Wiz tried to establish an unauthenticated session with a Windows PC.


Perhaps the Wiz is enforcing the authentication now. Perhaps with the SMB updates recently, the secrets file has been updated and the default username/password is no longer working.

I don't think that the secrets file is part of a backup, so not sure how that would have been overwritten though.

[dRdoS7]

Hi,

Try using FSTAB instead of AUTOFS for one of the mounts in Mountpoint management and see how you go with that.

Nice one, that worked OK on mine. I could see my own files.

Waiting, waiting, waiting....

And, just did the 2nd V2, and worked on that. I two sets of shares, the first empty, the second showed files. Did a reboot, and only one of each, and still showing files.

I had tried that on mine last week, but it didn't make any difference. Thought I'll wait until I have both running. But didn't think it worth changing to fstab.

I'll see what happens with the T2, it's in use ATM, so under pain of death if I go near it. Not that important as it will go in the caravan as a spare to the U4. But handy to have as a house spare, so it would be nice if worked on that too. Ditto the U4.

Having spares has come in handy in the past, as the T2s have "shuffled off this mortal coil". At least 2 have died since 2015. Also a U4, and 2 V2s have failed. The last 3 replaced by BW.

Just need the new 512GB MicroSD, and she can have 4 tuners.

dRdoS7

[Paul_oz53]

Try using FSTAB instead of AUTOFS for one of the mounts in Mountpoint management and see how you go with that.

As Grumpy_Geoff and I discussed elsewhere, if you mount the media folder with fstab (you have to modify smb-user.conf first), after that the autofs entry will magically work as normal.

Of course, there's no real need to do this but worth mentioning for completeness sake. Simpler to just swap fstab for autofs on the direct mount of the movie folder.

[Grumpy_Geoff]

Try using FSTAB instead of AUTOFS for one of the mounts in Mountpoint management and see how you go with that.

Nice one, that worked OK on mine. I could see my own files.

Waiting, waiting, waiting....

And, just did the 2nd V2, and worked on that. I two sets of shares, the first empty, the second showed files. Did a reboot, and only one of each, and still showing files.

The original AUTOFS mount hangs around until you do a reboot, but the new FSTAB mount works straight away (as the UI does a 'mkdir /media/net/{local share name}' and 'mount //{IP-addr}/{remote share name}'.
Remember you'll need to re-mount the share (press GREEN in the mounts editor) if you boot the "local" box whilst the "server" box was shutdown and then subsequently started if you want to access the "server".

In my testing of a T2, T4, and U4, the MIPS boxes using AUTOFS mounts can't get to shares from the ARM box, whereas they can if they change to using FSTAB mounts.
The ARM box can get to the MIPS boxes' shares using AUTOFS mounts.

Your experience seems to change this to - MIPS/ARM boxes using AUTOFS mounts can't get to shares from ARM boxes, whereas they can if they change to using FSTAB mounts.

[dRdoS7]

Hi,

I changed them both back to AUTOFS. Result was no visible files. Changed back to FSTAB. File visible. Have them disabled ATM.

I played a dashcam video from the 2nd V2 on my V2 last night (no recording yet as it's not connected to an antenna). The rotating balls (OverlayHD skin) would appear, then the playback paused, after a short time it would continue playing. That happened a few time in a short video. Also, when I took my V2 out of standby, and opened Media Player, the balls appeared, and screen was frozen. No visible files, I pressed exit, took a while, and then it unfroze and was exitted out of MP. It's possible it was still looking at folder/files on the 2nd V2. The same when I opened File Commander. That is set to not remember current folders.

Haven't played with it since last night.

Not had this amount of trouble with mounts before. At least the mounts on the NAS work. Both SMB & NFS. I'm not giving it to my wife to use until it can sorted. So I won't suffer any dark looks, or muttering from the owner of the 2nd V2.

I may try the NFS servers on the V2s.

Anybody has success with them?

dRdoS7

[MrQuade]

I may try the NFS servers on the V2s.

Anybody has success with them?

The NFS server works on the V2, but as of my last testing, none of the T or U series.

NFS client connections work from all of them though.

You just need to enable the server which will install the required software packages, then create your own exports file to export the movie directory.

[dRdoS7]

Hi,

I may try the NFS servers on the V2s.

Anybody has success with them?

The NFS server works on the V2, but as of my last testing, none of the T or U series.

NFS client connections work from all of them though.

You just need to enable the server which will install the required software packages, then create your own exports file to export the movie directory.

Cool. I only need it for the 2 V2s. Hopefully I won't be required to use the T2 or U4.

I've looked at the file, even added a few things, but don't see an NFS mount available.

I added this to nfsmount.conf:

Code: Select all

[ NFSMount_Global_Options ]
Proto=Tcp

[ Server "EDDYV2NFS" ]
rsize=32k
wsize=32k

[ MountPoint "/media/hdd/movie" ]
Background=True

Would you have an example?

I had NFS servers & mounts working on my Topfields, and also a Windows PC.

Thanks,

dRdoS7

[MrQuade]

I added this to nfsmount.conf:

Code: Select all

[ NFSMount_Global_Options ]
Proto=Tcp

[ Server "EDDYV2NFS" ]
rsize=32k
wsize=32k

[ MountPoint "/media/hdd/movie" ]
Background=True

Would you have an example?

You don't need to make any changes to nfsmount manually.

You can just create a /etc/exports file and put the following line into it
/media/hdd/movie *

That's the simplest option.

You can then just connect to the V2 using the normal network browser (after restarting nfs on the V2)
You should at the very least be able to see the nfs export/share. However, NFS will crash on the T or U series if you try to share on them. When I last tried on the V2 it worked nicely. At least on the OpenATV firmware.....I am pretty sure it also worked on the Beyonwiz firmware too.

[dRdoS7]

Hi,

I now have an NFS mount working on my V2. I can mount it on that V2, and create a sym link to a folder.

I'll have to change the mount back one folder to : /media/hdd * so I'll be able to mount the whole movie folder, and see all the files there too. Otherwise I can only share folders from the movie folder.

I can mount it on the other V2, but I can't create a sym. link.

I think I'll reinstall the FW on #2. See how it goes from there.

Thanks,

dRdoS7

[dRdoS7]

Hi,

Interesting development: since re-installing from USB, I can't get NFS server to install. It asks if I'd like to install the package, and reboot. I answer "yes", and it (I assume) installs, and reboots. Still no NFS. I go back to the NFS line in Network, and I am again asked if I'd like to install. Grounhog Day.

I am operating via OpenWebIF ATM, but I did do the USB install via HDMI. I swapped mine out. I thought I had installed NFS straight away, but maybe not.

I'll swap again, and see if there are any messages. Would the install appear in the log?

Should also add that I don't see anything in "Download Plugins", but I can remove plugins. Have switched to Beta Feed. Installed the 20201121 FW initailly via web when I received the V2. I only have a small 64GB SD ATM, but formatted in the V2, and it appears OK.

dRdoS7

[MrQuade]

Should also add that I don't see anything in "Download Plugins", but I can remove plugins. Have switched to Beta Feed. Installed the 20201121 FW initailly via web when I received the V2. I only have a small 64GB SD ATM, but formatted in the V2, and it appears OK.

Focus on that, because the issue is that you can't download any packages. This doesn't specifically have anything to do with NFS.

Double check you are on the beta feed. It could also just be a temporary outage of the update server.

[prl]

Focus on that, because the issue is that you can't download any packages. This doesn't specifically have anything to do with NFS.

It may have been a transitory problem, or local to dRdoS7. I just installed the NFS plugin on my test V2.

[dRdoS7]

Hi,

Don't what the problem is. Both appear to be setup the same, have same FW. Can connect via Windows 8 to the SMB shares.

Mine:

Code: Select all

System OE: 	OE-Alliance 4.3
Firmware version: 	beyonwiz 19.3.20201121 (20200822-83-g9d8cbb6)
Kernel / Drivers: 	4.4.35 / 1.2V-20201119182054

Link Speed: 	1 GBit/s
MAC address: 	d0:27:2b:00:51:a4
IPv6 address(es): 	none/IPv4-only network (SLAAC)
IPv4 address: 	192.168.1.174/24 via 192.168.1.240 (DHCP)

#2:

Code: Select all

System OE: 	OE-Alliance 4.3
Firmware version: 	beyonwiz 19.3.20201121 (20200822-83-g9d8cbb6)
Kernel / Drivers: 	4.4.35 / 1.2V-20201119182054

Link Speed: 	1 GBit/s
MAC address: 	d0:27:2b:00:51:b4
IPv6 address(es): 	none/IPv4-only network (SLAAC)
IPv4 address: 	192.168.1.171/24 via 192.168.1.240 (DHCP)

Mine has a green dot next to the Internet in Information, the 2nd V2 doesn't. I hadn't noticed that previously as I could access both via Windows Explorer. But that would be why I can't download anything.

AFAIKS, they are both entered in router's DHCP Address Reseravtion correctly.

Code: Select all

20	D0-27-2B-00-51-A4	192.168.1.174	Enabled

Code: Select all

23	D0-27-2B-00-51-B4	192.168.1.171	Enabled

Both appear in the Client's List:

Code: Select all

5	beyonwizv2	D0-27-2B-00-51-B4	192.168.1.171	Permanent

9	EDDYSV2	D0-27-2B-00-51-A4	192.168.1.174	Permanent

I can't see anything in the router that would prevent internet access to the 2nd V2.

So, how do I get the NFS package? I could download it via the PC (or 1st V2), and install it.

NFS Server is working on my V2, and I can mount it on the other V2.

The on-line updates, I can use adoxa's "Offline Upgrade", that he posted a while ago. I did use it on the T2s for a while. Worked OK.

It would be nice to have internet access on the 2nd V2, but it's not vital. Sharing folders is more important.

I compared the feed files, and both are "beta". Actually, that was before the last install, so still have to change that.

dRdoS7

[MrQuade]

So, how do I get the NFS package? I could download it via the PC (or 1st V2), and install it.

You fix the internet connection to the V2.

Seriously, if the V2 is demonstrating a problem, don't ignore it and press on because there are likely going to be other consequences.

[prl]

The "Link" indicator is shows that the Ethernet/WiFi adapter is configured and active. The "Internet" indicator shows whether the PVR can actually contact well-known sites on the Internet.

[MrQuade]

It's probably a DNS issue.

Open a command line on the V2 and ping a known internet address by name, then by its IP.

[Paul_oz53]

Seems like a hardware problem to me. If it persists, what happens if you swap the faulty unit with the working unit?

If it works then maybe a faulty cable or port. If not, maybe the ethernet port or corrupt firmware.

[dRdoS7]

Hi,

Out of interest, I grabbed the USB WiFi from the caravan, tried that:

So, that's not connecting to the internet either.

It's probably a DNS issue.

Open a command line on the V2 and ping a known internet address by name, then by its IP.

Code: Select all

/etc/opkg$ ping pvoutput.org
ping: sendto: Network is unreachable
PING pvoutput.org (45.56.66.169): 56 data bytes
/etc/opkg$ ping 45.56.66.169
ping: sendto: Network is unreachable
PING 45.56.66.169 (45.56.66.169): 56 data bytes

Ping worked on my V2.

So, how do I get the NFS package? I could download it via the PC (or 1st V2), and install it.

You fix the internet connection to the V2.

Seriously, if the V2 is demonstrating a problem, don't ignore it and press on because there are likely going to be other consequences.

I'd prefer to worry about internet later. It's really not that important. I'm sure lots of users have no LAN to their PVRs. We don't always have internet in the caravan. Lots of work has been done on the BWs to prevent outsiders hacking them, what better than no internet?

Seems like a hardware problem to me. If it persists, what happens if you swap the faulty unit with the working unit?

If it works then maybe a faulty cable or port. If not, maybe the ethernet port or corrupt firmware.

They have been swapped. Can't be cabling, as then neither would connect to the LAN. Wouldn't be hardware if it connects to LAN.

I'll download FW again. Maybe install an earlier version, and update that.

My V2's FW was upgraded on-line, the 2nd via USB.

dRdoS7

[MrQuade]

I'd prefer to worry about internet later. It's really not that important. I'm sure lots of users have no LAN to their PVRs. We don't always have internet in the caravan. Lots of work has been done on the BWs to prevent outsiders hacking them, what better than no internet?

It's not the actual internet I and worried about, it's the fact that part of the network setup on the box is broken. All that is going to happen is that problems will snowball.

You should never try to "work around" issues like this.

The fact that you can resolve DNS names tells me the V2 can talk to the router ok, but the router is denying access to the WAN.

Is that non-working V2 attached to a wireless bridge or something? Have you reached a wireless client limit on your router perhaps.

There might be a security rule or a permission that is denying access to that IP address too.

[dRdoS7]

HI,

I'd prefer to worry about internet later. It's really not that important. I'm sure lots of users have no LAN to their PVRs. We don't always have internet in the caravan. Lots of work has been done on the BWs to prevent outsiders hacking them, what better than no internet?

It's not the actual internet I and worried about, it's the fact that part of the network setup on the box is broken. All that is going to happen is that problems will snowball.

You should never try to "work around" issues like this.

I'll try an ealier version. Later.

The fact that you can resolve DNS names tells me the V2 can talk to the router ok, but the router is denying access to the WAN.

Is that non-working V2 attached to a wireless bridge or something? Have you reached a wireless client limit on your router perhaps.

There might be a security rule or a permission that is denying access to that IP address too.

Both are connected to an 8 port, which connects to the same router. All wired (except when I tested the USB WiFi). So, both the same.

No access, or security rules.

dRdoS7

[Grumpy_Geoff]

Hi,

Out of interest, I grabbed the USB WiFi from the caravan, tried that:

WiFi.jpg

So, that's not connecting to the internet either.

There's no "gateway" value (192.168.1.240) shown.

Go back to ethernet, try turning off DHCP and giving it the reserved address that the router has for it (whichever of the .171. or .174).

[dRdoS7]

Hi,

Out of interest, I grabbed the USB WiFi from the caravan, tried that:

WiFi.jpg

So, that's not connecting to the internet either.

There's no "gateway" value (192.168.1.240) shown.

Go back to ethernet, try turning off DHCP and giving it the reserved address that the router has for it (whichever of the .171. or .174).

That's the Gateway, been using that for many years. It's the router connected to the modem. It's the same on the other V2.

Anyway, since my last post, we had 4 matches of table tennis (I lost 3 to 1), and 6 games of UNO (I won 4 to 2). Then, I sat down to read how to install a package manually.

I switched to the Firefox tab with the 2nd V2 OpenWebIf, planning to open my V2, and saw the green internet icon lit up.

Quickly installed the NFS Server, which is now running.

dRdoS7

[Grumpy_Geoff]

There's no "gateway" value (192.168.1.240) shown.

Go back to ethernet, try turning off DHCP and giving it the reserved address that the router has for it (whichever of the .171. or .174).

That's the Gateway, been using that for many years. It's the router connected to the modem. It's the same on the other V2.

I was referring to the entry that's normally listed between the "MAC:" and "Bytes in / out:" lines.
"Gateway:" wasn't shown in the 1st wireless info, but was in the 2nd.

[dRdoS7]

Hi,

There's no "gateway" value (192.168.1.240) shown.

Go back to ethernet, try turning off DHCP and giving it the reserved address that the router has for it (whichever of the .171. or .174).

That's the Gateway, been using that for many years. It's the router connected to the modem. It's the same on the other V2.

I was referring to the entry that's normally listed between the "MAC:" and "Bytes in / out:" lines.
"Gateway:" wasn't shown in the 1st wireless info, but was in the 2nd.

I didn't notice that, but it's there in the screens showing both V2s Info screens a few posts back, so may not mean anything.

I was able to create an NFS on the 2nd V2 which has visible files.

I mounted my V2 NFS on the 2nd V2, I can see those files. Created a SYm. link in MediaPlayer. Played a couple of files.

What I did notice was that the resume point wheren't updated, and they resumed at the sam point each time I played them. Weird.

I'll have to check if that's the same with other NFS shared folders.

Also my NFS shared folder's Sym Link disappeared after playing some files, and a reboot made it reappear.

dRdoS7

[Paul_oz53]

Seems like a hardware problem to me. If it persists, what happens if you swap the faulty unit with the working unit?

If it works then maybe a faulty cable or port. If not, maybe the ethernet port or corrupt firmware.

They have been swapped. Can't be cabling, as then neither would connect to the LAN. Wouldn't be hardware if it connects to LAN.

I'll download FW again. Maybe install an earlier version, and update that.

My V2's FW was upgraded on-line, the 2nd via USB.

dRdoS7

Agree that it's unlikely to be hardware. Maybe the V2 port is at fault but if it works on the earlier firmware that will prove it's not a hardware problem.

If the online update progresses and it still works that will resolve the problem. If it doesn't at least that will help isolate the issue.

[dRdoS7]

Hi,

Not part of the problem, but I did notice this on the 2nd V2:

1st V2:

Indication appears to incorrect. It seems to be the Internet link, not the LAN link, that's displayed. LAN is working fine, no internet.

Haven't done another (retro) update yet. Have to clean the gutters.

dRdoS7

[Paul_oz53]

Hi,

Not part of the problem, but I did notice this on the 2nd V2:

Net info on 2nd.jpg
LAN on 2nd.jpg

1st V2:

Net Info on 1st.jpg
LAN on 1st.jpg

Indication appears to incorrect. It seems to be the Internet link, not the LAN link, that's displayed. LAN is working fine, no internet.

Haven't done another (retro) update yet. Have to clean the gutters.

dRdoS7

Hopefully it will just be a case of a corrupted USB update on the second V2. That the wrong parameter appears to be reported adds to my suspicion this may be at play.

Although it happens rarely, I've occasionally had cause to repeat a firmware install to clear a bug. These days, it's high on my action plan if something is not quite right.

[dRdoS7]

Hi,

Retro Upgrade the 2nd V2:

Had some problems with LAN not getting Internet:

Plugged in the USB (took a few reboots, re-scans, but finally) got WLAN & Internet:

Both working:

Most interesting is that AUTOFS & NFS work, and I can see it's files from both mounts:

Was also able to mount both the AUTOFS & NFS on my V2, and see it's files in both.

Not sure what the next step will be.

I can leave it as is (i.e. working.), or can update to latest FW (backup settings first!!), see what happens.

Online update is going to be > 250, so don't know if that's OK. Says to consider using USB! May download another copy, and try that first.

dRdoS7

[Paul_oz53]

Hi,

Retro Upgrade the 2nd V2:
...
Was also able to mount both the AUTOFS & NFS on my V2, and see it's files in both.

Not sure what the next step will be.

I can leave it as is (i.e. working.), or can update to latest FW (backup settings first!!), see what happens.

Online update is going to be > 250, so don't know if that's OK. Says to consider using USB! May download another copy, and try that first.

dRdoS7

I'll be setting up a V2 for Judy tomorrow so I'm keen to know if the beta is safe to use. I believe it is as others aren't indicating any show stoppers.

Being a bleeding edge type, I would try the online update but be prepared to try a fresh USB update before reverting to older firmware!

[dRdoS7]

Hi,

Hi,

Retro Upgrade the 2nd V2:
...
Was also able to mount both the AUTOFS & NFS on my V2, and see it's files in both.

Not sure what the next step will be.

I can leave it as is (i.e. working.), or can update to latest FW (backup settings first!!), see what happens.

Online update is going to be > 250, so don't know if that's OK. Says to consider using USB! May download another copy, and try that first.

dRdoS7

I'll be setting up a V2 for Judy tomorrow so I'm keen to know if the beta is safe to use. I believe it is as others aren't indicating any show stoppers.

Being a bleeding edge type, I would try the online update but be prepared to try a fresh USB update before reverting to older firmware!

I downloaded another copy of 20201121, and did a file compare: no difference.

Old version can create an AUTOFS mount which I can use. The twist is that the NFS mount, which can be seen on the 2nd V2 (i.e. itself), can't be seen on the 1st V2. I can the the mount, add it, but no files are visible.

I'll be interested to hear of your adventures. Will you be creating mounts?

dRdoS7

EDIT: Just realised I used AUTOFS instead of CIFS in many posts.

[Paul_oz53]

Hi dRdoS7,

Yes, I expect to mount her T2 and maybe a laptop or PC.

Invisible files in a visible mount may be due to wrong account credentials in other contexts. Worth checking. It may also be worth trying fstab instead of autofs.

[Grumpy_Geoff]

Yes, I expect to mount her T2 and maybe a laptop or PC.

... and NAS too if it/they work properly.
Plus vice versa, T2->V2
Couldn't be in better hands

[peteru]

LAN is working fine, no internet.

All the evidence points at some configuration issue in the router or another piece of networking hardware in your infrastructure. You haven't accidentally blacklisted the MAC or IP address of one of your machines? Or perhaps use a whitelist and mistyped the address? Or maybe your networking equipment is case sensitive on the MAC addresses? Is the problematic machine connected to an Ethernet port that has been assigned to a VLAN? Or perhaps the MAC address has been added to a VLAN?

[dRdoS7]

Hi,

LAN is working fine, no internet.

All the evidence points at some configuration issue in the router or another piece of networking hardware in your infrastructure.

You haven't accidentally blacklisted the MAC or IP address of one of your machines?

No.

Or perhaps use a whitelist and mistyped the address?

No

Or maybe your networking equipment is case sensitive on the MAC addresses?

Possibly, but all are in capitals.

Is the problematic machine connected to an Ethernet port that has been assigned to a VLAN?

No VLAN

Or perhaps the MAC address has been added to a VLAN?

No VLAN

Seems to be working OK ATM. Mostly - except internet unless the USB WiFi is plugged in.

Since the 20200823 install, I can see the 2nd V2's CIFS mount on the 2nd V2, which I couldn't with 20201121. I still can't see my V2's CIFS mount on my V2, or the 2nd V2. Only V2's NFS mounts are visble.

While rechecking for the above questions, I went down lower in the router's menu.

Found it: IP & MAC Binding!!!

The 192.168.1.171 IP used to belong to my T2, and was taken over by the V2. I had changed it in DHCP Reservation, but didn't realise it was also assigned elsewhere.

I've unplugged the USB WiFI, rebooted the 2nd V2, and now have Internet connection.

Don't know why that wouldn't have had a effect on the LAN. I could see the mount in Windows Explorer. I could also see the NFS mounts.

On the weekend, I'll remove the 2 mounts (CIFS & NFS) on my V2, reboot, and re-create them. Maybe even do the same FW downgrade.

dRdoS7

[Paul_oz53]

Yes, I expect to mount her T2 and maybe a laptop or PC.

... and NAS too if it/they work properly.
Plus vice versa, T2->V2
Couldn't be in better hands

Judy's NAS is a pair of older Dlink units that only support SMB v1.0. But after faffing around for an hour we restored connectivity to her PC and laptops.

Removing the T4 and swapping the HDD to an enclosure took longer than expected. Internally the T4 cement appeared ok but a hint of brownish goo. Judy will send it to Perth in due course.

Her aerial looks fine and similar to her neighbours but my signal strength meter shows only 50db. With an amplifier we got 70db. Poor signal strength appears to be the cause of her pixellation issues.

Installed the V2 with the SD card and the USB drive. Eventually realised one has to turn off the USB drive to format the V2's SD card. Also ran a disc check on the USB. Until I did that the T4 recordings weren't visible.

Although the setup wizard gave a suitable set of network parameters, there was no Internet connection. The network test said pass for all five tests, the Menu >> Information >> Network screen reported correct parameters but Setup >> Network >> Network interface only showed the Primary DNS with the rest of the fields blank. I had to manually edit that screen after which network access worked. Firmware is 20201106.

Setup access to the T2 from the V2 and to the NAS using autofs but deleted vers=2.1. No account id or password required. Worked immediately.

Initially set recording to the USB drive but then we swapped to the NAS as it has far more free space.

Registered the IceTV account details.

Time ran out and I had to leave so there remains many things left to do.

Judy will setup the reserved address in the router and we'll restore the V2 to automatic configuration DHCP and see if it still works ok.

I'd update the firmware too.

Didn't have time to setup the T2 to see the V2.

Judy was happy but was just coming to grips with the yellow location button in media player. We may get queries about that.

[dRdoS7]

Hi,

I installed 20200823FW on my V2 from USB. Didn't restore settings from 20201121FW.

I can see both V2's CIFS Movie Shares on my V2:

2nd V2:

UPDATE: I did an on-line update on my V2, and I could still see both CIFS mounts.

Then I did an on-line update on the 2nd. V2, and could still see both CIFS mounts.

I am (almost) tempted to revert the router's previous setting (i.e. incorrect IP binding). It fixed the lack of Internet connectionon the 2nd V2, but still don't see how it could have an effect on a V2 seeing it's own, or another's mount.

I'm free to swap the V2 in place of the T2, and hope it stays that way.

dRdoS7

[Paul_oz53]

Although the setup wizard gave a suitable set of network parameters, there was no Internet connection. The network test said pass for all five tests, the Menu >> Information >> Network screen reported correct parameters but Setup >> Network >> Network interface only showed the Primary DNS with the rest of the fields blank. I had to manually edit that screen after which network access worked. Firmware is 20201106.

Judy has reserved the IP address in the router and we have enabled automatic configuration, which now works as expected.

Setup access to the T2 from the V2 and to the NAS using autofs but deleted vers=2.1. No account id or password required. Worked immediately.

Initially set recording to the USB drive but then we swapped to the NAS as it has far more free space.

Judy contacted me by phone today reporting a list of woes with playing back, deleting and moving files on the NAS from the V2.

Long story short, we changed the Mount type from AUTOFS to FSTAB on the V2. AUTOFS works fine on the T2. After a reboot, playback behaved normally in all respects. However, we have had all sorts of erratic behaviour mounting the NAS as FSTAB at subsequent reboots.

After a second and a third reboot, it did not mount as FSTAB at reboot. However, manually mounting it as FSTAB did work. We then swapped back to AUTOFS and rebooted. This time it mounted and files playback normally. Thus, its behaviour is quite erratic between the two mount types.

Using FSTAB playback works fine if manually mounted but it did not reliably mount at boot. AUTOFS mounted every time we tried it. Playback worked on the later AUTOFS reboots after initially giving trouble. This may be because the IP address is now allocated by the router, removing a delay in resolving the address of the NAS when the media player accesses the playback source on a skip, etc.

I doubt NAS HDD spin down has anything to do with it as our time between tests was quite short - a minute or two. We have left it as AUTOFS as Judy usually goes to standby rather than deep standby on the V2/T4 in the lounge.

We'll see how it goes longer term.

[MrQuade]

You are almost always better off sticking with autofs.

If we actually find some case where fstab actually solves and issue we need to look into the exact reasons why and fix it in the firmware. Fstab is nothing but a band-aid solution to what might or might not be some other issue.