BSOD results in SQLite, Google Drive failure
I am losing count, having just recovered from the third or fourth Google Drive failure in a month across two PC's. This latest followed an unexpected shutdown, (a BSOD of an as yet unknown nature), which left a SQLite database in an unusable state:
Google Drive needs to be closed.
...unknown error occurred and Google Drive needs to be closed.
Error: database disk image is malformed
If you continue to see this error, try to disassociate your account
[*sigh*]
One Google (overlord) Groups thread from 2012 suggests using other services. e.g. EverNote, DropBox, and even (gasp!) Microsoft SkyDrive--Really?
(Lord) Google searches revealed that virtually anyone with some SQL skills might be able to recover from this. I am not a DBA. Having some very skilled DBA's at work has resulted in my leaving that skillset wanting....
Folks working in I.T. and/or with related skills can generally deal with and recover from interruptions/failures like these one way or another. (Incident response is something I enjoy--solving interesting & difficult puzzles in an almost House M.D. manner, which probably makes me some sort of Holmesian-Windows-barbarian, who knows). Considering some of the rubbish I have encountered with Google Drive, it is difficult to imagine folks with different skillsets responding to these interruptions. Either of my brothers would react vehemently, and perhaps rightfully so. Anyhow. Not cool, Lord Google.
There's a post on Twitter by Arul Dhesiaseelan (@aruld) which mentions Google Drive uses SQLite and includes a capture of an oft-encountered earlier Google Drive failure, (for which a search via...your favorite search engine will demonstrate others have also encountered this), "...PRIMARY KEY must be unique". Another one which, for most folks including myself, means starting from scratch and downloading everything again. (Where the hell is the frowny-face emoticon in Blogger?).
Now, in true geek (really hacker, but thanks to the media, that's usually used incorrectly--see cracker) fashion, we ought to be able to automate the backup any SQLite database that Google Drive uses and restore it from a backup, quickly & easily. This is especially important since Google Drive appears to be in some sort of immature, pre-release, beta state. (Where the hell is a good Slashdot article when you need one).
Hopefully in a future post: my humble attempts to automate backing up the Google (overlord) Drive SQLite DB in Windows.
Google Drive needs to be closed.
...unknown error occurred and Google Drive needs to be closed.
Error: database disk image is malformed
If you continue to see this error, try to disassociate your account
[*sigh*]
One Google (overlord) Groups thread from 2012 suggests using other services. e.g. EverNote, DropBox, and even (gasp!) Microsoft SkyDrive--Really?
(Lord) Google searches revealed that virtually anyone with some SQL skills might be able to recover from this. I am not a DBA. Having some very skilled DBA's at work has resulted in my leaving that skillset wanting....
Folks working in I.T. and/or with related skills can generally deal with and recover from interruptions/failures like these one way or another. (Incident response is something I enjoy--solving interesting & difficult puzzles in an almost House M.D. manner, which probably makes me some sort of Holmesian-Windows-barbarian, who knows). Considering some of the rubbish I have encountered with Google Drive, it is difficult to imagine folks with different skillsets responding to these interruptions. Either of my brothers would react vehemently, and perhaps rightfully so. Anyhow. Not cool, Lord Google.
There's a post on Twitter by Arul Dhesiaseelan (@aruld) which mentions Google Drive uses SQLite and includes a capture of an oft-encountered earlier Google Drive failure, (for which a search via...your favorite search engine will demonstrate others have also encountered this), "...PRIMARY KEY must be unique". Another one which, for most folks including myself, means starting from scratch and downloading everything again. (Where the hell is the frowny-face emoticon in Blogger?).
Now, in true geek (really hacker, but thanks to the media, that's usually used incorrectly--see cracker) fashion, we ought to be able to automate the backup any SQLite database that Google Drive uses and restore it from a backup, quickly & easily. This is especially important since Google Drive appears to be in some sort of immature, pre-release, beta state. (Where the hell is a good Slashdot article when you need one).
Hopefully in a future post: my humble attempts to automate backing up the Google (overlord) Drive SQLite DB in Windows.