lost 20 thousand posts after a error 127 from table handler

[serge M]

IchBin, sorry for not reading your post in total when I wrote mine.

well, I have a recycle board, but only if you delete thru the forum the posts go there. anything deleted or lost directly in the
DB does not go the recycle board, so this is no help at all. there is no posiibility, that those posts have been deleted from
the forum, they have gone from the DB directly.

Backing up the DB before repair would not help, the data was already lost.

nightbre, thanks for that point. the host keeps old data for 48 hours, nothing is there anymore to be reconstructed. I
asked them immediately, but they responded too late.

[Adish - (F.L.A.M.E.R)]

I could possibly have a look into your website if you want me to. Dunno what I may find out, but you might get lucky...

(I can't have a look at it for at least the following 12 hours unfortunately. Yeeeay! my laptop is coming back tomorrow from some hardcore operation.)

[serge M]

(F.L.A.M.E.R.) thank you a lot, would be most appreciated. www.jaguarclubpoland.net/forum let me know if you need some
more information. keep my fingers crossed for your laptop!

[Adish - (F.L.A.M.E.R)]

I meant the website from inside with the control panel login, admin login for SMF and database login if separately accessed instead through the control panel.

You can PM me the details as they are not safe to be shown publically.

[serge M]

I presupposed that  sent you a PM, thank you a lot for your offer to help.

[JimM]

After doing a bit of research on this here is what I found.  This appears to be a documented bug in MySQL 4.0.  It's reported when there is enough corruption in a table that MySQL is not able to read the data properly.  Some causes were listed as: 1) The mysqld process being killed in the middle of a write 2) The hardware that the database resides on losing power unexpectedly, 3) A hardware error.

From what I could find, repairing the table as you did is what was recommended and some data loss is to be expected when this happens.  It is normally minimal.

You can find more information here on the documented bug >>> http://bugs.mysql.com/bug.php?id=1711

It is your host responsibility to make sure the server software is the most up to date.  In this case they didn't and you have to suffer for it.  Bottom line is you need a new host.

[serge M]

JimM, thank you so much for that. I will look it through, sounds logically but:

it says "Running CHECK TABLE on all involved tables reveals nothing"

in my case, running CHECK TABLE at smf_messages showed the 127 error so it was
obvious for me to repair that one specific table. I keep on reading.

Well, no doubt about to change the host after all that, that was obvious already.

[serge M]

I did run a query on my sql and it turned that the actual version is:

4.0.27-max-log

so this seems to be a dead road as the bug was fixed in version 4.0.17 

well, anyhow, thank you a lot for your help JimM!

[Night09]

nightbre, well this topic is not really about the hosts responsibility although this is an interesting aspect of the hole thing
and I shall be happy about any opinion in this direction. this might be interesting also for others, in case they face similar
problems.

Ah sorry, I got the impression from your posts you were looking toward the host side of it so apologies for the confusion.

[JimM]

OK, sorry you are having this difficulty but there really isn't anything we can do.  I'll go ahead and mark this one as solved so that it doesn't appear in the support queue anymore.  If you have additional information feel free to unmark it.