Sharing between BWs - Autofs doesn't work, FSTAB does

sddawson · Post by **sddawson** » Thu Feb 24, 2022 13:09

I’ve started seeing this problem. It may have started when I updated all my boxes to 19.3, but I can’t be sure.

I have 4 boxes - a mix of V2, T3 and T4. They mostly can’t see each other's movies folder. I have deleted all the mounts and set them up from scratch using the network browser, accepting all the defaults. Mount Manager says they're all mounted. When I go to the /autofs folder and select one of them, I get the dreaded "Directory media/autofs/xxxx does not exist". If I change the mount types to FSTAB and go to the /net folder, they all work fine. Currently, the T3 is the odd one out. All its autofs mounts work. Any ideas anyone?

EDIT: Spoke too soon about FSTAB. While the mounts are there, trying to play anything results in the spinner every few seconds...

sub3R · Post by **sub3R** » Fri Feb 25, 2022 07:57

Whenever this happens with our two U4s on an Ethernet LAN, the fix has always been to do a USB update & restore settings on the U4 the other one can’t see (the Server). Works 100% every time on our setup.

This may not fix your issue but it could be worth trying.

A USB update & restore can get a lot of intermittent issues resolved on our U4s (till next time).

sddawson · Post by **sddawson** » Fri Feb 25, 2022 10:12

sub3R wrote: ↑
Fri Feb 25, 2022 07:57
Whenever this happens with our two U4s on an Ethernet LAN, the fix has always been to do a USB update & restore settings on the U4 the other one can’t see (the Server). Works 100% every time on our setup.

This may not fix your issue but it could be worth trying.

A USB update & restore can get a lot of intermittent issues resolved on our U4s (till next time).

Thank you for sharing your experiences. I have been thinking about doing that. It’s a real pain with 4 boxes and all the customisation I generally do to each one. But I did install the large 19.3 update over the air, and maybe it’s time to go the USB route…

sddawson · Post by **sddawson** » Fri Feb 25, 2022 18:36

sub3R wrote: ↑
Fri Feb 25, 2022 07:57
A USB update & restore can get a lot of intermittent issues resolved on our U4s (till next time).

Well there's a whole afternoon I won’t get back! Ended up having to USB-update all four boxes before they would all talk to each other successfully. But I got there! And everything seems to be working. Thanks for pushing me in that direction. There would seem to be a generic problem with updating to 19.3 over the air, since it affected all four boxes.

sub3R · Post by **sub3R** » Fri Feb 25, 2022 19:02

sddawson wrote: ↑
Fri Feb 25, 2022 18:36
... But I got there! And everything seems to be working. ...

Good to see you got it sorted. And yes, it is a pain having to do that.

Quite a while ago I’ve had some on-line updates screw up the server/client but I can’t remember which update/s. Usually it is after a power supply outage or having to shut down at the rear power switch after a hang, but after advice from prl (I think) I’ve learnt to use init 4 & reboot instead of having to do that, providing I can telnet to the U4 using PuTTY.

sddawson · Post by **sddawson** » Fri Feb 25, 2022 20:21

sub3R wrote: ↑
Fri Feb 25, 2022 19:02

sddawson wrote: ↑
Fri Feb 25, 2022 18:36
... But I got there! And everything seems to be working. ...
Good to see you got it sorted. And yes, it is a pain having to do that.

Quite a while ago I’ve had some on-line updates screw up the server/client but I can’t remember which update/s. Usually it is after a power supply outage or having to shut down at the rear power switch after a hang, but after advice from prl (I think) I’ve learnt to use init 4 & reboot instead of having to do that, providing I can telnet to the U4 using PuTTY.

Good to know. Thanks again.