I just went through the LVM sticky walk through. Despite the ugly post I made in there about being unable to mount the volume to /mnt/sdb1 the process went okay. I was able to copy all of /var/lib into my new lvm partition and then extend the volume to include the left over space on /dev/sda. df -h show the following:

Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             9.2G  1.5G  7.3G  17% /
varrun                506M  216K  506M   1% /var/run
varlock               506M     0  506M   0% /var/lock
udev                  506M  104K  506M   1% /dev
devshm                506M     0  506M   0% /dev/shm
lrm                   506M   34M  472M   7% /lib/modules/2.6.22-14-generic/volatile
/dev/mapper/vg-lib    585G   81G  504G  14% /var/lib
I've verified that all of the data in my previous /var/lib is in my new volume. But when I try to open up mythfrontend I get the backend setup tool. I choose English and then it says that "Myth could not connect to the database"

I can verify that the mythconverg database exists in /var/lib/mysql. If I attempt to run /etc/init.d/mysql start it fails.

Is there some sort of repair utility I can run? Or is there some mysql log file I can look into to see why it's failing?