T3 can't find network mount after some time

[terryweaver]

Hi,

My T3 keeps loosing the network mount, at bootup it's fine then if you want to use it later in the day it just sits there with the wheel spinning for about 15 minutes then it finds it.
I've checked the mount manager and it looks good (no red cross through it) then go straight to access the folder and same thing, if I turn it off at the back and reboot it it's fine straight away.
This has only started happening after the latest update, I haven't done one via USB for a few years and this one said I had to redo all my settings again so I couldn't restore them from what was saved.
I think I must have something wrong but I cant figure out what. It's like it's looking for the folder or reading all the files in it I'm not sure.
The folder I am sharing has the path D:\Movies
My router address is: 10.1.1.1
My PC address is: 10.1.1.2
Network sharing on my PC has password-protected sharing turned off

Here are my settings for the mount:

Mount Using: "FSTAB (mount at boot)"
Active: Enabled
Local share name: Movies
Mount Type: CIFS share
Server IP: 10.1.1.2
Server Share: Movies
Use as HDD replacement: Disabled
Mount Options: rw, utf8
Username:
Password:

My network settings are (I'm using Wi-Fi):

IP address: 10.1.1.49
Subnet: 255.255.255.0
Gateway: 10.1.1.1
Primary DNS: 10.1.1.1
Secondary DNS: 0.0.0.0

Version: 17.5
Build: 20190207

[MrQuade]

This has only started happening after the latest update

There hasn't been an online update for the 17.5 series firmware for a couple of years. So are you saying this has been a problem for that long?

Best advice to start with is to update to the latest beta (via USB) to get all the latest improvements. It shouldn't be necessary to clear your settings when switching to the latest USB (though it was necessary with the 17.5 series switching from 16.1).

I notice that you are using fstab rather than AutoFS. As stated, fstab is a boot-time mount, whereas autofs will be mounted on demand (and is tdefault). You may have better luck using autofs, especially if your PC is intermittently available or is rebooted every so often.

[Grumpy_Geoff]

My T3 keeps loosing the network mount, at bootup it's fine then if you want to use it later in the day it just sits there with the wheel spinning for about 15 minutes then it finds it.

Perhaps your wireless connection is dropping out.

Mount Using: "FSTAB (mount at boot)"

You could try using AUTOFS instead, particularly if your PC isn't always on.

This has only started happening after the latest update, I haven't done one via USB for a few years and this one said I had to redo all my settings again so I couldn't restore them from what was saved.

There hasn't been any update to the 17.5-series' 20190207 firmware.
The latest general release firmware is the 19.3-series 20191106 - you can restore settings using a backup taken using a 17.5-series firmware (Wiz HQ lazily posted mis-information).
But in my opinion, you should be running the latest beta - 20210602 and its online update to 20210603 (once you switch your feed to the beta feed).

[Grumpy_Geoff]

Ah, Speedy Gonzalez beat me to it (again)!

[terryweaver]

Hi Sorry I should have said I went back to my old version (17.5-beyonwizt3-20171230) but that didn't fix it, I then did an update online with the switch feed to beta.
I just tried changing to AUTOFS and rebooted now I can see my "Movies" folder but when I go to it it's empty.
Also I should have mentioned sometimes when watching a movie it drops out and goes back to the file commander screen, I can restart the movie and skip forward to where I was no problem.

[Grumpy_Geoff]

I just tried changing to AUTOFS and rebooted now I can see my "Movies" folder but when I go to it it's empty.

Try adding ",vers=2.1" to -

Mount Options: rw, utf8

Better still, update the firmware as advised.

[Paul_oz53]

Hi,

My T3 keeps loosing the network mount, at bootup it's fine then if you want to use it later in the day it just sits there with the wheel spinning for about 15 minutes then it finds it.
I've checked the mount manager and it looks good (no red cross through it) then go straight to access the folder and same thing, if I turn it off at the back and reboot it it's fine straight away.
This has only started happening after the latest update, I haven't done one via USB for a few years and this one said I had to redo all my settings again so I couldn't restore them from what was saved.
I think I must have something wrong but I cant figure out what. It's like it's looking for the folder or reading all the files in it I'm not sure.
The folder I am sharing has the path D:\Movies
My router address is: 10.1.1.1
My PC address is: 10.1.1.2
Network sharing on my PC has password-protected sharing turned off

Here are my settings for the mount:

Mount Using: "FSTAB (mount at boot)"
Active: Enabled
Local share name: Movies
Mount Type: CIFS share
Server IP: 10.1.1.2
Server Share: Movies
Use as HDD replacement: Disabled
Mount Options: rw, utf8
Username:
Password:

My network settings are (I'm using Wi-Fi):

IP address: 10.1.1.49
Subnet: 255.255.255.0
Gateway: 10.1.1.1
Primary DNS: 10.1.1.1
Secondary DNS: 0.0.0.0

Version: 17.5
Build: 20190207

Hi Terry,

My ethernet-connected T3 is working fine with virtually identical settings except for the FSTAB setting. Mine is set to AUTOFS and is using pre-allocated IP addresses as set by my router by reference to MAC addresses.

I have found pre-allocating the IP addresses in the router to be far more reliable. A short delay while waiting for a sleeping HDD to spin up is all that I normally see. I did have a glitch after an MS update a few days ago whereby the PC couldn't see the T3 but that came good after I rebooted the T3.

My firmware is 20210603.

Cheers, Paul

[terryweaver]

Ok, I've updated to the latest beta 19.3 via USB, then online update using switch_feed_to_beta to build 20210603.
I've added , vers=2.1 to the line rw, utf8 now it reads "rw, utf8, vers=2.1"
and I changed to AUTOFS (mount as needed)
Just a note I have a static lease set up on my router for the T3 (10.1.1.49)
Rebooted
the "Movies" folder is there but it's empty, mountpoint manager has a red cross through it.
If I change back to FSTAB (mount at boot) I can see the contents of the "Movies" folder and play files.

[MrQuade]

I've added , vers=2.1 to the line rw, utf8 now it reads "rw, utf8, vers=2.1"

You need to remove that. The T3 doesn't actually support SMB 2.1 due to kernel limitations.

You need to make sure that you have enabled SMB1 support in windows via the Windows "optional features".

[Grumpy_Geoff]

If I change back to FSTAB (mount at boot) I can see the contents of the "Movies" folder and play files.

The next time the FSTAB share can't be found, try a restart of the T3's network (MENU>>Setup>>Network>>Network restart) instead of a reboot.

[Grumpy_Geoff]

I've added , vers=2.1 to the line rw, utf8 now it reads "rw, utf8, vers=2.1"

You need to remove that. The T3 doesn't actually support SMB 2.1 due to kernel limitations.

How does the share work then?

[MrQuade]

How does the share work then?

It just doesn't apply the setting, and continues to use SMB1, there will be an error in /var/log/messages.

Likely terryweaver already made that setting a while back.

I still can't figure out why some people are having this trouble with autofs vs fstab. Quite possibly the "vers" option is being handled differently in those two scenarios.

[terryweaver]

ok removed vers=2.1
I have enabled SMB1 support in windows (the client box was not checked)
rebooted computer, rebooted T3.
"Movies" folder is still empty
Tried network restart no change

[Grumpy_Geoff]

ok removed vers=2.1
I have enabled SMB1 support in windows (the client box was not checked)
rebooted computer, rebooted T3.
"Movies" folder is still empty
Tried network restart no change

Okay, try changing the T3's local share name to "PC-Movies" or similar, as "Movies" is also the name of the default export of /media/hdd/movie/ and perhaps there's a clash somewhere.

[terryweaver]

Ok I just removed the space between the comma and the utf8, so the line now reads "rw,utf8" not "rw, utf8"
It now works with AUTOFS (mount as needed) I can see the files in the "Movies" folder

[MrQuade]

Ok I just removed the space between the comma and the utf8, so the line now reads "rw,utf8" not "rw, utf8"
It now works with AUTOFS (mount as needed) I can see the files in the "Movies" folder

Ohhh, interesting!

[Grumpy_Geoff]

Ok I just removed the space between the comma and the utf8, so the line now reads "rw,utf8" not "rw, utf8"
It now works with AUTOFS (mount as needed) I can see the files in the "Movies" folder

So the FSTAB code doesn't care about the space, but the AUTOFS code does?

[Paul_oz53]

Ok I just removed the space between the comma and the utf8, so the line now reads "rw,utf8" not "rw, utf8"
It now works with AUTOFS (mount as needed) I can see the files in the "Movies" folder

So the FSTAB code doesn't care about the space, but the AUTOFS code does?

FSTAB seems to be quite insensitive but can't be sure. From my recent foray into FSTAB it appears to parse to all lowercase so I wouldn't be surprised if it trims spaces too.

What is likely though is the former FSTAB entry still persists in the fstab file.

I had to install FSTAB-editor to remove redundant entries. Mount manager doesn't delete them properly. They disappear from automounts.xml and aren't mirrored in auto.network IIRC but live on in fstab if not manually deleted in the editor.

[MrQuade]

What is likely though is the former FSTAB entry still persists in the fstab file.

If say that if you were converting an existing fstab mount to an automount, then the old entry world be likely to be left behind. Deleting the fstab and recreating as autofs should work properly.

[Paul_oz53]

What is likely though is the former FSTAB entry still persists in the fstab file.

If say that if you were converting an existing fstab mount to an automount, then the old entry world be likely to be left behind. Deleting the fstab and recreating as autofs should work properly.

Indeed, exactly what I did. So it depends on how one converts fstab to autofs whether this happens or not.

[Grumpy_Geoff]

What is likely though is the former FSTAB entry still persists in the fstab file.

If say that if you were converting an existing fstab mount to an automount, then the old entry world be likely to be left behind. Deleting the fstab and recreating as autofs should work properly.

Indeed, exactly what I did. So it depends on how one converts fstab to autofs whether this happens or not.

I can't recall it exactly, but didn't prl state that a mount should be first deleted before changing its type given the nature/quirkiness of the mountpoints management code? Or was that something else I'm thinking of?

[Paul_oz53]

You're probably right Grumpy_Geoff but who amongst men ever reads the instructions first?

When something doesn't work as I imagine it should the problem is the fault of the maker, never the user...

PEBKAC is fake news I'm reliably informed!

[terryweaver]

Update
everything seems to be ok now
I'll just run through everything I did.
1) Updated to the latest beta 19.3 via USB, then online update using switch_feed_to_beta to build 20210603.
2) Enabled SMB1 support in windows via the Windows "optional features" (the client box was not checked).
3) Removed the space between the comma and the utf8, so the line now reads "rw,utf8" not "rw, utf8"
4) Changed from FSTAB (mount at boot) to AUTOFS (mount as needed).
5) Rebooted computer and T3, all good now

