is database corrupt ?

[lasto]

for some strange reason cant get into the board because of this error :

Invalid SQL:
SELECT COUNT(*) AS count
FROM post
WHERE dateline > '1111354169'

mysql error: Can't open file: 'post.MYI'. (errno: 144)

mysql error number: 1016

so first to do was to repair it - first tried by way of repair in admincp - still no luck whatsoever so went though phpmyadmin and after trying repair for about 5 times the same errors still come up.

new.post repair info Wrong bytesec: 0- 0- 0 at 20232512; Skipped
new.post repair error 5 when fixing table
new.post repair error Can't copy datafile-header to tempfile, error 9
new.post repair status Operation failed
new.post_parsed repair status OK

every other table says OK except ones above - where do i go from here or is it start afresh ???

just got this by running repair in admincp

post Check Warning: Table is marked as crashed and last repair failed
post Check Warning: 1 client is using or hasn't closed the table properly
post Check Warning: Size of indexfile is: 2538496 Should be: 1872896
post Check Warning: Size of datafile is: 28518948 Should be: 28516600
post Check Error: Can't read indexpage from filepos: -1
post Check Error: Corrupt

[Marco van Herwaarden]

If this is not because of a filesystem that has no space left, or some OS filesystem permissions have changed, i suggest you ask for help at vb.com or open a support ticket.

[lasto]

nope is new host only got it other day.Aint going to vb.com but thanks for the tip will wait here and see who can help as hate shunting from board to board when this is only one i use anyway.

[Dean C]

It doesn't look very healthy. It normally means corruption :(

[Marco van Herwaarden]

True there are a lot of helpfull people on vb.org and also a lot of knowledge. But for the speed of solving this, i suggested vb.com, because the official Jelsoft support people who are dealing with this kind of problems on an every day base, might be your fastest solution. And this is a typical problem that could (not saying must) be handled through official support channels.

I know i wouldn't burn my fingers on this problem, unless i was 100% sure ;)

[Dean C]

I get the impression that lasto's board is modified due to his large volume of posts here, so that would mean he wouldn't qualify for support at vB.com unfortunately :)

[Marco van Herwaarden]

You could try have a look at this page: http://dev.mysql.com/doc/mysql/en/crashing.html

I get the impression that lasto's board is modified due to his large volume of posts here, so that would mean he wouldn't qualify for support at vB.com unfortunately :)Repairing a corrupted post table on MySQL level, is hardly something that any hack could have something to do with. I would say that no matter how heavilly a board is hacked, help to recover a crashed database file on this level would be a legit support question.

[lasto]

well weird thing it was running perfect - but i installed a hack that dropped a table so i got the host to restore everything again though cpanel and went back to board - read a post and thats when the error appeared.

@dean - it aint that heavy hacked - main forum shows only 19 queries - every hack here i reply to i dont add to board but i like to mess with em on my computer on a test board to see what they got going for them.

And my database for the board is only 101 megs - hardly big in todays terms.

[Marco van Herwaarden]

lasto, did you host restore the OS files, or did he do another import?

[lasto]

just the sql database - prior to this the board was running fine except for an attachment problem but this i could fix.
The database looks restored fine though as i was on the board after it was restored and i even read a thread - it was when i went to read a another thread that the error kicked in but i suppose that error could of kicked in at any time.

[Marco van Herwaarden]

Well somehow the restored file is corrupted. Maybe because mysqld was still running while restoring the database on filesystem level.

Did you have a look at that mysql.com link? especially the part:
Stop the mysqld server with mysqladmin shutdown, run myisamchk --silent --force */*.MYI from the data directory to check all MyISAM tables, and restart mysqld. This ensures that you are running from a clean state. See Chapter 5, Database Administration.

Mind you i am guessing here, i have no real experience with this error.

But maybe a new restore would be a more secure way to go, if ofcourse the backup itself is not corrupt.

One more to look at: http://forums.mysql.com/read.php?20,16745,16745#msg-16745

[lasto]

cheers marco you been a great help - at moment am waiting for hosts as they are gonna take a look at it and see about another restore.
If that fails then im hoping my luck will hold out so i can grab the members/email/password etc and just copy them over to a new install and just start afresh and learn from this lesson.

well here whats i was hoping to do and that was take the users from the database and just overwrite the user table in a fresh install but already ran into a problem and that is inside the user table must be excess tables which obviously a fresh install would`nt need and because of this when i go to edits a member in admincp i get a mysql error.