As you may have noticed. Our website is in rough shape. It "works", but the SQL errors abound and cause for an ugly rendering of the page. Even if you don't understand what tha means, jump out of your RSS reader and come take a look.
Anyway, it has been going on for a very long time. My hosting company keeps putting me off with, and I paraphrase, "we have priority jobs". First it was on my shared database server on the fritz and then it was on another server needing to be rebuilt over the weekend. They are making statements like you have to understand these guys manage like a thousand servers and I'm thinking, "which means they should be able to handle it professionally!" I know what it takes to handle a server rebuild. A lot of it is standing around watching, time that could be used to help others. Requests to talk with people up the line have been ignored by those receiving the request.
It isn't my habit to point out an ugly looking site, but after it taking this long to get fixed I suppose some sort of message is due. I'm not just ignoring it, but it would seem my host is.
I'll leave you with this thought of the day, The true test of quality tech support is the fires of major unexpected outages.
:-) Wish I'd seen Greg's comments a bit earlier. That's pretty much what I did. It was a cache so I deleted it, rebuilt in and it got repopulated.
The "Can't open file: 'cache_page.MYI' (errno: 144) indicates a corrupted table. Best route is probably to extract all of the data that you can from the table and re-create it using phpmyadmin or whatnot. If cache_page only holds temporary data (page caching for the cms), then it can be dropped and recreated with no ill effect hopefully :)
Goes away upon login.
I find that rather odd, so it must be something tied to the permissions, I would assume.