Everything you need to know about data recovery with the Raise Data Recovery software
Thanks to Raise Data Recovery, restoring any file has become elementary even for novice users. This guide will give you an insight into different aspects of this process and teach you to easily cope with various data loss tasks, even if you’ve never worked with data recovery software before. Here you can also find some helpful advice from experts in this realm that will help you to avoid those gross mistakes which may turn the whole procedure into a data disaster.
A file system is the main mechanism responsible for the management of data on a storage medium. Not only it regulates the way data is allocated, stored and manipulated by the OS, but also defines the method of handling it in the process of file deletion or storage formatting. Therefore, in case of any mishaps and the need to restore the removed information, the chances for successful data recovery depend drastically on the behavior of the applied file system.
If you have deleted some files or the entire volume with your data was formatted due to an unfortunate mistake, you can easily estimate the possibility to set things right, if you know what type of file system actually performed this operation. Thus, let’s have a closer look at different file systems of Windows (NTFS, FAT/FAT32, exFAT, ReFS), macOS (HFS+, APFS) and Linux (Ext2, Ext3, Ext4, ReiserFS, XFS, JFS), their general structure and how exactly they get rid of the data during deletion and formatting.
General information about data recovery
The file systems of Windows
NTFS file system
Structure: the file system header (boot record), the Master File Table ($MFT), space for files:
The NTFS file system uses the Master File Table (MFT) for files coordination. Basically, the MFT contains the information about all files along with the folders that hold these files. This information, to be specific, includes the location, name, size of a file as well as the date/time of its creation and last modification.
If the file attributes are too big for one MFT cell, the file system will allocate another cell placed in the file for the list of file attributes.
Procedure: the file system does not delete and rather labels the file record in the MFT as unused and marks the file location in the MFT and Bitmap as released. The system also deletes the file entry from its directory.
Recovery: the information about the deleted file (name, size, location) remains in the MFT. If the MFT record remains unchanged and the data on the drive was not overwritten, the chances for file recovery are 100%. Yet, if this record was deleted, it is still possible to find the file by its content with the help of the RAW-recovery method (the analysis of the raw content of the drive for the presence of files of pre-defined types, bypassing the file system structure).
Procedure: the file system wipes the beginning of the MFT only. The MFT tail remains unchanged.
Recovery: the first 256 files lose their links to the MFT; thus, their recovery is only possible with the RAW-recovery method. Recovery chances for the files following these 256 files are up to 100%.
FAT/FAT32 file system
Structure: the file system header (2 headers more for FAT32), FAT tables and the data area.
The FAT file system applies the File Allocation Table containing an entry for each cluster on the drive and a link from this table to the file location on the disk. It also holds links to the cluster of the file start, file continuation and file end. The FAT file system does not apply defragmentation of fragmented files. As to its original design, files on FAT have 8 symbols for the file name and 3 symbols for the file extension. That is why the file system stores long file names separately utilizing the long file names (LFN) extension feature.
Procedure: the file system deletes all the information contained in the File Allocation Table including the links to the file continuation and end clusters. The data area itself is not wiped, though. The first symbol of the file name is deleted in its short form, and with FAT32, the part of information about the starting file cluster gets deleted.
Recovery: the file start can be found, but the information about the file continuation and the end needs to be assumed. For this reason, data recovery may be incomplete. Besides, the FAT file system doesn't defragment files making it difficult to retrieve fragmented files even with the RAW-recovery method. Another issue is that file names are limited in length and can even be stored detached on the storage. Recovery of long file names may give no effect.
exFAT file system
Structure: the file system header, the FAT table and the data area.
Like its predecessors, the exFAT file system applies the File Allocation Table to manage files. This table contains an entry for each cluster on the drive and makes a link from this table to the file location on the storage. It also holds links to the file start, file continuation and file end. This file system tries to avoid file fragmentation. The file system does not provide linking to the sub-directories of a file.
Procedure: the file system deletes all the information contained in the File Allocation Table including the links to the file continuation and end. The data area itself is not wiped, though.
Recovery: as links to the files’ continuation may be lost, the recovery result for files with the size of several blocks can be incomplete. The chances for successful recovery of a file in case of directory damage can be low as well. At the same time, recovery of files by their contents (the RAW-recovery method) may give highly positive results due to low files fragmentation.
ReFS file system
Structure: B+trees are used for all on-disk structures, including file data and metadata.
The structure of the ReFS file system is substantially different from the ones of its predecessors. The information within it is generally organized in a form of B+-trees that work similarly to databases. Such a tree is composed of the root, internal nodes and leaves. Each tree node has an ordered list of keys and pointers to the nodes of lower level or leaves. The most notable feature of ReFS is its usage of Copy-on-Write (CoW) – the original file system entries are never modified right away, they are just copied and written to a new location along with the necessary changes.
Procedure: the file system doesn’t edit a file’s metadata directly. It creates its copy, makes the required changes and links the data to the “updated entry” only after it is successfully written to the storage.
Recovery: the previous versions of file system objects still remain on the drive, making it possible to recover up to 100% of the data.
The file systems of macOS
HFS+ file system
Structure: the file system header; the file system journal; the Catalog File with the files containing information about other files (so-called hard-link files).
The HFS+ file system supports journaling. The file system journal keeps track of all file system modifications. The HFS+ journal is limited in its size, new information is added and written every time over the old journal records. In this way, the file system overwrites older information to release the journal for the data about newer file system modifications.
The HFS+ file system aims at files defragmentation. The file system thoroughly looks for a place to store a file, and literally glues file fragments together in the found one. Still, the remaining fragmented files can impose a problem to the recovery result.
HFS+ supports hard links stored as separate files inside a hidden HFS+ root directory, they serve to store information about a user file. Each hard-link file is bound to its user file.
Procedure: the file system deletes the hard link from the directory. Nevertheless, it still keeps this information in its journal records for some time.
Recovery: the program can refer to the file system journal to find an older file system state and return the lost hard link in its place. Data recovery chances will depend greatly on the time the system is used after the deletion of a file. Yet, if the journal record has been emptied, you can try RAW-recovery, which can give excellent results for non-fragmented files.
Procedure: the file system deletes the hard-link directory leaving the journal and on-disk data area intact.
Recovery: the program addresses the file system journal to recover everything that is recoverable from the journal or employs RAW-recovery (by file contents) to retrieve the lost files. Recovery chances may be low for fragmented files due to the deletion of hard-links.
APFS file system
Procedure: the file has a two-tree structure: one tree contains the data itself, while the other is the virtualization of the first one. During deletion the first tree is wiped, however, in some data loss cases, both trees get damaged. In such cases, file recovery is not possible.
Recovery: Previous versions of the first tree are analyzed with help of the second one and thus get recovered.
The file systems of Linux
Ext2 file system
Structure: the file system header; inodes; inode table.
The Ext2 file system uses inodes containing information about files. This information includes user and group ownership, access mode and extension. Some inodes include an inode table copy.
Inodes do not include file contents and file names, as they are stored in file directories and are not considered to be metadata according to the file system.
Procedure: Ext2 labels the file inode as free and updates the map of free blocks. The file name entry is unlinked from the directory record. The file name to node reference is wiped. The file will be deleted as soon as all inode references to this file are deleted.
Recovery: due to file descriptions remaining in the inode, the chances to retrieve the file are quite high. Nevertheless, file names stored in directories and unlinked from the file will be lost.
Procedure: Ext 2 wipes all file allocation groups and deletes file inodes.
Recovery: the program can apply the RAW-recovery method to find files by their contents. Recovery chances depend on file fragmentation: fragmented files are hard to retrieve.
Ext3/Ext4 file system
Structure: the file system header; inodes; inode table.
Ext3 and Ext4 structure
In addition to inodes implemented in Ext2, Ext3 and Ext4 file systems use file system journaling. The file system journal keeps track of all modifications made by the file system. Ext4 differs from the Ext3 file system by the references structure.
Procedure: The file system makes an entry to the journal and then wipes the file inode entry. The directory record is not deleted completely and rather the order for directory reading gets changed.
Recovery: the retrieval of deleted files even with the file name is possible due to the file system journal. Still, the recovery result depends on the time the file system remains in operation after file deletion.
Procedure: All allocation groups as well as file inodes and even the journal are wiped. The file system journal may still contain information about some of the recently created files.
Recovery: the retrieval of lost files is only possible with the RAW-recovery method to find lost files by their contents. Fragmented files have low recovery chances.
ReiserFS file system
Structure: the file system header, the S+-tree.
The file system uses the S+-tree which stores files metadata and has descriptors of all files and file fragments. In the process of writing new metadata into the tree, the new tree created for the new data replaces the old one. At the same time, its older copy remains on the disk. Thus, the file system can store lots of metadata copies. This technique is called Copy-on-Write (COW).
Procedure: The system updates its S+-tree to exclude the file and renews the map of free space.
Recovery: due to COW, it is possible to recover all files including their names. Moreover, you can also retrieve the previous version of such a file from an older S+-tree copy.
Procedure: The file system creates a new S+-tree over the existing one.
Recovery: COW helps to retrieve the previous file system state enabling complete data recovery. However, the chances for complete recovery of lost files decrease, if the file system partition was full. In such case, the system would overwrite the old data with new one.
XFS file system
Structure: complex tree structures, inodes, bitmaps
The XFS file system uses inodes to store files metadata and journaling to keep track of system modifications. Only metadata is journaled by this file system. Each inode has a header and a bitmap. XFS stores inodes in a special tree in a specific place on the disk. The system also has a bitmap for free storage blocks.
Procedure: the inode responsible for this file is excluded from the tree; its place is overwritten with new information.
Recovery: XFS keeps the file metadata still leaving much information and making the recovery of lost files possible. The chances to recover a deleted file even with the correct file name are quite high.
Procedure: root directories of the file system are overwritten.
Recovery: chances to recover files which were not located at the beginning of the storage are high, in contrast to those files, which were stored close to the disk start.
JFS file system
Structure: the superblock, the B+-tree, the journal, inode file sets
JFS file system employs the B+-tree structure for storing data, journaling for file system modifications and inodes for describing files. The system is also capable of storing several file systems on one partition with links to the same file. File names can be saved in the Unicode and UTF8 encodings.
Procedure: JFS updates the counter of the object uses and releases its inode in the inodes map. The directory is rebuilt to reflect the changes.
Recovery: The file inode remains on the storage increasing the chances of files recovery up to almost 100%. The recovery chances are low for file names only.
Procedure: JFS writes a new tree. It is small at the beginning and gets extended with further file system use.
Recovery: the chances to recover lost files after formatting are quite high due to the small size of a new B+-tree. Moreover, the internal inodes numbering increases chances for easy files recovery after formatting.
This step-by-step video tutorial will walk you through the functionality of Raise Data Recovery and teach you to restore files with several clicks of a mouse. The instruction can be applied to almost any device: from the memory card of your camera to the internal drive of your PC.
Data recovery after storage format has never been so easy. Learn how you can use Raise Data Recovery to get your lost files back from a formatted USB flash drive and other digital media with no sweat. Just carry out a few simple steps and then save the data to another location.
If you wish to use Raise Data Recovery without limitations, you might want to obtain a license for the software. This short instruction will guide you through the process of purchasing and activation of licenses by following the prompts provided in the interface of the application.
What’s more? Explore the variety of our software solutions!
Raise Data Recovery is a beginners-friendly application designed to save you costs and efforts in rescuing lost files. If you have higher requirements to your data recovery tools, check out more advanced products of SysDev Laboratories: