mysql 5.5 crash on Debian 6 - stuck in endless restart loop

mysql 5.5 crash on Debian 6 - stuck in endless restart loop

After a server crash my mysql dB crashes. During startup it produces
36,000 lines in syslog, and I have no idea how to repair this. I had
master slave replication setup , but I have no idea what to do with the
slave.
The databases contain email server records and no one can use Email anymore.
The versions are :
ii libdbd-mysql-perl 4.016-1
Perl5 database interface to the MySQL database
ii libmysqlclient16 5.1.66-0+squeeze1
MySQL database client library
rc libmysqlclient18 5.5.30-1~dotdeb.0
MySQL database client library
ii libqt4-sql-mysql 4:4.6.3-4+squeeze1
Qt 4 MySQL database driver
ii mysql-client 5.5.31-1~dotdeb.0
MySQL database client (metapackage depending on the latest version)
ii mysql-client-5.5 5.5.31-1~dotdeb.0
MySQL database client binaries
ii mysql-client-core-5.5 5.5.31-1~dotdeb.0
MySQL database core client binaries
ii mysql-common 5.5.31-1~dotdeb.0
MySQL database common files, e.g. /etc/mysql/my.cnf
ii mysql-server 5.5.31-1~dotdeb.0
MySQL database server (metapackage depending on the latest version)
rc mysql-server-5.1 5.1.58-1~dotdeb.1
MySQL database server binaries and system database setup
ii mysql-server-5.5 5.5.31-1~dotdeb.0
MySQL database server binaries and system database setup
ii mysql-server-core-5.5 5.5.31-1~dotdeb.0
MySQL database server binaries
All I would like to do is rollback any trnasactions and then get this dB
running again. I've searched on Google for lots of help, but they refer to
many items that I simplay do not understand how to use. For example I
tried innochecksum, and the man page states just type the command, and
then within it tell it to scan tables files: There are no table files in
/var/lib/mysql/tablename/*, and this command is not interactive. Hence the
confusion.
Can anyone help me out here because I really an in at the deep end.
Many thanks, Simon
The syslog mysql messages read: I cannot post the messages because
serverfault thinks these are links, and I do not have permission to paste
linkes, even though it's the contents of syslog.