Log in

View Full Version : MySQL error


[D]Vincent
08-11-2002, 01:47 AM
Vincent]If you go to www.fflounge.com/board you will see my forums are down because of a database error. When I try and do the repair thing for my tables it also gives me an error. First off I can't even go to access because it gives me this error:
Database vbforums - table access
[ Browse ] [ Select ] [ Insert ] [ Empty ]

Error
SQL-query : [Edit]

SHOW KEYS FROM `access`

MySQL said:


Can't open file: 'access.MYD'. (errno: 144)

Back
And I can't open annoucement because of this error:
[ Browse ] [ Select ] [ Insert ] [ Empty ]

Error
SQL-query : [Edit]

SHOW KEYS FROM `announcement`

MySQL said:


Can't open file: 'announcement.MYD'. (errno: 144)

Back
And the same things with searchindex and user.
And when I do hit the Repair link on a table I can go to it gives me this(this happens on them all not just forum):
Database vbforums - table forum
SQL-query

SQL-query : [Edit]
REPAIR TABLE `forum`




Table Op Msg_type Msg_text
forum repair error 28 when fixing table
vbforums.forum repair status Operation failed
Anyone have an idea of what to do or what went wrong?

[D]Vincent
08-11-2002, 03:03 AM
Anyone at all?

[D]Vincent
08-11-2002, 03:28 AM
Vincent]I checked my e-mail and this is the error they sent me:
Database error in vBulletin 2.2.6:

Invalid SQL: SELECT user.*,userfield.* FROM user LEFT JOIN userfield ON userfield.userid=user.userid WHERE user.userid='53'
mysql error: Can't open file: 'user.MYD'. (errno: 144)

mysql error number: 1016

Date: Sunday 11th of August 2002 05:26:20 AM
Script: http://www.fflounge.com/board/board/index.php?s=
Referer:

Can someone please help me out my members are going to kill me if I go on AIM >_<

Logician
08-23-2002, 09:06 AM
apply:
repair user
repair access

and other "repair (tablename)" commands for all tables that give errors..It's MYSQL table corruption..

[D]Vincent
08-23-2002, 09:10 AM
Vincent]No ++++ sherlock, I already got it fixed, anyways it gave me an error at the time when I tried repairing, ended up being the problem of my ++++ty host :rolleyes: