to get data into right place.

[Kailee]

Hello friends,
Recently, I found a HD crash in my server so had to recover the mysql files with recovery software. When reading the data, mysql said it was corrupted. I've tried with myisamchk --extended-check, recreating the table and using the new .frm and .myi., followed the instructions in the manual, but end up in the deadend of 'Wrong bytesec: 154-126-101 at linkstart: 0' and when I try to repair it, either with REPAIR TABLE or with myisamchk, I get 'Wrong bytesec: 154-126-101 at 0; Skipped' followed by a bunch of 'Found block that points outside data file' resulting on an empty data file.

I tried to debug myisamchk and got down to mi_dynrec.c, where the call to '_mi_get_block_inf' returns a info->header[0]=154, which sends a BLOCK_SYNC_ERROR back and generates the 'Wrong bytesec' error.

The documentation for BLOCK_SYNC_ERROR says /* Right data at wrong place */
so, how to get this data into the right place? Is there any applicat -- This message may have been cut off and the rest will only be shown to members. To become a member, click here --

[sierra]

One thing to remember is that there is nothing compressed by default. As long as you didn't use 'myisampack', everything should be in plain in .MYD.

To create a new index file from .MYD and .frm is to use the command REPAIR TABLE ... USE_FRM.

Check if your backup was done from a consistent state means was the server inactive or did you hold a global read lock? If so, there should be a way to get your data back. -- This message may have been cut off and the rest will only be shown to members. To become a member, click here --