[itstonyb]

Hopefully someone can help:

The network mount in my V2 has stopped working (red x) It was connected to my Synology Diskstation which still works fine, no changes to anything and still fully accessible from my pc.

This has happened before a few times but all I've needed to do is go into mount manager click on the mount and then save with green button and all is reconnected, but not this time.

The network link in V2 is active and I can see all connected devices in the network

IP addresses are all the same , no changes to anything.

Settings:
AUTOFS
Active - Yes
Local Share name Diskstation
CIFS share
Server IP 192/168.0.100 (this is a static IP for the V2 and has not changed, can see V2 from my PC on this ip)
Server Share - Disk Storage (again nothing has changed here)
Use as HDD replacement - No
Mount options - rw,utf8,vers=2.1
User Name and Password (no changes)

[Grumpy_Geoff]

Server IP 192/168.0.100 (this is a static IP for the V2 and has not changed, can see V2 from my PC on this ip)
Server Share - Disk Storage (again nothing has changed here)

The "server IP" address should be that of the Synology, not your V2.

[itstonyb]

Yes sorry I meant to say the server ip of 192.168.0.100 is the address of my Synology, which hasn't changed

[MrQuade]

Yes sorry I meant to say the server ip of 192.168.0.100 is the address of my Synology, which hasn't changed

