Maybe you have a broken harddrive too, but this was hardly the reason for the dovecot crash, so better buy another server.
On 5/3/06, Gerald Dachs <gda@gmx.de> wrote:
I really don't know why I answer you again, you even don't read my answers. I will try it a last time and repeat my answer from the last mail: This is caused most likely by bad memory or too hot cpu. well in that u may be right :)
the hard disk is working with MBR 0 BROKEN :)) how do i am able to run debian in a broken hard drive ? well need make us sometime to do something like magic , i gess im obligated to save all the stuffs on the computer and try to get a new hard drive
good luk 4 me
grab this cd http://www.ultimatebootcd.com/ , boot your
i ll ckeck but i know i have to get a new hard drive
computer with it
and check whether cpu or memory has a problem. Reinstalling something does not help, this is not windows.
Gerald
uff i missed 1 more step
check this oput there is the full bug
tell me what u think
http://channels.debian.net/paste/2480
is there a solution ? or i have to reinstall ? or migrate to other version? On 5/3/06, Gerald Dachs <gda@gmx.de> wrote:
you got an answer from me, that it was not an answer to your question is another thing.
Core was generated by `imap'. Program terminated with signal 11, Segmentation fault.
This is caused most likely by bad memory or too hot cpu.
Gerald