Of course a long holiday weekend and a client project due make for perfect timing for a server crash and a good test of my computer problem solving skills, patience, and TKLBAM restore.
Not sure what the server was doing when I accidentally shut it down, but it didn't want to come up. As a matter of fact, there's a good probably it's days are done, and I'm just using costly end-of-life care at the moment, such as the Vertex 4 SSD I bought to see if I could revive it.
Biggest problem was the BIOS not recognizing the relatively new (~ 1 year) WD 500GB Green HDD, which had my TKL LAMP as the main OS, as well as a few VMs and other goodies -- Cloudprint, Logitech Media Server, PHPVirtualBox, etc.
So I can't get the box to boot off the WD500 HDD, even though all the tools in Parted Magic and Boot-Repair-Disk say it's just fine (this is one reason I'm thinking the mobo is hosed). Replaced the SATA cables. Installed the SSD and used UnetBootin to create a LiveUSB of the latest Turnkey LAMP. I can get it to boot from the SSD, to Webmin and run TKLBAM Restore, then it all goes to hell...
I tried it once, and couldn't reboot the machine. Wiped the SSD and reinstalled TKL LAMP, booted, ran TKLBAM Restore, and now have this error:
Download s3://s3.amazonaws.com/tklbam-[ lettersandnumberscode ]/duplicity-full.[ lookslikeacacatenationofmylastfullbackdateandid ].vol28.difftar.gpg failed (attempt #1, reason: BotoServerError: BotoServerError: 500 Internal Server Error <?xml version="1.0" encoding="UTF-8"?> <Error><Code>InternalError</Code><Message>We encountered an internal error. Please try again.</Message><RequestId>C9AF3DD7C870D7F1</RequestId><HostId> [ areallylongseriesoflettersandnumbersthatIdon'tknowiftheyareimportant ]</HostId></Error>)
[UPDATE] I "tried again" on the recommendation of the above error:
Local and Remote metadata are synchronized, no sync needed. Last full backup date: Sat Nov 10 12:37:26 2012
Yeah... I don't think so.
Any way to "force" the Restore to happen? For example:
tklbam-restore 4 --noninteractive --force
FYI, I'm restoring a 10.x LTS on top of the 12.x Debian version.