vBulletin Database Error

[matt_turpin]

I'm usually decent at troubleshooting minor forum ailments, but this one is beyond me. Any tips on possibly rectifying this issue would be greatly appreciated. I'll paste the error report.

Database error in vBulletin 3.7.2:
Invalid SQL:
  SELECT picture.pictureid, picture.userid, picture.caption, picture.extension, picture.filesize,
   picture.width, picture.height, picture.reportthreadid, picture.state,
   picture.idhash, picture.thumbnail_filesize, albumpicture.dateline, albumpicture.albumid
  FROM albumpicture AS albumpicture
  INNER JOIN picture AS picture ON (picture.pictureid = albumpicture.pictureid)
  WHERE albumpicture.albumid = 1
   AND albumpicture.pictureid = 179;
MySQL Error   : Table './buchisdm_buchisdma/picture' is marked as crashed and last (automatic?) repair failed
Error Number  : 144
Request Date  : Tuesday, August 5th 2008 @ 06:35:28 AM
Error Date    : Tuesday, August 5th 2008 @ 06:35:28 AM
Script        : [URL]http://www.buchisdma.com/forums/album.php?albumid=1&pictureid=179[/URL]
Referrer      : 
IP Address    : 66.212.205.234
Username      : Pompidou
Classname     : vB_Database
MySQL Version : 5.0.51a-community

The symptoms of the problem are that photo albums are broken. Viewing them brings an error screen of doom with the above displayed.

[copiertalk]

try to repair the table in the maint section of the admin cp or contact your host and see if they can help.

I would backup first just to have a copy of your data when doing anything with the database. you may have to run the repair table in the admincp a couple of times.

[matt_turpin]

I did a database repair and narrowed down the problem, and recieved this feedback:
pictureCheckWarning: Table is marked as crashed and last repair failed
pictureCheckWarning: Size of indexfile is: 9216 Should be: 7168
pictureCheckError: Record-count is not ok; is 236 Should be: 127
pictureCheckWarning: Found 289 parts Should be: 127 parts
pictureCheckError: Corrupt

[Steve Machol]

To fix this run Repair/Optimize in the Admin CP. You may need to run it more than once to fix all errors:

Admin CP -> Maintenance -> Repair/Optimize Tables -> Check All -> Continue

If you cannot access the Admin CP you can also use phpMyAdmin to repair tables.

If that doesn't work then this may be too damaged to fix with the normal methods. Please check out this thread for other ways to repair a db, particularly items #2 and 3:

http://www.vbulletin.com/forum/showthread.php?s=&threadid=44909

You may have to ask your host to try and repair this for you.