Something must be different then....

Are you running the latest beta firmware and configured to get updated from the beta update feed?

There were some updates in the last beta that changed a few things in the way that mounts are handled. Of note were changes in the way that the SMB versions are handled (the vers=2.1 is generally not needed with the latest firmware).

No firmware updates on the Synology?

Any info in the Synology logs? Can you try to re-save the mount and then check the last few lines of /var/log/messages on the V2?

[Paul_oz53]

My T3 has no "vers=2.1" parameter in its mounts and works fine in accessing network mounts. Delete it if it is present and try again.

[MrQuade]

My T3 has no "vers=2.1" parameter in its mounts and works fine in accessing network mounts. Delete it if it is present and try again.

Whether that parameter is required depends on a lot of factors.

For the T3, it should definitely be removed since it is not supported.

On the V2, it depends what version of firmware is running on the V2, and what the minimum supported SMB version is on the NAS.

If the NAS enforces SMB2 or later, and the V2 is on older firmware, then the parameter is required.
If the NAS allows SMB1, then the parameter isn't required.
If the V2 is on latest firmware, and the NAS doesn't support SMB2, then you would actually need to specify vers=1.0 instead.

PeterU's suggestion of the addition of some checkboxes (or toggle'able options) for these version options makes a lot of sense.

[Paul_oz53]

