July 13th, 2019, 13:50
July 13th, 2019, 17:20
rubenatch wrote:So, I'm looking for utilities (it doesn't matter if they run under DOS, Windows or Linux, or if they have GUI or CLI) that can perform those tasks:
- A tool that can check every compressed file in a directory looking for corrupted data (i.e.: check all zip files under a folder and all subfolders).
July 13th, 2019, 18:36
My laptop HDD has developed some bad blocks. It has the standard stuff (a hidden NTFS partition and a system NTFS partition), and it has too much 7z and zip files to take care of. The computer still boots, but it has obviously some DLLs corrupted.
- A tool that can map a physical block to a file, so I can know what files have been corrupted. It should support disks with more than one partition, and FAT/NTFS/ext filesystems. I know that there is a tool that can get a ddrescue log file and find which file can be corrupted, but it does need an image previously created and I don't have enough disk space to do so.
- A tool that can create a file that occupies a physical block, so I can be sure that important data won't be written there (until I get a new disk).
July 13th, 2019, 20:23
July 14th, 2019, 2:44
fzabkar wrote:for /r C:\Recovery_Root_Dir %f in (*.zip) do "c:\program files\7-zip\7z" t %f >> C:\zip_tests.txt
maximus wrote:First I am going to state the obvious. Backup all your important data now, before the drive completely fails.
maximus wrote:You do not need an image or clone (although it is highly recommended to image or clone your drive before it fails). You can run ddrescue with a destination of /dev/null, that will create a log file without creating an actual data backup. Then you can use the ddrutility programs with the ddrescue log and choosing the failing disk as the input.
maximus wrote:I would like to add that you should get a replacement disk as soon as possible, and use the computer as little as possible (not at all would be best), including not doing any of the above mentioned actions. The more you mess with the disk, the sooner it will further fail and leave you with no data.
July 14th, 2019, 21:33
July 15th, 2019, 0:33
rubenatch wrote:fzabkar wrote:for /r C:\Recovery_Root_Dir %f in (*.zip) do "c:\program files\7-zip\7z" t %f >> C:\zip_tests.txt
This will test the current directory, not subfolders.
FOR /R [[drive:]path] %variable IN (set) DO command [command-parameters]
Walks the directory tree rooted at [drive:]path, executing the FOR statement in each directory of the tree. If no directory specification is specified after /R, then the current directory is assumed. If set is only a single period (.) character, then it will enumerate the directory tree.
July 17th, 2019, 19:43
Powered by phpBB © phpBB Group.