My server crashed with a raid corruption. I've rebuilt the raid, restored the filesystem and zimbra, and am now getting a "zmmailboxdctl is not running" in zmcontrol status. Seems there is a transaction suspended in the database causing the mailbox to crash on startup. I have not been able to clear it. Any suggestions would be much appreciated.

output of mailbox.log:

2014-04-23 09:41:14,284 INFO [main] [] redolog - Starting pre-startup crash recovery
2014-04-23 09:41:15,315 INFO [main] [] redolog - Redoing 2 uncommitted transactions
2014-04-23 09:41:15,316 INFO [main] [] redolog - REDOING: txn 1398099855.1 [CreateMessage] ver=1.31, tstamp=1398099861854, change=331200, mailbox=20, id=188560, rcpt=jim@mydomain.com, rcvDate=1398099861851, shared=false, blobDigest="O0p4BrCZlM2kLPwhjfC7RVfj5IM=", size=21586, dataLen=21586, folder=4, conv=-1, convFirstMsgId=-1, calItemPartStat=NE, noICal=false, flags=512, tags="", bodyType=1, path=/opt/zimbra/store/incoming/1398099855497-1.msg
2014-04-23 09:41:15,667 INFO [main] [] index - Initialized Index for mailbox 20 directory: LuceneIndex{mbox=20, dir=org.apache.lucene.store.NIOFSDirectory@/opt/zimbra/index/0/20/index/0 lockFactory=org.apache.lucene.store.SingleInstance LockFactory@66bb1ead} Analyzer=com.zimbra.cs.index.ZimbraAnalyzer@6db248 c
2014-04-23 09:41:15,668 INFO [main] [] cache - initializing folder and tag caches for mailbox 20
2014-04-23 09:41:15,788 INFO [main] [] mbxmgr - Mailbox 20 account 962b9958-c9a3-44e2-9f22-cec1060e593b LOADED
2014-04-23 09:41:16,578 INFO [main] [] zimlet - Loaded class com.zimbra.cs.zimlet.handler.NANPHandler
2014-04-23 09:41:16,588 INFO [main] [] zimlet - Loaded class com.zimbra.cs.zimlet.handler.RegexHandler
2014-04-23 09:41:16,737 INFO [main] [] mailop - Adding Message: id=188560, Message-ID=<0.0.0.61.1CF5D50AA0BCB46.EFA6@popconserve.us>, parentId=-1, folderId=4, folderName=Junk.
2014-04-23 09:41:16,757 WARN [main] [] store - Destination file exists. Backing up to /opt/zimbra/store/0/20/msg/46/188560-331200.msg.bak
2014-04-23 09:41:16,758 WARN [main] [] store - /opt/zimbra/store/0/20/msg/46/188560-331200.msg.bak already exists. Deleting to make room for new backup file
2014-04-23 09:41:16,836 FATAL [main] [] system - Unable to commit database transaction. Forcing server to abort.
com.zimbra.common.service.ServiceException: system failure: committing database transaction

Also seeing this in zmdbintegrityreport:

zimbra@mail:~/log$ /opt/zimbra/libexec/zmdbintegrityreport -v -r
Database errors found.
/opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password=ex_BhkVJmF9xBKkQD53qclIkMb --auto-repair
mboxgroup21.mail_item
Warning : InnoDB: Index 'i_tags_date' contains 6953 entries, should be 6954.
error : Corrupt
mboxgroup58.mail_item
Warning : InnoDB: Index 'i_parent_id' contains 7583 entries, should be 7584.
Warning : InnoDB: Index 'i_index_id' contains 7583 entries, should be 7584.
Warning : InnoDB: Index 'i_unread' contains 7583 entries, should be 7584.
Warning : InnoDB: Index 'i_date' contains 7583 entries, should be 7584.
Warning : InnoDB: Index 'i_mod_metadata' contains 7583 entries, should be 7584.
Warning : InnoDB: Index 'fk_mail_item_volume_id' contains 7583 entries, should be 7584.
error : Corrupt
mboxgroup81.mail_item
Warning : InnoDB: Index 'i_name_folder_id' contains 227 entries, should be 226.
Warning : InnoDB: Index 'i_type' contains 227 entries, should be 226.
Warning : InnoDB: Index 'i_parent_id' contains 227 entries, should be 226.
Warning : InnoDB: Index 'i_folder_id_date' contains 227 entries, should be 226.
Warning : InnoDB: Index 'i_index_id' contains 227 entries, should be 226.
Warning : InnoDB: Index 'i_unread' contains 227 entries, should be 226.
Warning : InnoDB: Index 'i_date' contains 227 entries, should be 226.
Warning : InnoDB: Index 'i_mod_metadata' contains 227 entries, should be 226.
Warning : InnoDB: Index 'i_tags_date' contains 227 entries, should be 226.
Warning : InnoDB: Index 'i_flags_date' contains 227 entries, should be 226.
Warning : InnoDB: Index 'i_volume_id' contains 227 entries, should be 226.
Warning : InnoDB: Index 'fk_mail_item_volume_id' contains 227 entries, should be 226.
error : Corrupt
mysql.general_log
Error : You can't use locks with log tables.
mysql.slow_log
Error : You can't use locks with log tables.
mboxgroup21.mail_item
note : The storage engine for the table doesn't support repair
mboxgroup58.mail_item
note : The storage engine for the table doesn't support repair
mboxgroup81.mail_item
note : The storage engine for the table doesn't support repair
zimbra@mail:~/log$


Thanks for taking a look.