2x V2s unable to share mounts with eachother

[telesynth]

I've had 2 V2s in the house on the LAN and sharing each other's HDDs for some time. And then it stopped working after an update (sorry its a year ago). Both V2s are 19.3 with the latest updates. The error I get on both machines is "Directory /media/autofs/xxxx does not exist". I can remove the mounts and recreate them (with network browsing), have the correct root password, finds the drives and I can add the mount. But the "not exist" error always happens when you try to access the hdd in Media. I'm sure I'm doing the right things, but both machines have the same error accessing each other's drives.

Any ideas?

[MrQuade]

I've had 2 V2s in the house on the LAN and sharing each other's HDDs for some time. And then it stopped working after an update (sorry its a year ago). Both V2s are 19.3 with the latest updates.

Latest "official" or latest "beta". What's the update's date show as on your V2s?

have the correct root password,

You don't need to specify a username or password to access the media directory share.
It *should* accept them from what I remember, but it is easier if you simply don't bother entering them.

Messages relating to those mountpoints in the V2's /var/log/messages log file might shed some light on what is failing.

[telesynth]

Thanks for the fast response. Build is 20210710, just updated this week. But it hasn't been working for some time on several earlier versions.

Errors in the messages log file are

Jul 23 18:01:08 Paddy daemon.err nmbd[1999]: [2021/07/23 18:01:08.344890, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Jul 23 18:01:08 Paddy daemon.err nmbd[1999]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.191 for name WORKGROUP<1d>.
Jul 23 18:01:08 Paddy daemon.err nmbd[1999]: This response was from IP 192.168.0.190, reporting an IP address of 192.168.0.190.
Jul 23 18:02:20 Paddy user.info kernel: ^[[1;32mdvb video add event 2 - 30 0 25 0
Jul 23 18:02:20 Paddy user.info kernel: ^[[m
Jul 23 18:02:20 Paddy user.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
Jul 23 18:02:22 Paddy user.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
Jul 23 18:02:32 Paddy daemon.info automount[1944]: key "VIDEO_TS" not found in map source(s).
Jul 23 18:02:32 Paddy daemon.info automount[1944]: key "VIDEO_TS.IFO" not found in map source(s).
Jul 23 18:02:32 Paddy daemon.info automount[1944]: key ".e2settings.pkl" not found in map source(s).

[MrQuade]

That sort of looks like the V2 tried to automatically play a DVD image file, or read treasuring a directory like it was a dvd image.

Do you have any rogue video_ts.ifo files in your movie folder on either machine perhaps?

Not sure exactly what those messages mean.

[Paul_oz53]

I notice two IP addresses namely 192.168.0.190 and ...191 in the log. Are these the respective addresses of the two V2s?

When my U4s stopped seeing each other I changed the mount type from autofs to fstab, which worked for me.

The directories mount as media/net/xxxx.

[telesynth]

I notice two IP addresses namely 192.168.0.190 and ...191 in the log. Are these the respective addresses of the two V2s?

When my U4s stopped seeing each other I changed the mount type from autofs to fstab, which worked for me.

The directories mount as media/net/xxxx.

You fixed it! I changed the mounts to fstab and they both work. Thanks.

[MrQuade]

Wtf is doing on with the fstab fix.

It seems to work for some people, but I can't for the life of me think why it would/should.

What about the spaces in the mount options?

Autofs doesn't like spaces being there, but none should be inserted by default for a newly created mount.

[telesynth]

My mount names are LOUNGE and PADDY. Always have been. I think I struck this problem before in version 16, fixed it with fstab and then completely forgot about it. When I installed 19 from scratch it defaulted back to autofs. Googling the "multiple responses for WORKGROUP" seems to be a thing in linux samba.

[MrQuade]

My mount names are LOUNGE and PADDY. Always have been.

I was talking about the mount options, not the mount names.