hard drive failure

[monky]

i recently lost a hard drive, but have a backed up copy of my everything.db file from before the crash. how do i get everything to read that database and allow me to export a file list?

i tried 'everything -old.db -read-only' but it refuses to allow me to search anything (i'm guessing because the drive doesn't exist anymore?).

i'm on 1.3.3.657 (x64).

thanks

edit: nevermind, the database was created with a different version of everything and wasn't compatible. got it working now. my bad

[redhab]

monky, I'm in the same situation. What command line did you use to load the old db file?

[therube]

I would backup the .db first ...

Everything has a -read-only switch.
So something like:

Code: Select all

everything.exe  -read-only
or
everything.exe  -read-only  -db  save_me_please.db

Once you have opened the .db, you can export its contents to an .efu (csv file).

[xgenei]

This command line string (augmented by paths) does create a new back up DB file - but the export command is only producing a 53 byte file. It only contains a header of the db file name. Any with a better idea?

[dennisqwilson]

I have the same problem -- a dead data drive and a backed-up copy of my "everything.db" file. How can I export the contents of that file to a text list?

[void]

Please make a backup of your Everything.db, Everything likes to recreate this file if it thinks it is out of date.

If the Everything.db was created with Everything 1.2 you will need:
http://www.voidtools.com/Everything1.2.1.389b.zip

Extract Everything1.2.1.389b.zip to an empty folder and copy your Everything.db file into the same location.
This version opens the Everything.db in read only mode, from there you can export to a txt file from File -> Export.

If the Everything.db was created with Everything 1.3:
Make a backup of your Everything.db
as therube said, run Everything with the following command line:

Code: Select all

Everything.exe -read-only

From the File menu, click Export.

[dennisqwilson]

Thank you!

[coober]

I have a similar problem. Hard drive crash and that NTFS volume is no longer on my system and I want to retrieve the list of files from the last everything scan.

I have a backup of the everything.db. I'm not sure which exact version of everything.exe I was running. The db header looks like the one created by the current 1.3x version.

Running current 1.3x everything.exe -read-only -db everything.db displays 0 results.
Running 1.3x without the params scans and creates a new db.
Running Everything1.2.1.389b.exe scans and creates a new db.

Is there anything I'm missing? Is there any alternate way to export the list?

[void]

You will need a hex editor.

Could you please send the first 8 bytes of the Everything.db file.

The Everything.db may be compressed.
If the database starts with BZ, please rename the database to Everything.db.bz2, extract the Everything.db file and read the first 8 bytes.

With the first 8 bytes I can determine the version.
What is the size of the Everything.db?

Hope I can help.

[coober]

Much appreciated.

Size: 14,154,880
First 8 bytes: ESDb<bh:05><bh:00><bh:07><bh:01>

[void]

Please try Everything 1.3.2.645b - Everything 1.3.2.658b.

These versions of Everything should be able to open your Everything.db.
Like Everything 1.3.4.686, please use the following command line options to open your Everything.db in read only mode:

Code: Select all

Everything-1.3.2.658b.exe -read-only -db <Everything.db>

[coober]

Thank you.
I tried Everything 1.3.2.645b, Everything 1.3.2.658b, and then 644b and 643b.
All returned 0 results.

I used sysinternals procmon.exe to monitor the activity.

645b opened the db, read all of it in 64K chunks, and then created an errorlog.txt:
10/9/2014 9:35 PM: Everything 1.3.2.645b: .\src\db.c(7956): _db_load_local(): if (67046387 != 70547791): buffer underflow.

658b 32 bit opened the db but returned no error and displayed 0 results.
658b 64 bit shows no signs of opening the db. It returned no error and displayed 0 results.

644b and 643b opened the db, read one 64K chunk, and then closed the file and displayed 0 results with no error:

Thank you again for your help. Is there any value in my trying any other versions/methods?

[void]

645b opened the db, read all of it in 64K chunks, and then created an errorlog.txt:
10/9/2014 9:35 PM: Everything 1.3.2.645b: .\src\db.c(7956): _db_load_local(): if (67046387 != 70547791): buffer underflow.

To report this error, Everything 645b is opening the everything.db ok, but it appears the db is corrupt (missing file name data).
If you would like, send the everything.db to david@voidtools.com and I will attempt to recover your list of files.

[coober]

I give up. It's time for me to sign up for some offline backup.

Thank you for your incredibly generous offer to try to extract the list and for all your help!

[void]

Everything-1.3.2.645-coober.zip is a modified Everything 1.3.2.645b that will allow buffer underflows.

You should be able to get most of your file names back with this.
Same as before, from a command prompt, run:

Code: Select all

Everything.exe -read-only -db <everything.db>

From the File menu, click Export...

[coober]

I gave that build a try, no error was generated, but Everything displayed zero results. My file must have more problems. I'd hate to take any more of your time with my small problem so I'm going to consider it lost for good. Thanks again, you are too kind.

[Leopold]

I'm in same situation as topic starter. One of hdd's on my home pc is died and I've a Everything.db file (about 21 MiB in size with header ESDb<05><00><07><01>). I tried to open Everything.db with command Everything.exe -read-only, but I've got 0 objects message.

On my work pc I've tried to test if Everything.exe -read-only command is working and I find out that it's still gave me 0 objects. Also I figured that if I use Everything.exe -admin -read-only command I'll be able to successfully load work pc's database file on my work pc. Then I tried to repeat it at home pc, but it gave me the same 0 objects. I've even tried to copy my Everything.db file from home pc to work pc, but it's still shows 0 objects.

[added after some time, while forum was readonly]

I'm have Everything v1.3.3.658 x86 running on Win7 Ultimate SP1 x64, I've also tried newer versions but they shows me a message in debug log about unsupported db.

Here is part of debug log, gathered when I run Everything.exe -read-only -debug -admin on my home pc trying to open needed db

Code: Select all

db_load
new thread (0)
_db_filesystem_add 0: 0, 00608c20
_db_filesystem_add 1: 0, 00608d20
_db_filesystem_add 2: 0, 00608ba0
open volume \\?\Volume{a3ed2cc6-9449-11e3-90bd-806e6f6e6963}
opened 508 0.000438
open volume \\?\Volume{a3ed2cc7-9449-11e3-90bd-806e6f6e6963}
opened -1 0.000373
CreateFileW(): GetLastError(): 2: Failed to open volume \\?\Volume{a3ed2cc7-9449
-11e3-90bd-806e6f6e6963}
usn journal state changed
loaded db in 0.003590 seconds

Seems Everything checks if volume id exists on the pc and it refuse to show db content if one of volumes not found.

Do you have any suggestions about how to list db content without presence of one of volume?

[void]

Please see db2efu for an Everything database recovery tool.

Please let me know if you have any troubles.

[Leopold]

db2efu worked like a charm.
Now I'm able to see everything.

There is output in case you need it for some purpose:

Code: Select all

c:\>db2efu.exe Everything.db List.efu
Everything.db opened for reading...
List.efu created for writing...
Magic ESDb
Version 1.7.5
flags 00000000
number of folders: 149682
number of files: 1183025
decode size: 42074517 (ignored)
filesystem count: 3
Loading Hierarchy...
NTFS folder count: 149682
Loading folders...
Loading files...
Conversion complete!