Unable to find recording files error message

Have a MythTV related problem? Ask for help from other MythTV users here.

Moderator: Forum Moderators

Post Reply
jimls
Newcomer
Posts: 3
Joined: Sat Oct 14, 2017 2:26 am
United States of America

Unable to find recording files error message

Post by jimls » Sat Oct 14, 2017 3:10 am

have a 0.27 system for recording USA OTA programs. It works most of the time but sometimes stops recording. It is a combined BE/FE with two HVR-1600 tuner cards (using just the digital tuners). It looks like I have disk space and that isn't the issue. The recording titles are shown but the preview is black. When I select to view it it gives an error: " the file for this recording cannot be found". I looked at the logs but couldn't see anything obvious but must admit I didn't really know much about what I was looking at.

This happened once before and things worked ok after rebooting but I haven't rebooted yet this time because I would like to find the issue. I checked the uptime and determined that at least one recording worked since it was last booted.

What should I be looking at? Really loosing SAF over this... Is it possible the tuners are failing? Any chance there might be files with the missing recordings?
Last edited by jimls on Sat Oct 14, 2017 11:41 am, edited 1 time in total.

jimls
Newcomer
Posts: 3
Joined: Sat Oct 14, 2017 2:26 am
United States of America

Re: Unable to find recording files error message

Post by jimls » Sat Oct 14, 2017 3:41 am

I did find this:

https://code.mythtv.org/trac/ticket/10318

so, on the off chance it has to do with my Nvidia card got the info with:
nvidia-smi

Card is GeForce 8400GS
Driver is 340.102

I ran (kind of grasping at straws here and found something about this in a related search):
dmesg | grep 'saa7164|firmware'
but it gave no output.


dmesg by itself (no parameters) showed a number of errors like this but I am not sure it is related to the current issue:

Code: Select all

[1995048.940625] s5h1409_writereg: error (reg == 0xf5, val == 0x0001, ret == -6)
[1995048.941957] s5h1409_writereg: error (reg == 0xf3, val == 0x0001, ret == -6)
[1995048.943288] s5h1409_writereg: error (reg == 0xf3, val == 0x0001, ret == -6)
[1995048.944596] mxl5005s I2C write failed
[1995048.945928] s5h1409_writereg: error (reg == 0xf3, val == 0x0000, ret == -6)
[1995048.947291] s5h1409_writereg: error (reg == 0xf3, val == 0x0001, ret == -6)
[1995048.948589] mxl5005s I2C write failed
[1995048.949884] mxl5005s I2C write failed
[1995048.951215] s5h1409_writereg: error (reg == 0xf3, val == 0x0000, ret == -6)
[1995048.981932] s5h1409_readreg: readreg error (ret == -6)
[1995048.983267] s5h1409_writereg: error (reg == 0xf5, val == 0x0000, ret == -6)

User avatar
pgbennett
Developer
Posts: 156
Joined: Mon Apr 27, 2015 5:41 pm
United States of America

Re: Unable to find recording files error message

Post by pgbennett » Sat Oct 14, 2017 2:02 pm

In playback if you press I you will see recording info that includes the file name. You may have to press I twice to see all the info. See if you can find the file in the storage group directory.

Is the problem with recording or playback? If it is with recording then the NVidia will have nothing to do with it.

If the file exists and is a reasonable length it may be a playback problem. Try playing it with VLC or another playback program. If it works that way you can try different playback profiles in MythTV to see if a different one works.

jimls
Newcomer
Posts: 3
Joined: Sat Oct 14, 2017 2:26 am
United States of America

Re: Unable to find recording files error message

Post by jimls » Sat Oct 14, 2017 2:32 pm

I can't get to playback. When I select the video it immediately gives an error that the file cannot be found. How do I get to a point that I can enter "I"? I am pretty sure it is the tuners locking up. If I try to watch live tv through myth front end it gives an error of not locking on to a signal and no picture.

I understand your comment about the tuner not being an issue with the video card - they seem unrelated but there have been issues with the nvidia drivers causing trouble with some tuners. It was some sort of software conflict, possibly involving interrupts.

Post Reply