View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 5 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
 Post subject: Scheduled recordings
PostPosted: Sun Apr 02, 2006 6:56 pm 
Offline
Joined: Sun Mar 26, 2006 3:42 pm
Posts: 39
I have an issue with my recordings, for example when I record a 30 minute show (The Simpsons" for example the times on it show that its at plat 0:16:38 out of 11:28:38 - but at the end of the recording (30 minutes) the recording asks me if I want to delete as it should.

In addition, the commercial auto skip doesn't work. I have flagging enabled, but it doesn't seem to help.

Any have any ideas?


Top
 Profile  
 
 Post subject:
PostPosted: Wed Apr 05, 2006 10:37 pm 
Offline
Joined: Sun Mar 26, 2006 3:42 pm
Posts: 39
Anyone have anything? I am totally lost here.


Top
 Profile  
 
 Post subject:
PostPosted: Sat Apr 08, 2006 7:58 pm 
Offline
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location: Fontana, Ca
You'll find folks won't usually comment if we don't know what the problem is... Or if enough detail isn't provided. Have you investigated the logs?

_________________
cesman

When the source is open, the possibilities are endless!


Top
 Profile  
 
 Post subject:
PostPosted: Sun Apr 09, 2006 12:16 am 
Offline
Joined: Sun Mar 26, 2006 3:42 pm
Posts: 39
hey Cesman, Thanks for the reply. When you refer to the logs, which ones in particular are you thing?

from /var/log/syslog I get:

Apr 9 00:07:25 mythtv mysqld[3430]: 060409 0:07:24 /usr/sbin/mysqld: Can't ope
n file: 'recordedmarkup.MYI'. (errno: 145)
Apr 9 00:07:25 mythtv mysqld[3430]: 060409 0:07:25 /usr/sbin/mysqld: Can't ope
n file: 'recordedmarkup.MYI'. (errno: 145)
Apr 9 00:07:26 mythtv mysqld[3430]: 060409 0:07:26 /usr/sbin/mysqld: Can't ope
n file: 'recordedmarkup.MYI'. (errno: 145)
Apr 9 00:07:27 mythtv mysqld[3430]: 060409 0:07:27 /usr/sbin/mysqld: Can't ope
n file: 'recordedmarkup.MYI'. (errno: 145)
Apr 9 00:09:44 mythtv kernel: set_rtc_mmss: can't update from 58 to 9
Apr 9 00:09:59 mythtv last message repeated 8 times
Apr 9 00:10:00 mythtv kernel: set_rtc_mmss: can't update from 58 to 10
Apr 9 00:10:33 mythtv last message repeated 13 times
Apr 9 00:10:57 mythtv last message repeated 12 times
Apr 9 00:11:01 mythtv kernel: set_rtc_mmss: can't update from 58 to 11
Apr 9 00:11:32 mythtv last message repeated 17 times
Apr 9 00:11:59 mythtv last message repeated 10 times
Apr 9 00:12:00 mythtv kernel: set_rtc_mmss: can't update from 58 to 12
Apr 9 00:12:34 mythtv last message repeated 19 times
Apr 9 00:12:50 mythtv last message repeated 7 times
Apr 9 00:12:51 mythtv mysqld[3430]: 060409 0:12:51 /usr/sbin/mysqld: Can't ope
n file: 'recordedmarkup.MYI'. (errno: 145)
Apr 9 00:12:52 mythtv mysqld[3430]: 060409 0:12:51 /usr/sbin/mysqld: Can't ope
n file: 'recordedmarkup.MYI'. (errno: 145)
Apr 9 00:12:55 mythtv kernel: set_rtc_mmss: can't update from 58 to 12
Apr 9 00:12:57 mythtv last message repeated 2 times


and from /var/log/dmesg I have:

kjournald starting. Commit interval 5 seconds
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
(fs/jbd/recovery.c, 255): journal_recover: JBD: recovery, exit status 0, recover
ed transactions 37045 to 37923
(fs/jbd/recovery.c, 257): journal_recover: JBD: Replayed 3742 and revoked 2/15 b
locks
kjournald starting. Commit interval 5 seconds
EXT3 FS on hde, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
ADDRCONF(NETDEV_UP): eth0: link is not ready
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Warning: /proc/ide/hd?/settings interface is obsolete, and will be removed soon!


Does this show anything?


Top
 Profile  
 
 Post subject:
PostPosted: Sun Apr 09, 2006 12:21 am 
Offline
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location: Fontana, Ca
The logs you need to look at vary... It all depends on what the issue is. Sorry, I'm not going to step you thru every possible issue and what log to take a look at... There are various post on the forum what logs and there is a page on the wiki about logs. From what you've posted, it looks like you need to check the db for errors. Yes, there is a post in Hints and Tips on this...

_________________
cesman

When the source is open, the possibilities are endless!


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 6 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu