Gunnar If the data is very important then don't do anything that will change the computer.
If you have sometools that can take an image copy of the disk (DD to another drive) or maybe the free accessdata imaging software then I would recommend doing this first - it will leave all options open should you wish to try something complex later. I have tools that can recover tables and rows from a damaged database, all they need is the schema of the original DB (the more complicated the bettter). The data can be recovered from the corrupt DB, from any journal files and also potentially from the swap file (or equivalent) or unused space on the hard disk. Records can also potentially be recovered from RAM - although in your case as the power has been off this is not going to work. The success of the operation depends on many factors but there is a fair chance that it won't be 100% acceptable - depending on the nature of the data (and any table constraints) this may be acceptable. It may also require some manual "filtering" of the recovered data as more simple tables are prone to include what can be best described as suprious results. Any old backups of the database can potentially be used to create a working solution. More information - the DB schema particularly - and what you need recovered for it to be a success (even a partial success) would be good. Paul www.sandersonforensics.com skype: r3scue193 twitter: @sandersonforens Tel +44 (0)1326 572786 http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit -Forensic Toolkit for SQLite email from a work address for a fully functional demo licence On 19 October 2015 at 18:51, gunnar <gharms at hiqinvest.nl> wrote: > Thanks a lot Simon! > We'll try it. > > > (BTW I also got an email from alexa, but looking in the sqlite mailing list > I can see that I'm not the only one) > > > > > On 10/19/2015 06:20 PM, Simon Slavin wrote: >> >> On 19 Oct 2015, at 5:13pm, gunnar <gharms at hiqinvest.nl> wrote: >> >>> We run sqlite with PRAGMA synchronous=OFF. >>> >>> Now we suffered from a 'hard reboot' because a sysadmin unplugged the >>> power cable :( >>> >>> Is it possible to repair >> >> First take a copy of the database file and any other file from the same >> directory with a similar name. This is just in case you decide to use >> heroic (i.e. expensive) means to rescue the database later. >> >> Open the proper (not the copy) database using the SQLite Shell Tool >> downloadable from the SQLite site. Use the '.dump' command to dump the >> database as a text file of SQL commands. >> >> Read through that file and see if it looks like it has captured all your >> data in it. If it has ... >> >> Create a new blank database using the SQLite Shell Tool. >> Use the '.read' command to execute the commands in the text file. >> Use various commands in the SQLite shell tool to explore the resulting >> database and see if it looks like it's worth using. >> >> Simon. >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users at mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >> > > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
