[mythtv-users] unable to watch recordings

[Steve Daniels]

> -----Original Message-----
> From: mythtv-users-bounces at mythtv.org [mailto:mythtv-users-
> bounces at mythtv.org] On Behalf Of sarvin
> Sent: 23 June 2006 17:15
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] unable to watch recordings
> 
> 
> On Jun 23, 2006, at 2:57 AM, Steve Daniels wrote:
> 
> >
> >> -----Original Message-----
> >> From: mythtv-users-bounces at mythtv.org [mailto:mythtv-users-
> >> bounces at mythtv.org] On Behalf Of sarvin
> >> Sent: 23 June 2006 06:20
> >> To: Discussion about mythtv
> >> Subject: [mythtv-users] unable to watch recordings
> >>
> >> Unfortunately I lost power to my MythTV and the computer was shutdown
> >> improperly. For some reason I'm not able to watch recorded or live
> >> T.V. any longer. The logs look fine, mysql and mythbackend both start
> >> fine as well. I'm not sure what the problem is or where to look. Any
> >> advice would be greatly appreciated.
> >
> > You say the logs look fine, did you also look at the mysql logs and
> > check
> > the tables, just because it starts doesn't mean mysql has clean and
> > tidy
> > uncorrupted tables ready for mythbackend to play with.
> >
> > HTH
> >
> > Steve
> 
> mysqld.err produces:
> 
> InnoDB: Starting crash recovery.
> InnoDB: Reading tablespace information from the .ibd files...
> InnoDB: Restoring possible half-written data pages from the doublewrite
> InnoDB: buffer...
> 060622 21:05:07  InnoDB: Starting log scan based on checkpoint at
> InnoDB: log sequence number 0 55130.
> InnoDB: Doing recovery: scanned up to log sequence number 0 55130
> InnoDB: Last MySQL binlog file position 0 79, file name ./Athlon64-
> bin.000315
> 060622 21:05:08  InnoDB: Flushing modified pages from the buffer pool...
> 060622 21:05:08  InnoDB: Started; log sequence number 0 55130
> /usr/sbin/mysqld: ready for connections.
> Version: '4.1.14-log'  socket: '/var/run/mysqld/mysqld.sock'  port:
> 3306  Gentoo Linux mysql-4.1.14-r1
> 060622 21:05:20 [ERROR] /usr/sbin/mysqld: Can't open file:
> 'mythlog.MYI' (errno: 145)
> 060622 21:05:20 [ERROR] /usr/sbin/mysqld: Can't open file:
> 'mythlog.MYI' (errno: 145)
> 060623  0:00:20 [ERROR] /usr/sbin/mysqld: Can't open file:
> 'mythlog.MYI' (errno: 145)
> 060623  0:00:20 [ERROR] /usr/sbin/mysqld: Can't open file:
> 'mythlog.MYI' (errno: 145)
> 060623  0:02:15 [Note] /usr/sbin/mysqld: Normal shutdown
> 
> 060623  0:02:15  InnoDB: Starting shutdown...
> 060623  0:02:18  InnoDB: Shutdown completed; log sequence number 0 55166
> 060623  0:02:18 [Note] /usr/sbin/mysqld: Shutdown complete
> 
> 060623  0:02:23  InnoDB: Started; log sequence number 0 55166
> /usr/sbin/mysqld: ready for connections.
> Version: '4.1.14-log'  socket: '/var/run/mysqld/mysqld.sock'  port:
> 3306  Gentoo Linux mysql-4.1.14-r1
> 060623  0:04:09 [Note] /usr/sbin/mysqld: Normal shutdown
> 
> Other than that, everything else appears normal.
> I've run optimize_mythdb.pl in the hopes that that might solve the
> problem. How would I check the tables?

Hiya,

> InnoDB: Starting crash recovery.

Seems ominous..

060622 21:05:20 [ERROR] /usr/sbin/mysqld: Can't open file:
> 'mythlog.MYI' (errno: 145)

Is definitely an error that you do not want happening.

Running the optimize_mythdb.pl should fix all these problems though.. IIRC
anyway.

But it sounds like you are still experiencing problems. Do you have a good
backup to revert to?

Sorry I can't be of more help :-(

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.2/373 - Release Date: 22/06/2006