My T3 has no "vers=2.1" parameter in its mounts and works fine in accessing network mounts. Delete it if it is present and try again.

Whether that parameter is required depends on a lot of factors.

For the T3, it should definitely be removed since it is not supported.

On the V2, it depends what version of firmware is running on the V2, and what the minimum supported SMB version is on the NAS.

If the NAS enforces SMB2 or later, and the V2 is on older firmware, then the parameter is required.
If the NAS allows SMB1, then the parameter isn't required.
If the V2 is on latest firmware, and the NAS doesn't support SMB2, then you would actually need to specify vers=1.0 instead.

PeterU's suggestion of the addition of some checkboxes (or toggle'able options) for these version options makes a lot of sense.

Half asleep! Read the topic heading and fixated on the T3 rather than the V2. Of course, you're right.

Agree on selectable options.

Lately, I've found some aspects of Samba to be erratic. Two U4s see each other and the T3 fine. Both see the T4 but one works fine whilst the other is plagued by delayed responses and buffering. The T4 responds in kind. Works fine with the T3 and one U4 but barely speaks to the Lounge U4.

[itstonyb]

Nothing has changed.
The v2 can see everything connected but wont light up green in the mount manager.
Have not done a firmware update on either the V2 or the Synology

Where do I find log messages:
/var/log/messages on the V2?

[Grumpy_Geoff]

Where do I find log messages:
/var/log/messages on the V2?

Yeah, messages file in directory /var/log/, so the path to the file is as MrQuade posted - /var/log/messages.
If you don't have FTP access, then you can grab the file via a browser - http://beyonwizv2/file?file=/var/log/messages
Whilst you're there, grab /etc/auto.network as well so we can check the mount definition (you can obscure username and password if you wish).

[itstonyb]

ok I have no idea what you have said but here are the last few lines of the log file:

