Irrelevant. What is preventing slapd from starting up? If the loglevel statement in your slapd.conf is still set to "none", comment it out, or set it to something more helpful (like 256), restart slapd and see what shows up in the syslog. If that doesn't give you enough information, increase the loglevel until it tells you why it's not starting up.
No amount of adjusting the loglevel in slapd.conf/slapd-config is going to help you get information on why slapd won't start if it never gets far enough to open syslog. Which is why I've suggested using slapd level debugging.
But most likely, the db simply needs to be recovered via the db_recover command, which I've already pointed Scott at.
--Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration