You mentioned that in your first post, what I would like to know is
1 - Has this ever worked?
2 - Is this a new install or an upgrade (and if so, from what version)?
3 - Do you have a /var/log/mythtv/mythfrontend.log file? If so, does it contain any indication of the failure?

That's not the code I gave you, please re-read that post and note the > symbol preceding each of those lines.

Sorry,

I found those recordins that wouldnt expiry and deleted them they were in my live tv view under recordings.

[quote]1 - Has this ever worked?
2 - Is this a new install or an upgrade (and if so, from what version)?
3 - Do you have a /var/log/mythtv/mythfrontend.log file? If so, does it contain any indication of the failure? [/quote]

1. - No this is the first time I have tried it.
2. From memory i upgraded from R5E50.
3. yes i have the /var/log/mythtv/mythfrontend.log but when i check it there is never an error at the time It crashed. In my previous post that was the last few lines.

I have about 40 gig free on the hardrive.

Seeing as its christmas and ill have the time im thinking of wiping everything and starting fresh with r5f27.

Hi,

Going into the way back machine, ~A26 era, sometimes things would get out of sync and the db entry would be deleted or the recording was deleted but not both and then we ended up with some dead wood. The history should appear under mythlink / pretty.

Anyway, if it is telling you that the file is missing, then it will need that file to exist before it can delete. Just go through the list that it says is missing and touch the file. Open a couple of xterms and while viewing one, copy and paste the missing enteries.

If it says "/myth/tv/1007_20070622074123.mpg" is missing then do:
$ touch /myth/tv/1007_20070622074123.mpg
and repeat for all that it complains about. Never directly delete files from the /myth/tv folder, make a copy is fine, no to moving also.

At 256 mem every once in a while the front end may exit on me HOWEVER, the choice of theme can affect things as some themes require more space than others. With 384mem that problem ceased. I suspect it may be a timeout as it is trying to swap things around and can't do it quick enough. "A premature exit, not a crash"

Also I am finding the pieces in this thread very unclear. Hardware you have 2.x cpu, we know about 256mem, and 5200 card, how big a drive? ide or sata? How do all the other functions work, music, gallery, videos, and etc? Exactly what steps are you doing when the "crash" occurs?

Give the folks all the details you can so they can get you running smoothly. If things are messed up now with the db & what there are for recordings, an upgrade won't fix it. Fix it then upgrade :0
Mike

Hi,

thanks, I think I have fixed the missing mpg problem. I have already deleted throught the myth funciton of going to recordings menu and selecting them from the list and hitting delete. It doesnt come up with the errors in the backend log anymore.

Just to clarrify the problem, when I select Archive and then select find files in the menu it reads the hardrive for about 5 minutes and drops back to the penguine screen. I cant find any errors in the mythfrontend.log or mythbackend.log to do with the crash.

My system is:
Pentium 4 2.66 gig
mem: 256 meg
Graphics card - FX5200
Tuner: Dvico plus pci.
Harddrive: From memory 300 gig ide seagate pretty sure it was a barracuda.
Version: Knoppmyth R5F1 upgraded from r5d1.

I have read the upgrade notes and I have a working directory for Archive in settings.

All other functions are fine except for myth musics scan for new music. When i scan it reads for about 5 minutes and drops back to the penguine screen. However if I do the scan upon a fresh boot without doing anything else it will work. However I have never successfully got Archive to work even on a reboot.

I appreciate everyones help, I dont want to keep wasting everyones time.

This smells of a bad DB as Mike alluded to. There are a few posts on these forums regarding how to repair your DB (searching for "repair database" should yield those)

At this point this may be your best bet, but be sure to try the DB repair first. If you go with R5F27, go through tjc's Hints & Tips post http://knoppmyth.net/phpBB2/viewtopic.php?t=16384 to be sure there aren't any pitfalls with your setup.