Recovering Data After a Logical Damage


Logical damage to a file system may prevent the host OS from mounting or using the file system.

  • can use native OS tools to repair
    • Windows chkdsk
    • Linux fsck
    • Mac Disk Utility
  • third party tools
    • Sleuth Kit
    • TestDisk

Logical Damage Recover Techniques

Consistency Checking

Consistency checking involves scanning a disk’s logical structure and ensuring that it is consistent with its specifications.

  • E.g., most file systems, a directory must have at least two entries, a dot entry that points to itself and a dot-dot entry that points to its parent
    • file system repair program reads each directory to ensure these exist and point to correct directories
    • if not, error is displayed and you can correct the problem
  • chkdsk and fsck work this way
  • 2 major problems
    1. consistency check can fail if the file system is highly damaged
    2. chkdsk utility might automatically delete data files if the files are out of place or unexplainable
      • does this to ensure the OS can run properly
  • same problem occurs on system restore disks that restore OS by removing the previous OS
    • avoid by installing the OS on a separate partition from the user data

Zero-Knowledge Analysis

  • file system is rebuilt from scratch using knowledge of an undamaged file system structure
    • scan the drive, noting all file system structures and possible file boundaries
    • then match the results to the specifications of a working file system
  • slower than consistency checking
  • but can be used to recover logical structures that are almost completely destroyed
  • does not repair the damaged file system
    • but allows you to extract the data to another storage device