Hard drive crashed, how can I retrieve that hard drive's filenames from everything?

[cal]

Got a malfunction message from Windows, the hard drive then disconnected. When I try connecting again, it isn't recognized anymore.

Hard drive letter G, is there any way to retrieve the file names of that hard drive?

Any way to archive each day's drive file names?

[void]

Please backup your Everything.db as soon as possible.

Please try the database recovery tool to recover filenames.

Good luck.



edit:
For Everything 1.5, open your Everything.db from File -> Open File List...

[cal]

The database recovery tool didn't do anything or failed, I selected everything-1.5a.db and it exported to a EFU file, the exported file is blank 0 kb.

I am on 1.5.0.1383a and the db file is 87mb last modified today 8/13

There is a Everything-1.5a.backup.db file last modified 8/11 that is 106mb

[therube]

Ditto, 0 bytes.

Code: Select all

xxx.db opened for reading...
out.efu created for writing...
Magic ESDb
Version 1.7.49
Unknown DB version 01070031

Looks like the .db is newer then the (recovery) tool.


I suppose an updated db2efu tool will be forthcoming.

[therube]

Make (multiple ) copies of any .db that you have.
Work on copies. Work safely.

You can try to open your .db in a different instance of Everything.
You want to do this in -read-only mode.

Exit any running Everything's.

create a directory, say C:\RECOV\
copy Everything.exe & Everything.db into C:\RECOV\
from within C:\RECOV\, run:

Everything.exe -read-only -db Everything.db

That should load your Everything.db in a -read-only mode.
From there, you should be able to search, Export...

(Changes will not be effected [to the .db].

Note: other changes may make physical changes to files on disk.

Say your .db has c:/out/readme.txt,
& say your current HDD also has a c:/out/readme.txt file.
If you were to "delete" said file, through this instance of Everything, it would physically delete the file from your drive.
Likewise, if you "renamed" the file in Everything from readme.txt to readme999.txt, it would physically do that on your disk (though would not be reflected on the Everything end, in its' .db - cause you're in a -read-only mode.)


Work on backups & be careful as to what you're doing.

[cal]

Unfortunately, the backup db did not have the content of the crashed drive on it, I'll know what to do next time though. I shook the hard drive really hard and it was recognized for a few minutes, I exported the file names which had the video id of each video so I was able to plug them back into a downloader to redownload all the lost videos.