Thank you for your replies. I attempted to restore again and most
oddly, mysql complained that it couldn't restore to a particular
table because it wasn't in the database, which, of course, it had to
be because the restore itself had just recreated it. So I blew away
the entire mysql directory on the disk, updated to 5.0.45, and then
it did not complain when I restored that time. So far, it has not
since.


>Hi
>This might be happening due to two reasons;
>1 The system date might not be correct.
>2. Some things wrong with log postion (Incorrect log position)
>
>Regards,
>Krishna Chandra Prajapati


>The checksum errors might be due to various reasons. We had similar
>issue where we restored the database multiple times, replaced the
>ram sticks nothing ed. Finally we drilled down the issue to the
>chassis. Recommend testing the restore on a different machine to
>rule out any hardware issue.
>
>--
>Thanks
>Alex
><http://alexlurthu.wordpress.com>http://alexlurthu.wordpress.com


>On 8/31/07, Maurice Volaski
><<mailto:mvolaski@aecom.yu.edu>mvolaski@aecom.yu. edu> wrote:
>
>A 64-bit Gentoo Linux box had just been upgraded from MySQL 4.1 to
>5.0.44 fresh (by dumping in 4.1 and restoring in 5.0.44) and almost
>immediately after that, during which time the database was not used,
>a crash occurred during a scripted mysqldump. So I restored and days
>later, it happened again. The crash details seem to be trying to
>suggest some other aspect of the operating system, even the memory or
>disk is flipping a bit. Or could I be running into a bug in this
>version of MySQL?
>


--

Maurice Volaski, mvolaski@aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University