<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Steve Daniels wrote:
<blockquote cite="mid449c2257.1910c042.2ace.13c7@mx.gmail.com"
type="cite">
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:mythtv-users-bounces@mythtv.org">mythtv-users-bounces@mythtv.org</a> [<a class="moz-txt-link-freetext" href="mailto:mythtv-users">mailto:mythtv-users</a>-
<a class="moz-txt-link-abbreviated" href="mailto:bounces@mythtv.org">bounces@mythtv.org</a>] 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:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:mythtv-users-bounces@mythtv.org">mythtv-users-bounces@mythtv.org</a> [<a class="moz-txt-link-freetext" href="mailto:mythtv-users">mailto:mythtv-users</a>-
<a class="moz-txt-link-abbreviated" href="mailto:bounces@mythtv.org">bounces@mythtv.org</a>] 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.
</pre>
</blockquote>
<pre wrap="">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
</pre>
</blockquote>
<pre wrap="">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?
</pre>
</blockquote>
<pre wrap=""><!---->
Hiya,
</pre>
<blockquote type="cite">
<pre wrap="">InnoDB: Starting crash recovery.
</pre>
</blockquote>
<pre wrap=""><!---->
Seems ominous..
060622 21:05:20 [ERROR] /usr/sbin/mysqld: Can't open file:
</pre>
<blockquote type="cite">
<pre wrap="">'mythlog.MYI' (errno: 145)
</pre>
</blockquote>
<pre wrap=""><!---->
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 :-(
</pre>
</blockquote>
Does that file exist? If so it might be ownership roblems. chown it
to mysql:mysql. Once that is done running "myisamchk -f *.MYI" in that
directory is also not a bad idea. Do all this with myth totally shut
down.<br>
<br>
W<br>
</body>
</html>