 Summary
solved by the fsck.e3fs -cvf which is manually answering every question of the check tool. this really is the luck that just one of it is the ibdata file repaired, and I copy them it works.
conclusion, the other ways I have checked before moving to the last solution, which I saw all of them need a live connection to the mysql backend, as in this case there is no way of it, and no incremental backups there is no other mysql binlog in the zimbra system, so in case if hard corruption in the ibdata or ib_logfile not work even with innodb_force_recovery = 6, there is no way in zimbra 6.0.0 as tested.
so having a routine backup is a must! |