| View previous topic :: View next topic |
| Author |
Message |
LIsLinuxIsSogood
Veteran
Joined: 13 Feb 2016
Posts: 1179
|
 Posted: Sun Jun 03, 2018 5:12 am Post subject: Method for document checking |
 |
|
| I have an old hard drive that became corrupt/damages but was able to take some action and recover some of the files (there are now literally hundreds without names and many of them). Since I know that many are not actually recoverable, but others that are would be scattered throughout the directory (folder) therefore does anyone know of a way to check which of these (mostly docs, xls, and other microsoft like rtf) to maybe sort the list by actual readability of the files so that I don't have to go through it one at a time, which could take a year or more to do if I go little by little like I have been doing.[/bug] |
|
| Back to top |
|
 |
LIsLinuxIsSogood
Veteran
Joined: 13 Feb 2016
Posts: 1179
|
| Posted: Sun Jun 03, 2018 6:48 am Post subject: |
|
|
| Actually in case that there isn't any suggestions I was also wondering since I know that executing or opening a corrupt file may be not a good idea, but what about writing, reading or copying from one disk to the other (in order keep files until later when I can try to recover them). Is there danger in doing that? |
|
| Back to top |
|
|
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5934
|
| Posted: Sun Jun 03, 2018 7:03 am Post subject: |
|
|
| LIsLinuxIsSogood wrote: | | but what about writing, reading or copying from one disk to the other (in order keep files until later when I can try to recover them). Is there danger in doing that? |
you mean like a backup? 
no that should be fine unless the backup has data corruption issues as well.
_________________
| Neddyseagoon wrote: | | The problem with leaving is that you can only do it once and it reduces your influence. |
banned from #gentoo since sept 2017 |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21622
|
| Posted: Sun Jun 03, 2018 4:27 pm Post subject: |
|
|
| If a disk is in sufficiently bad shape, it may have a measurable and low number of read passes / hours of life left. Copy everything you might want to save onto a good drive, then work from there. At worst, some files may fail to copy if the disk is too far gone. If your problem is purely data corruption and the hardware is in good order, there is a chance that working from a corrupt filesystem could confuse the kernel into crashing. Generally, that should not happen, but be aware and try not to leave any unsaved work open until you are done working with the corrupt filesystem. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54232
Location: 56N 3W
|
| Posted: Sun Jun 03, 2018 5:29 pm Post subject: |
|
|
LIsLinuxIsSogood,
| Quote: | | ... there are now literally hundreds without names ... |
that sounds like you used fsck to 'help' before you used ddrescue to make a drive image.
The contents of lost+found are fragments, identified by inode number. The fragments may not even be complete files.
fsck makes the filesystem metadata self consistent. It says nothing about user dat that may be on the filesystem.
Even files that you can navigate to via the directory structure may be damaged.
You can use a tool like file to look at the start of files and guess what they are.
Unfortunately, that only tells about the starts. The middles and ends can be corrupt or missing. The same goes for the fragments in lost+found.
You are trying to put Humpty Dumpty together again and don't even know if you have all the pieces.
Your next step is a drive image with ddrescue since you want to prevent whatever you have now from deteriorating further.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Other Things Gentoo
