I've seen this when I killed mysqld (yeah I know, bright move) when I figured "optimize database" took too long from within URD (so I was new, gimme a break
Anyway, you should not loose the entire DB, at worst the parts_18318. Quickest fix, if you can live with it, is to purge that group (or purge the table manually) and rebuild it. Probably it's just not considered "consistent" since mysqld died when your IDE problem happened, and you will not loose any data (my guess).
I was able to fix my table (fairly big one btw) by using myisamchk as suggested by spearhead. (mysql should be stopped when doing this)
Here's some fairly straightforward infohttp://dev.mysql.com/doc/refman/5.0/en/myisam-repair.html