Jun 29 19:25:10 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 19:25:11 beyonwizv2 user.warn kernel: video[0] ready to play
Jun 29 19:25:11 beyonwizv2 user.warn kernel: ^[[1;32mdvb video add event 17 - 7 0
Jun 29 19:25:11 beyonwizv2 user.warn kernel: ^[[m
Jun 29 19:25:11 beyonwizv2 user.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
Jun 29 19:25:12 beyonwizv2 user.warn kernel: [23:51:14:358 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 646 Failed
Jun 29 19:25:12 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 1 - 0 0 1920 1080
Jun 29 19:25:12 beyonwizv2 user.info kernel: ^[[m
Jun 29 19:25:12 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 0 0 30 0

[itstonyb]

I also notice that when I update an existing mount, it does it in about 2 seconds whereas it normally take 15-20 seconds to advise "your network mount has been updated".

[itstonyb]

I've also tried a full factory reset but to no avail.

[prl]

There's nothing in the /var/log/messages snippet that's relevant top network mounts.

[itstonyb]

ok so Im guessing this piece of rubbish is heading for the bin

[itstonyb]

Here are the full log meesages for today:
Jun 29 17:34:35 beyonwizv2 daemon.notice ntpdate[1910]: step time server 27.124.125.252 offset 1624959249.673003 sec
Jun 29 17:34:35 beyonwizv2 daemon.err ntpdate[1911]: step-systime: Invalid argument
Jun 29 17:34:35 beyonwizv2 daemon.notice stb-hwclock: Current system time has been written into FP pseudo RTC.
Jun 29 17:34:35 beyonwizv2 user.warn kernel: ^[[1;32mdvb video add event 17 - 7 0
Jun 29 17:34:35 beyonwizv2 user.warn kernel: ^[[m
Jun 29 17:34:35 beyonwizv2 user.warn kernel: proc_vmpeg_0_dst_apply_write 1
Jun 29 17:34:35 beyonwizv2 user.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
Jun 29 17:34:36 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 17:34:36 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 17:34:36 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 17:34:36 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 17:34:36 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 17:34:36 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 17:34:38 beyonwizv2 user.warn kernel: panscan
Jun 29 17:34:38 beyonwizv2 user.warn kernel: proc_video_videomode_50hz_write [1080p50]
Jun 29 17:34:38 beyonwizv2 user.warn kernel: proc_video_videomode_60hz_write [1080p50]
Jun 29 17:34:38 beyonwizv2 user.warn kernel: proc_video_videomode_24hz_write [1080p50]
Jun 29 17:34:40 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 17:34:40 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 17:34:40 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 17:34:40 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 17:34:40 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 17:34:40 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 17:34:40 beyonwizv2 user.warn kernel: hi_dvb_set_source [dmx: 0, tuner: 0, isvtuner: 0]
Jun 29 17:34:40 beyonwizv2 user.info kernel: [hi_dvb_attach_tsport:740 dmx 0,port 32]0 5 1 0 184
Jun 29 17:34:40 beyonwizv2 user.warn kernel: demodid = 0,i2c = 2,freq=184500000 band=7000000,stream pid = -1
Jun 29 17:34:40 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 17:34:40 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 17:34:40 beyonwizv2 user.warn kernel: audio[0] ready to play
Jun 29 17:34:40 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 17:34:40 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 17:34:40 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 17:34:40 beyonwizv2 user.warn kernel: video[0] ready to play
Jun 29 17:34:41 beyonwizv2 user.warn kernel: ^[[1;32mdvb video add event 17 - 7 0
Jun 29 17:34:41 beyonwizv2 user.warn kernel: ^[[m
Jun 29 17:34:41 beyonwizv2 user.warn kernel: [22:00:44:023 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 0 Failed
Jun 29 17:34:42 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 1 - 0 0 1920 1080
Jun 29 17:34:42 beyonwizv2 user.info kernel: ^[[m
Jun 29 17:34:42 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 0 0 25 0
Jun 29 17:35:09 beyonwizv2 cron.info crond[1901]: (*system*) RELOAD (/etc/crontab)
Jun 29 17:35:29 beyonwizv2 user.info kernel: ^[[mir frame error.
Jun 29 17:35:29 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:36:28 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 17:36:28 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 17:36:28 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 17:36:28 beyonwizv2 user.warn kernel: audio[0] ready to play
Jun 29 17:36:28 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 17:36:28 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 17:36:28 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 17:36:28 beyonwizv2 user.warn kernel: video[0] ready to play
Jun 29 17:36:29 beyonwizv2 user.warn kernel: ^[[1;32mdvb video add event 17 - 7 0
Jun 29 17:36:29 beyonwizv2 user.warn kernel: ^[[m
Jun 29 17:36:29 beyonwizv2 user.warn kernel: [22:02:31:503 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 2647 Failed
Jun 29 17:36:29 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 1 - 0 0 1920 1080
Jun 29 17:36:29 beyonwizv2 user.info kernel: ^[[m
Jun 29 17:36:29 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 0 0 25 0
Jun 29 17:36:32 beyonwizv2 user.info kernel: ^[[mir frame error.
Jun 29 17:36:32 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:36:33 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:36:33 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:36:34 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:36:34 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:36:38 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:36:38 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:36:38 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:37:07 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:37:07 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:37:08 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 17:37:08 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 17:37:08 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 17:37:08 beyonwizv2 user.warn kernel: audio[0] ready to play
Jun 29 17:37:08 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 17:37:08 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 17:37:08 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 17:37:08 beyonwizv2 user.warn kernel: video[0] ready to play
Jun 29 17:37:09 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 1 - 0 0 1920 1080
Jun 29 17:37:09 beyonwizv2 user.info kernel: ^[[m
Jun 29 17:37:09 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 0 0 30 0
Jun 29 17:37:09 beyonwizv2 user.info kernel: ^[[m^[[1;32mdvb video add event 17 - 7 0
Jun 29 17:37:09 beyonwizv2 user.warn kernel: ^[[m
Jun 29 17:37:09 beyonwizv2 user.warn kernel: [22:03:12:083 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 973 Failed
Jun 29 17:37:51 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 30 0 25 0
Jun 29 17:37:51 beyonwizv2 user.info kernel: ^[[mir frame error.
Jun 29 17:37:51 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:38:35 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:38:35 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:38:39 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:38:39 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:38:40 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:38:40 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:38:45 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:38:45 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:38:57 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:38:57 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:39:34 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:39:35 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:40:09 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:40:09 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:40:37 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:40:37 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 17:47:01 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 18:17:01 beyonwizv2 cron.info CROND[2056]: (root) CMD ( cd / && run-parts /etc/cron.hourly)
Jun 29 18:30:01 beyonwizv2 authpriv.info crond[2084]: pam_unix(crond:session): session opened for user root by (uid=0)
Jun 29 18:30:01 beyonwizv2 cron.info CROND[2085]: (root) CMD (/usr/bin/ntpdate-sync silent)
Jun 29 18:30:09 beyonwizv2 daemon.notice ntpdate[2089]: step time server 194.0.5.123 offset 1.902294 sec
Jun 29 18:30:09 beyonwizv2 daemon.notice stb-hwclock: Current system time has been written into FP pseudo RTC.
Jun 29 18:30:09 beyonwizv2 authpriv.info CROND[2084]: pam_unix(crond:session): session closed for user root
Jun 29 18:40:05 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 18:40:05 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 18:40:05 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 18:40:05 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 18:40:05 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 18:40:05 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 18:40:05 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 19:17:01 beyonwizv2 cron.info CROND[2167]: (root) CMD ( cd / && run-parts /etc/cron.hourly)
Jun 29 19:24:43 beyonwizv2 user.warn kernel: hi_dvb_set_source [dmx: 0, tuner: 0, isvtuner: 0]
Jun 29 19:24:43 beyonwizv2 user.info kernel: [hi_dvb_attach_tsport:740 dmx 0,port 32]0 5 1 0 184
Jun 29 19:24:43 beyonwizv2 user.warn kernel: demodid = 0,i2c = 2,freq=184500000 band=7000000,stream pid = -1
Jun 29 19:24:44 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 19:24:44 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 19:24:44 beyonwizv2 user.warn kernel: audio[0] ready to play
Jun 29 19:24:44 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 19:24:44 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 19:24:44 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 19:24:44 beyonwizv2 user.warn kernel: video[0] ready to play
Jun 29 19:24:45 beyonwizv2 user.warn kernel: ^[[1;32mdvb video add event 17 - 7 0
Jun 29 19:24:45 beyonwizv2 user.warn kernel: ^[[m
Jun 29 19:24:45 beyonwizv2 user.warn kernel: [23:50:47:555 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 94342 Failed
Jun 29 19:24:46 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 1 - 0 0 1920 1080
Jun 29 19:24:46 beyonwizv2 user.info kernel: ^[[m
Jun 29 19:24:46 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 0 0 25 0
Jun 29 19:25:06 beyonwizv2 user.info kernel: ^[[mproc_vmpeg_0_dst_apply_write 00000001
Jun 29 19:25:10 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 19:25:10 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 19:25:10 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 19:25:10 beyonwizv2 user.warn kernel: audio[0] ready to play
Jun 29 19:25:10 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 19:25:10 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 19:25:10 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 19:25:11 beyonwizv2 user.warn kernel: video[0] ready to play
Jun 29 19:25:11 beyonwizv2 user.warn kernel: ^[[1;32mdvb video add event 17 - 7 0
Jun 29 19:25:11 beyonwizv2 user.warn kernel: ^[[m
Jun 29 19:25:11 beyonwizv2 user.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
Jun 29 19:25:12 beyonwizv2 user.warn kernel: [23:51:14:358 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 646 Failed
Jun 29 19:25:12 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 1 - 0 0 1920 1080
Jun 29 19:25:12 beyonwizv2 user.info kernel: ^[[m
Jun 29 19:25:12 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 0 0 30 0

[Grumpy_Geoff]

ok so Im guessing this piece of rubbish is heading for the bin

Grab http://beyonwizv2/file?file=/etc/auto.network

[MrQuade]

Here are the full log meesages for today:

Have you attempted to re-save your network mount since 17:34 today? I can't see any entries in that log that report mount failures.

Can you try re-saving that mount, and then posting a fresh log?

I also notice that when I update an existing mount, it does it in about 2 seconds whereas it normally take 15-20 seconds to advise "your network mount has been updated".

That's odd, it should only take about 2 seconds if things are working properly.

[itstonyb]

# automounter configuration
MAIN -fstype=cifs,user=*user*,pass=*pasword*,rw,iocharset=utf8,vers=2.1,cache=loose ://192.168.0.4/New Volume
NAS -fstype=cifs,user=*user*,pass=*password*,rw,iocharset=utf8,vers=2.1,cache=loose ://192.168.0.100/Disk Storage

First mount is my PC, second is my Synology NAS
Neither light up green

[itstonyb]

Just attempted to re save mounts again and here are the log file lines:

Jun 29 21:57:44 beyonwizv2 user.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
Jun 29 21:57:46 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 21:57:46 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 21:57:46 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 21:57:47 beyonwizv2 user.warn kernel: audio[0] ready to play
Jun 29 21:57:47 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 21:57:47 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 21:57:47 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 21:57:47 beyonwizv2 user.warn kernel: video[0] ready to play
Jun 29 21:57:47 beyonwizv2 user.warn kernel: ^[[1;32mdvb video add event 17 - 7 0
Jun 29 21:57:47 beyonwizv2 user.warn kernel: ^[[m
Jun 29 21:57:47 beyonwizv2 user.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
Jun 29 21:57:48 beyonwizv2 user.warn kernel: [02:23:50:384 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 20635 Failed
Jun 29 21:57:49 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 1 - 0 0 1920 1080
Jun 29 21:57:49 beyonwizv2 user.info kernel: ^[[m
Jun 29 21:57:49 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 0 0 25 0

[itstonyb]

Last 2 attempted mount saves:

Jun 29 22:39:01 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 30 0 25 0
Jun 29 22:39:01 beyonwizv2 user.info kernel: ^[[mir frame error.
Jun 29 22:39:01 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 22:39:32 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 22:39:32 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 22:39:32 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 22:39:32 beyonwizv2 user.warn kernel: audio[0] ready to play
Jun 29 22:39:32 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 22:39:32 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 22:39:32 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 22:39:32 beyonwizv2 user.warn kernel: video[0] ready to play
Jun 29 22:39:33 beyonwizv2 user.warn kernel: ^[[1;32mdvb video add event 17 - 7 0
Jun 29 22:39:33 beyonwizv2 user.warn kernel: ^[[m
Jun 29 22:39:33 beyonwizv2 user.warn kernel: [03:05:35:308 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 1322 Failed
Jun 29 22:39:33 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 1 - 0 0 1920 1080
Jun 29 22:39:33 beyonwizv2 user.info kernel: ^[[m
Jun 29 22:39:33 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 0 0 25 0
Jun 29 22:39:42 beyonwizv2 user.info kernel: ^[[mir frame error.
Jun 29 22:39:42 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 22:39:52 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 22:39:52 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 22:39:52 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 22:39:52 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 22:39:52 beyonwizv2 user.warn kernel: stStdTiming[h:640, v:480]
Jun 29 22:39:52 beyonwizv2 user.warn kernel: stStdTiming[h:1024, v:768]
Jun 29 22:40:17 beyonwizv2 user.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
Jun 29 22:40:20 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 22:40:20 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 22:40:21 beyonwizv2 user.warn kernel: proc_vmpeg_0_dst_apply_write 00000001
Jun 29 22:41:31 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 22:41:31 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 22:42:00 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 22:42:00 beyonwizv2 user.warn kernel: ^[[1;32mdvb video add event 17 - 7 0
Jun 29 22:42:00 beyonwizv2 user.warn kernel: ^[[m
Jun 29 22:42:00 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 22:42:00 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 22:42:00 beyonwizv2 user.warn kernel: audio[0] ready to play
Jun 29 22:42:00 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelDetachSync 0 0
Jun 29 22:42:00 beyonwizv2 user.warn kernel: DmxPcrAcquire 0 -1073059932
Jun 29 22:42:00 beyonwizv2 user.warn kernel: Enter DMX_OsiPcrChannelAttachSync 0 0 4325376
Jun 29 22:42:01 beyonwizv2 user.warn kernel: video[0] ready to play
Jun 29 22:42:01 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 1 - 0 0 1920 1080
Jun 29 22:42:01 beyonwizv2 user.info kernel: ^[[m
Jun 29 22:42:01 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 0 0 30 0
Jun 29 22:42:02 beyonwizv2 user.info kernel: ^[[m[03:08:04:148 ERROR-HI_VPSS]:HI_DRV_VPSS_RelPortFrame[520]:Port = 0 RelPortFrame 3678 Failed
Jun 29 22:48:23 beyonwizv2 user.info kernel: ^[[1;32mdvb video add event 2 - 30 0 25 0
Jun 29 22:48:23 beyonwizv2 user.info kernel: ^[[mir frame error.
Jun 29 22:48:23 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 22:48:51 beyonwizv2 user.warn kernel: ir frame error.
Jun 29 22:48:51 beyonwizv2 user.warn kernel: ir frame error.

[peteru]

It's a bad idea to have spaces in path names. You should rename New Volume and Disk Storage to get rid of the embedded spaces. NewVolume and DiskStorage would be suitable alternatives.

Also, kernel logs are not going to show enigma2 log output.

[itstonyb]

Ok will try that however it's been that way all along without any problems until now (6 years of T4 and V2 mounting to my NAS).

[MrQuade]

Also, kernel logs are not going to show enigma2 log output.

Shouldn't it show an AutoFS mount failure though?
Hrmmm...or do you have to attempt to access the mount for that to spit out an error.

[itstonyb]

Still no joy.
I can access the V2 through OpenWebif and play live tv on my pc so obviously not a network error on the V2.

The V2 wont mount anything, not just my Nas, but also not my PC or T4 upstairs.

Where do I get the beta firmware upgrade from and also are the instructions to upgrade the V2 the same as the T4?

[Grumpy_Geoff]

The V2 wont mount anything, not just my Nas, but also not my PC or T4 upstairs.

Did you change the share names on the PC and NAS, not just the local name on the V2?
Do those same shares work on the T4?

Where do I get the beta firmware upgrade from and also are the instructions to upgrade the V2 the same as the T4?

Beta firmware - viewtopic.php?f=56&t=14722
Take a backup before you flash the new firmware.

[itstonyb]

Thanks for the link

Yes the T4 mounts to the Synology, I just went upstairs and all good, I then deleted the mount and re-entered it and still all working properly.
The only difference in the settings is: utf8,vers=2.1 on the V2 vs utf8 on the T4
So it must be the V2 that is the issue
Will try the beta firmware upgrade on the V2 and see if anything changes

no I haven't renamed the shares on anything as I don't want to mess access up to anything else and shouldn't need to in any case as it has never been an issue.