Recording playback stops suddenly, TV service stops and looses path to recording folder (1 Viewer)

[wawa79]

Hi,

My MP experience has improved a lot since the last few months (lot of major issues fixed). But here is a new problem I never experienced before and that happens more and more frequently.

I am watching a recording program. Suddenly it freezes. No choice but to stop the playback. Then when I return to the recorded TV view, all recordings have disappeared and TV service is stopped (no more live TV, no TV guide).
Rebooting the PC restart TV service but does not restore the list of recorded programs. I need to go to TV Server and re-import the recordings (the recording paths in the settings are correct).
Recordings are on a NAS (Synology DS413) and path is using UNC (eg \\MyServer\MyrecordingFolder). The NAS does not go to stanby and does not seem to be the source of playback disruption.

Logs are attached (the issue occured at around 21:20 ~ 21:22). Any suggestion is welcome!

Thank you in advance!

 

[mm1352000]

Hello

Looks like TS reader starts to fail to read the recording:

06-11-2013 21:20:30.095 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832
06-11-2013 21:20:30.095 [10861fc0] [ fcc] Read failed...
06-11-2013 21:20:30.109 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832
06-11-2013 21:20:30.109 [10861fc0] [ fcc] Read failed...
06-11-2013 21:20:30.124 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832
06-11-2013 21:20:30.124 [10861fc0] [ fcc] Read failed...
06-11-2013 21:20:30.139 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832
06-11-2013 21:20:30.139 [10861fc0] [ fcc] Read failed...
06-11-2013 21:20:30.154 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832
06-11-2013 21:20:30.154 [10861fc0] [ fcc] Read failed...
06-11-2013 21:20:30.169 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832

This forces playback to be stopped.

The big negative number is an error code (0x80070040). Google suggests it means that "the specified network name is no longer available".

I suspect the share (\\DISQUERESEAU) became unavailable for some reason. Maybe the IP address of the NAS changed or network connection dropped out.

mm

 

[wawa79]

Hello

Looks like TS reader starts to fail to read the recording:

06-11-2013 21:20:30.095 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832
06-11-2013 21:20:30.095 [10861fc0] [ fcc] Read failed...
06-11-2013 21:20:30.109 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832
06-11-2013 21:20:30.109 [10861fc0] [ fcc] Read failed...
06-11-2013 21:20:30.124 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832
06-11-2013 21:20:30.124 [10861fc0] [ fcc] Read failed...
06-11-2013 21:20:30.139 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832
06-11-2013 21:20:30.139 [10861fc0] [ fcc] Read failed...
06-11-2013 21:20:30.154 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832
06-11-2013 21:20:30.154 [10861fc0] [ fcc] Read failed...
06-11-2013 21:20:30.169 [10861fc0] [ fcc] FileReader::Read() read failed - error = -2147024832

This forces playback to be stopped.

The big negative number is an error code (0x80070040). Google suggests it means that "the specified network name is no longer available".

I suspect the share (\\DISQUERESEAU) became unavailable for some reason. Maybe the IP address of the NAS changed or network connection dropped out.

mm

Thank you for the help. I did not look at the error code!

I need to understand why the share becomes unavailable: both the NAS and the router seem to stay alive while this happens... and the NAS has a fixed IP. I will try to replace \\DISQUERESEAU by its IP address: sometimes, devices names do not appear in the list of attached devices of the router. It can be a problem of QoS on the network... I think this issue started when I replaced my poor DLink NAS by the reknowned Synology one :-(

Even if I understand MP is not designed to handle hardware failures, it would be nice if TV server could 'recover' without loosing recording list from such situation.

 

[mm1352000]

Even if I understand MP is not designed to handle hardware failures, it would be nice if TV server could 'recover' without loosing recording list from such situation.

I can't explain how TV Server is losing the recording list. I suspect it simply doesn't show recordings that can't be found on disk. So, if TV Server thinks the NAS is not available then it wouldn't show those files.

Please could you use the watchdog with option 3 to grab the logs again. Then we can see if Windows thinks there is some kind of event or problem at the time that the recording stopped playing.

 

[wawa79]

I can't explain how TV Server is losing the recording list. I suspect it simply doesn't show recordings that can't be found on disk. So, if TV Server thinks the NAS is not available then it wouldn't show those files.

Please could you use the watchdog with option 3 to grab the logs again. Then we can see if Windows thinks there is some kind of event or problem at the time that the recording stopped playing.

TV Server not showing recordings when the media hosting them is down sounds a normal behaviour. But recordings are not back in the list after the media becomes available again, as if they were deleted from the DB when they are not reachable.
I adjusted QoS on the router to ensure traffic between NAS and Htpc is at top priority and I did not get the issue again today. The issue may come from security cameras I installed recently that may use significant bandwidth. I will consider isolating them on a sub-network behind a 2nd router.
I will try to simulate the loss of connection by unplugging the RJ45 cable while playing a recording and post logs with requested debug level ASAP;

 

[mm1352000]

TV Server not showing recordings when the media hosting them is down sounds a normal behaviour. But recordings are not back in the list after the media becomes available again, as if they were deleted from the DB when they are not reachable.

Yeah, at this point I can't explain it.

I adjusted QoS on the router to ensure traffic between NAS and Htpc is at top priority and I did not get the issue again today. The issue may come from security cameras I installed recently that may use significant bandwidth. I will consider isolating them on a sub-network behind a 2nd router.

Is the connection to your MediaPortal PC wireless?

I will try to simulate the loss of connection by unplugging the RJ45 cable while playing a recording and post logs with requested debug level ASAP;

It probably would have been enough to use the watchdog with option 3. It exports existing log files. In any case, if you can reproduce again and provide fresh log files using the watchdog with option 1 that is just as good.
In case you weren't aware:
http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/16_Support/3_Forums/2_Log_Files

 

[wawa79]

Is the connection to your MediaPortal PC wireless?

No, NAS and Mediaportal PC are on a wired network (through a Netgear WNR3500L 1Gb router). The cameras also are wired and on that network.

 

[Sebastiii]

I think i remember that if network is not found, there is an auto cleanup of invalid recording in db and then you need to re import it.
I think i have run is the same situation long time ago and i have forgot that lol.

 

[wawa79]

I think i remember that if network is not found, there is an auto cleanup of invalid recording in db and then you need to re import it.
I think i have run is the same situation long time ago and i have forgot that lol.

Yes, this is exactly what happens. I wonder if this "auto-cleanup" feature is a good strategy: a warning message or a user prompt might be welcome!