RAID 0 Data Recovery

RAID 0 Data Recovery Service

0800 008 6638

Emergency Rebuild, Recovery.

Contact Button

RAID 0 Data Recovery.

Data Recovery from a RAID 0 system is conducted in very much the same manner as a single disk recovery. The RAID 0 element only adds to the complexity of the recovery as we have potentially two hard disk drives requiring laboratory attention.  Once the faults with the hard disks have been overcome we can then concentrate on the reconstruction process and data extraction.

Rebuilding RAID 0 Systems.

RAID 0 is a Hard Disk Drive configuration without redundancy. If any hard disk drive in a RAID 0 array fails, the whole array fails and the system will not be able to read or write files.

Data from individual disks can be recovered but the data is useless unless it can be reconstructed properly.

Every RAID 0 implementation has a unique set of configuration parameters and reconstruction following corruption is a complex task.

Datlabs technicians specialize in rebuilding RAID 0 disk arrays using a variety of tools, test gear and laboratory facilities to accomplish the task. Datlabs have also developed propriety applications to specifically facilitate the reconstruction of RAID 0 arrays.

RAID 0 Advantages.

A RAID 0 hard drive system configuration is a convenient way of increasing the total available system data storage capacity whilst increasing data transfer speeds. Users most likely to benefit from a RAID 0 configured system will include the likes of Graphic Designers, PC Gamers and Video Editors and anyone looking to maximize the speed at which data can be read/written.

RAID 0 Disadvantages.

RAID 0 configured systems offer no contingency against the failure of one or other of the hard disk drives. i.e. There is no redundancy built into the system. This means that if there is a fault with a hard drive in the array then access to all the stored data will be lost.

The inherent vulnerability of a RAID 0 is due to the way data is stored across all array member hard disk drives. Data in a RAID 0 is written simultaneously to the system array member disks using a method commonly termed striping. The actual size of the stripe is configured via the RAID system controller application and is usually circa 64Kb – 512Kb (this is the portion of each file that will be written to a disk before moving onto the next) As a consequence, unless the file in question is below the configured stripe size then it is guaranteed to be stored on multiple disks.

RAID 0 Systems. Explained.

RAID 0 systems typically have two physical hard drives managed as a single logical volume. This volume will have the combined capacity of both hard drives and a greatly increased data input/output speed. Data being transferred simultaneously via two channels through to the controller and system processor.

RAID 0 Configuration Explained.

Merely as a help to understanding how a RAID O operates and why special assistance is needed when a disk drive fails it is worthwhile exploring how data is stored on RAID 0 configured disks.

Raid 0 arrays are built for performance. Instead of reading/writing specific files to one specific hard disk, RAID 0 arrays read/write files to multiple hard disks in parallel. The process of fracturing files and writing them to multiple hard disks is called “striping.”

As a demonstration of striping :- A text file of four characters “ABCD” and a RAID 0 of two disks (stripe width of two) with a stripe/block size of four bits (equal to one half of a character).

The text in the file can be shown as:-

raid 0 table4

The file is stored as follows:

The first block of four bits (first half of letter A) is written to disk 1 and the second block of four bits (second half of letter A) is written to disk 2. This pattern will repeat until all bits are written.

raid 0 table 3

In this example half of the file is on disk 1 and the other half is on disk 2. Notice that the file is not split down the middle (down the middle would have “AB” on disk 1 and “CD” on disk 2). Half of each character is stored on each disk.

Now consider what happens when a disk fails and the data from each disk is recovered.

raid 0 table1

Disk 1 by itself contains the text “DD” and disk 2 contains a special character called “Device Control 2” and the number 4. Obviously, the data from each disk is garbage unless it’s reconstructed in the proper order.

The array must be reconstructed properly by assembling alternating blocks from disk 1 and disk 2 like this:

raid 0 table

RAID 5 Recovery Service

RAID 1 Recovery Service

RAID 0 Recovery Service