My system keeps / on an IDE drive and /myth on a VG grown on a SATA drive. The IDE drive started getting read errors, so I booted from the CD, fsck'ed the drive, and copied everything to a new drive. I had to copy a couple of directories from the CD, but it looked as though I got everything ok. I pulled and tossed the old drive, booted from the new drive, and started running into problems with mythweb. I figured, "must've missed something when I replaced the drive", so I figured I'd run mythbackup, reinstall, and run mythrestore. Trouble is, mythbackup fails. It throws the following error while trying to dump the mythconverg tables:
...
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld.
Checking for corrupt, not cleanly closed and upgrade needing tables..
mysqldump: Got error: 29: File './mythconverg/recordedseek.MYD' not found (Errcode: 13) when using LOCK TABLES
Restarting MythTV server: mythbackendNo /usr/bin/mythbackend found running; none killed.
....

and at the end of the backup script, it announces:

Checking for the existance of the DB dump file...
Using file /myth/backup/mythconverg.sql.gz
DB dump file exists. Checking the compression...
Compression looks OK. Checking DB dump contents...
Generating a list of tables and record counts in the DB dump...
Warning, could not get record counts from DB dump!

The backup is bad or already out of date!


I stopped mysql and mythbackend and ran myisamchk against everything in mythconverg, and found no problems. Anyone have any ideas how to proceed? I kind of need to get the box back in trim, as Universal's gonna start showing Battlestar in HD tonight and $spouse says "record it or die"

Ok, never mind. Some digging around on mysql.com turned up that "Errcode: 13" is a permissions error. Turns out that, whilst everything *else* was owned by mysql:mysql, recordedseek.MYD was owned by root:root. Changing ownership on the file fixed the problem and I got a clean backup.

You may now return to your regularly scheduled programming.

The good news is that the backup sanity checks work...