<p>I'm pleased that worked out...</p>
<p>As aftermath. I urge that you make sure backups are brought up to "spec" so that the answer to as many such questions as possible can become... "And I solve this by restoring my backup."</p>
<p>I'm not familiar with MyISAM internals (let alone other engines like Solid, InnoDB, and such, which'll add to the opacity), but have fiddled little bits with Postgres and filesystems, and expect similar... If you get stuck recovering a failed DB/FS, it's near certain that all you really get is a set of more or less shattered fragments, as opposed to an actual database or filesystem.</p>
<p>It's like dropping a plate... Even if you are lucky enough to find all the pieces, you'll not likely ever be serving meals on it again.</p>
<p>Fancier porcelain may survive a bit more, but shattering is still shattering, and the metaphor fits pretty well.</p>
<p><blockquote type="cite">On May 9, 2010 10:50 PM, "William O'Higgins Witteman" <<a href="mailto:william.ohiggins@utoronto.ca">william.ohiggins-H217xnMUJC0sA/PxXw9srA@public.gmane.org</a>> wrote:<br><br><p><font color="#500050">On Sat, May 08, 2010 at 07:46:55PM +0000, <a href="mailto:ijaaz@digitalmethods.com">ijaaz-UwkSZrAjFfdkDLQDXwjzI9BPR1lH4CV8@public.gmane.org</a> wrote:<br>
>Couldn't you just copy /v...</font></p>No, at least not in this case - when mysql tried to start it made an<br>
effort and then barfed.<br>
<br>
The solution was that I still had a bootable hard drive from the dead<br>
server (it was MB failure that killed it), and I was able to boot it on<br>
another machine and do a dump, then pull the dump off to a USB stick and<br>
put everything back together again.<br>
<br>
Thanks for the help!<br>
--<br>
<br>
yours,<br>
<font color="#888888"><br>
William<br>
<br>
</font><br>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.10 (GNU/Linux)<br>
<br>
iD8DBQFL53ReHQtmiuz+KT8RAoH/AKCo3aMhlXh15KLPRRz4obE6XiQkCQCbBkhr<br>
bqd9n2A9v5aYLJHxiQVLLw4=<br>
=Ixu9<br>
-----END PGP SIGNATURE-----<br>
<br></blockquote></p>