I run a master backend with two diskless frontend clients. The backend locked up the other day after running for a couple of months. It was a hard lockup, no ssh, no login at the console. So I had to power off.

Things looked to be OK after a restart. However the recordings since that time all have wrong time lengths as reported by the GUI. I mean when playing a recording, hitting 'info' displays the position you are in the recording. Instead of saying "0:01:30 of 0:59:50" for an hour recording, the recording size is much larger. Something more like "0:01:30 of 8:34:17". The recording is really recorded the length it's supposed to be, just this value of the length is broken.

Any suggestions?

Thanks in advance.

Heh, I was just about to make a post with the same thing. It's very strange, indeed. I haven't found a fix, yet though.

I have HD and SD tuners in my system. The HD recordings do have the correct time on them though. So I think it may be some sort of calculation error since the two types of files have different bit rates.

Also, it started about a month ago on R5E50. I upgraded to F1, hoping it might be fixed, but it was not. At the time, I hadn't made any tweaks to the system, it's been running beautifully.

Check for database damage. See Cecil's sticky posting under hints & tips on DB repair.

I've fixed this a few times in the past by running "commercial detection" and "lossless transcoding" a few times on the effected recording. This seems to rebuild the "seektable" in the database.

_________________
My Ziki

Thanks for the info. It was a corrupted DB table/file. Re-running mythcommflag on the recordings to fix them up too.

Thanks again for all of your help.

I had this same problem after a storm knocked out my backend. I repaired the tables as above, but I also had to run the following command to rebuild the time tables:




This solved my extended length issue.

I figured this out by scrolling down a ways in the STICKY on MYSQL repair here:

http://mysettopbox.tv/phpBB2/viewtopic.php?t=1043

Now I just have to worry about this impending ZAP2It stuff!

-Loco