T3 can't find network mount after some time

[Grumpy_Geoff]

The only difference in the settings is: utf8,vers=2.1 on the V2 vs utf8 on the T4

Then remove the ,vers=2.1 from the V2's mount options.

[itstonyb]

I tried removing the ,=ver2.1 yesterday, but that did nothing

[MrQuade]

If you are running the latest beta firmware on the V2, then you actually need to replace the vers option with vers=1.0 if you want to connect using a lower SMB version

It's insufficient to just remove the 2.1 option

[itstonyb]

Ok, simple fix..I changed the "Mount Using" from AUTOFS to Enigma2 ,saved and the mounts light up green and work again.

Thanks all for trying to help.

I haven't done the beta firmware upgrade yet, do I need to?

[Paul_oz53]

Ok, simple fix..I changed the "Mount Using" from AUTOFS to Enigma2 ,saved and the mounts light up green and work again.

Thanks all for trying to help.

I haven't done the beta firmware upgrade yet, do I need to?

I have long wondered what the Enigma2 option did. This is the first time I have seen a report that it actually works! Is this confined to the V2 or does it have an effect on earlier machines too?

[itstonyb]

I have only changed it on the V2, I didn't need to change it on the T4, it works on utf8

[prl]

I have long wondered what the Enigm[a]2 option did.

It is similar to the FSTAB option, except that no mount entries are put into /etc/fstab, and the mounts are done by enigma2 (the main application that runs everything that makes the box a PVR rather than a Linux computer) when it starts up at the end of the boot sequence. With FSTAB entries are put into /etc/fstab so that the mounts are done in the system startup scripts at boot time.

I don't think many people use it, though I have played around with it while testing.