My R5F1 box suddenly developed a fault whereby mysql appears to be unable to start.

Strange as it may sound, all I did to break it was to copy over a xorg.conf which I had set up previously (and had working with my HDTV). Maybe I caused a problem because I copied over the xorg.conf before exiting MythTV?

When my box comes up I notice a message about mysql failure, then it boots to a Myth screen where it prompts me to select my language, then goes to a server setup screen where everything appears to be ok.

in /vart/log/syslog I see the following messages ..

Jun 2 20:45:43 mythtv lircd-0.8.1-CVS-pvr150[3201]: lircd(all) ready
Jun 2 20:45:44 mythtv mysqld_safe[3272]: started
Jun 2 20:45:45 mythtv mysqld[3275]: 070602 20:45:45 InnoDB: Started; log sequence number 0 43665
Jun 2 20:45:45 mythtv mysqld[3275]: 070602 20:45:45 [ERROR] Fatal error: Can't open and lock privilege tables: File './mysql/host.MYD' not found (Errcode: 5)
Jun 2 20:45:45 mythtv mysqld_safe[3286]: ended
Jun 2 20:45:58 mythtv /etc/init.d/mysql[3421]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Jun 2 20:45:58 mythtv /etc/init.d/mysql[3421]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Jun 2 20:45:58 mythtv /etc/init.d/mysql[3421]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Jun 2 20:45:58 mythtv /etc/init.d/mysql[3421]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Jun 2 20:45:58 mythtv /etc/init.d/mysql[3421]:

does anyone have any suggestions how I might fix this?

<EDIT> I tried to restart mysql, but no joy

root@mythtv:/var/log# sudo /etc/init.d/mysql restart
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!

I have read of this problem, reported recently on the mythtv archive, unfortunately I haven't been able to find a solution there, it looks like it might mean yet another reinstall of R5F1,

thanks,

Kevin

Sounds to me like you whacked your /etc/mysql/my.cnf file. See http://forums.mysql.com/read.php?11,51024,51024 , make sure your datadir (and the other directory entries) is correct.

Hi,

my.cnf is there, in the /etc/mysql directory. I really don't know what it should look like, but at a glance it would look to be ok ..

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/serve ... ables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0

[mysqld]
old_passwords = false # inserted by debconf
# Activate the above for connections from hosts running Debian Woody/Sarge!
#
# Prior to MySQL 5.0, user passwords were stored in a rather weak way. This
# has been improved with the drawback that client programs shipped with
# Debian Woody/Sarge (technically: linked against libmysqlclient.so.12 or
# earlier) cannot connect any more if either their account has either been
# created or their password has been modified using MySQL 5.0.
# See http://dev.mysql.com/doc/refman/5.0/en/old-client.html
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
language = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
#
# * Fine Tuning
#
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 128K
thread_cache_size = 8
#
# * Query Cache Configuration
#
query_cache_limit = 1048576
query_cache_size = 16777216
query_cache_type = 1
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#
# The following can be used as easy to replay backup logs or for replication.
#server-id = 1
#log_bin = /var/log/mysql/mysql-bin.log
# WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!
#expire_logs_days = 10
#max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * BerkeleyDB
#
# According to an MySQL employee the use of BerkeleyDB is now discouraged
# and support for it will probably cease in the next versions.
skip-bdb
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
#skip-innodb
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer = 16M

#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the ndbd storage daemons,
# not from the ndb_mgmd management daemon.
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1

What does yield? And if it does exist, what are the permissions?

locate: warning: database `/var/cache/locate/locatedb' is more than 8 days old

-rw-r--r-- 1 root root 553448 May 11 01:02 /var/cache/locate/locatedb

On that long thread at the mysql forums, I saw some stuff about files needing to be owned by 'mysql', so might it be a problem that on my system they are owned by 'root'?

thanks,

Kevin

If you run updatedb this warning will go away.

Wrong file...

Yep, that's why I was asking about the permissions on host.MYD

updatedb worked, locate can now find 'host.MYD' but I can't query the permissions on it ..

root@mythtv:/var/lib/mysql# locate host.MYD
/var/lib/mysql/mysql/host.MYD
root@mythtv:/var/lib/mysql# ls -lart /var/lib/mysql/mysql/host.MYD
ls: /var/lib/mysql/mysql/host.MYD: Input/output error
root@mythtv:/var/lib/mysql# file /var/lib/mysql/mysql/host.MYD
/var/lib/mysql/mysql/host.MYD: ERROR: cannot open `/var/lib/mysql/mysql/host.MYD' (Input/output error)

Kevin

Better check your /var/log/syslog and /var/log/messages files, you may have a problem with your drive.

My host.MYD is an empty regular file This is on my R5D1 system. Can you remove host.MYD and recreate it?

slowtolearn,
looks like you were right, my drive seems to be hosed

I just got back after being out for few hours and turned on my Myth box from cold and saw the following messages:

Root: Multiply-claimed block(s) in inode 189210 : 469882 469883
Root: Multiply-claimed block(s) in inode 189215 : 469883
Root: Multiply-claimed block(s) in inode 189299 : 469882
Root: (There are 3 inodes containing multiply-claimed blocks.)
Root: File /var/log/auth.log (inpode #189210, mod time Sun Jun 3 09:08:20 2007)
Root: /var/log/debug (inode #189215, mod time Sun Jun 3 09:03:13 2007)
Root: /var/log/user.log (inode #189299, mod time Sun Jun 3 09:08:19 2007)
Root:
Root: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck died with exit status 4
failed (code 4)
* An automatic file system check (fsck) of the root filesystem failed.

I have just downloaded the SeaTools program from the Seagate website and are going to run some diagnostics.

This drive is just a few weeks old, now wonder they are selling for so little these days. Because it is OEM that probably means sending back to the manufacturer,

Kevin

That would certainly explain the issue you were seeing with the host.MYD file. No fun...

I have had very good luck with Seagate returns, they usually turn them around in less than a week.

slowtolearn,
I am wondering if shutting down my MythBox incorrectly could have caused this corrupt file system.
Normally I shut the box down via the KnoppMyth menu but my children over this past week have just been hitting the power button (because I haven't told them otherwise). Linux is pretty robust isn't it?

Also, I realize now that ever since installing R5F1 I have noticed some error, some fail message about fsck already mounted. Since Myth was coming up I assumed it was a bogus message, but perhaps I should have pain more attention to it.

BTW SeaTools has not found any problem yet with my drive, the short test passed ok and it is 75% through the long test. Not sure if it performs any writes to disk, I am assuming it does otherwise it is not much use as a diagnostic tool,

Kevin

Yes it is, but it isn't impervious to abuse (ungraceful shutdowns).

Once that is done you'll want to backup any media/files that you don't want to lose!

Assuming the disk passes the tests, try a manual fsck on it - Boot from the CD, quit out of setup as soon as you get a chance and fsck /dev/hda1 and /dev/hda3 (substitute appropriate devices). Hopefully there's no physical issue with the drive.

When I want to really hit the drive I'll use fsck -cDkvy /dev/xxx. WARNING: this can be dangerous and cause you to lose files. It can also take a very long time, depending on the size of the filesystem.

I realise now that the PC case I used to build my MythTV box is very old and certainly pre-SATA and pre-Athlon. I have a modern PSU I am going to use to replace the old one, I don't think my current PSU is really up to the job. The new PSU was from my work computer and had to be replaced as it had an issue not powering up with some Asus motherboards, hopefully it will boot with my M2NPV.

Thanks for the tips on running fsck, I will let you know how I get on. Probably be a few days,

Kevin