Tag: how to rebuild raid 5 without losing data

HOW TO SETUP RAID 5

HOW TO SETUP RAID 5

Of all the RAID levels that consumers are likely to use on their home systems, RAID 5 is one of the more exotic choices. While RAID 0 and 1 are pretty straightforward, RAID 5 is a little more complex. As we discussed in earlier articles, RAID 0 stripes data across an array of drives, making reads and writes faster, while also sacrificing redundancy. RAID 1 does the opposite, writing identical data across every drive in the array, creating a redundancy in the event of failure. RAID 5 is somewhere in between. Like RAID 0, RAID 5 stripes data across an array of drives. However, one of the drives is reserved as the redundant copy of the piece of data. As each block of data is written, the stripes and redundant copy rotate places, so that no single drive fills up with redundant copies (this is called distributed parity). For this to work, RAID 5 requires a minimum of three drives.

When a drive in a RAID 5 array fails, the data can be located somewhere else in the array. If failure occurred on a drive that held a striped copy, the entirety of the data can be found on the drive that holds the parity copy. If the parity is missing, you still have a copy of the data striped across the other drives. On the flip side, if you lose more than one drive, you’ll lose the entire array because parity is distributed across all the drives.

In terms of performance, read operations will be similar to that of RAID 0, as the striped data can be read from several drives at one. Write operations, however, are more like RAID 1, since the parity data is written to only one drive.

Drive space is also pooled, but less so than in RAID 0. In RAID 5, it works a bit differently. Due to the way parity works, if you have three drives, the available space will be equal to a RAID 0 array with two drives. In our examples, we used three 120GB SSDs, which resulted in arrays with 240GB of space.

If you want install an OS on top of a RAID array, RAID 5 will work fairly well, so long as you’re not trying to use it atop an array of multi-terabyte spinning drives. RAID 5 offers more resiliency than RAID 0, as well as significant gains in read operations for loading programs and games.

By now you already know that it’s always best to use drives of identical make, model, and capacity when constructing a RAID array. Even if you’re forced to use different makes and models (as we were in our examples), you have to make sure that the drive capacities are identical. Mixing drives will at best result in an array that will perform as if each drive were the slowest one.

When connecting your drives for use in RAID, be sure to use the same interface for the drive. If two drives in your array are using SATA 6Gbps, use the same interface for every other drive you intend to add to the array.

It’s also a good idea to make sure all of the drives in your array are using the latest firmware. Firmware fixes can result in better speeds and fix potential bugs that can wreak havoc on your data.

CREATING ON WINDOWS

Creating a RAID 5 array in Windows is just as easy as creating RAID 0 and 1 arrays. It’s important to remember Microsoft uses the name “Storage Spaces” instead of RAID, but the function is pretty much the same. To start, hit Win + S and search for “Storage spaces” and launch the utility. Next, click “create a new pool and storage space.” You’ll be prompted for administrator access. Click yes to continue. You’ll see a window showing all of the unformatted disks that can be used. Select all the disks you want in the array and click “Create pool.” You’ll have to select at least three to be able to create a RAID 5 array. Next, give the pool a name and drive letter. The name will appear as the drive label. Select NTFS as the file system. For Resiliency type, select “Parity,” which is the equivalent to RAID 5? When you’re ready, click Create storage space to create the array. If you want to remove a RAID array for any reason, simply click Delete next to the storage space you want to remove. To remove the pool, remove all of the storage spaces in it first.

CREATING ON LINUX

Creating a software RAID 5 array in Linux takes only two terminal commands. In Linux, the program mdadm (we like to pronounce it “madam”) is what we’ll use to set up the array.

First things first, you need to get the RAID software. You’ll need to download and install mdadm from your software repository. It’s pretty common, and is included in most software repos. In Ubuntu, type the following command: sudo apt-get install mdadm

The command will install mdadm for you, along with a dependency called Postfix. Postfix is an SMTP service that sends emails. The reason it’s included is because if a drive fails or something else happens to your array, the system can alert you with an email. That’s great for IT administrators, but Postfix is a PITA to administer. In many cases, you can just set the program to use no configuration if you like. If you do take the time to set it up, it can give you early warning when drives fail.

Once mdadm is all set up, all you need to do is use the following command: sudo mdadm –create /dev/mdX –level=5 –raid-devices=[number of drives (3 or more)] [drive name] [drive name] [drive name] [etc]

The above command will vary based on the size of your array, and how you’d like to name it. RAID devices are generally named /dev/md X where X is the index of the array. Drive names can be any valid Linux device path, e.g., /dev/sda or /dev/disk/by-uuid/[UUID] .

If you’re not sure how Linux has identified your drives, you can use lsblk to identify them:

lsblk -o name,model,mountpoint,size

Once you create your array, you’ll have to wait while the drives synchronize, which may take several minutes.

You can also create RAID arrays in Linux using the GNOME disk utility. In Ubuntu, search for “Disks” and open the utility. On the left side of the window, click the checkbox above the list of drives. Then, select the drives you want to use to create an array and click Create RAID.

RAID DATA RECOVERY KENYA

RAID SYSTEMS
RAID stands for Redundant Array OF Independent Discs, which is a data storage technology that combines multiple physical disk drives into a single logical unit for the purpose of data redundancy or even both.
TYPES OF RAID SYSTEMS
1) Software RAID: RAID system that doesn’t require a dedicated hardware RAID controller. The RAID compatibility depends on the operating system. It applies whereby there is a single disk with two partitions; one to boot from and the other for data storage.
2) Hardware/Physical RAID: RAID controllers are required in this setup. This controllers support different levels of RAID and also specify the kinds of disks to be used in the array; SSD, SATA OR SAS.
LEVELS OF RAID
RAID 0: Consists of stripping, without mirroring of parity. The capacity of this level of RAID is the sum of all the disks in the set. Failure of one disk in the set causes loss of the entire RAID and the chances of data recovery are minimized.
RAID 1: Consists of data mirroring, without parity or stripping. Data is written identically to two or more drives therefore producing a mirrored set of drives in the set.
RAID 2: Consists of bit-level stripping whereby data is stripped in a way that each sequential bit is on a different drive.
RAID 3: Consists of byte-level stripping whereby data is stripped in a way that each sequential byte is on a different drive.
RAID 4: Consists of block-level stripping with dedicated parity whereby the read/write operations do not spread across all data drives.
RAID 5: Consists of block-level stripping with distributed parity whereby the parity info is distributed among all drives requiring all drives but one to be present to operate. Upon failure of a single drive, subsequent reads can be calculated from the distributed parity such that no data is lost.
RAID 6: Consists of block-level stripping with double distributed parity. This provides fault tolerance of up to two failed drives.
Nested (Hybrid) RAID: Many controllers allow RAID levels to be nested. The elements of RAID may be individual drives or arrays by themselves.

Note: Attempting to recover a RAID without an unexperienced data recovery specialist can put your critical data at further risk. When hardware malfunction is a component of the problem, permanent destruction of data can occur with failed recovery attempts.

With alot of experience on Raid recovery and through our advanced and up to date technology.East Africa Recovery Experts has the capacity and technical expertise required to solve complex, technically challenging RAID recoveries.

WHAT NOT TO DO WHEN YOUR RAID 5 SYSTEM FAILS

WHAT NOT TO DO WHEN YOUR RAID 5 SYSTEM FAILS
If you’re reading this then you probably know that there are different types of RAID systems and if not the following link will assist you to comprehend it better: With that issue out of the way,we will focus mainly on the RAID 5 system which is described as ‘fault resistant’, meaning that it can tolerate failure of a hard disk drive with the data on it still being available and readable. That being said the fault resistant part tolerates failure for only one hard drive and not more than that for RAID 5 whereas for RAID 6 the limit is increased to two drives. When it comes to RAID 5 there are three key points to note;
  1. The array must consist of three or more hard drive elements.
  2. The Reliable Availability of data stored can tolerate the failure of no more than one hard drive element.
  3. A rebuild procedure will always fail unless all components (controller and all hard drive elements) are present.
In the case where you cannot access and/or backup all the data stored in your RAID 5, do not attempt to rebuild it, contact the data recovery experts immediately. However, if you can back it up, do it first and fast to avoid total data loss. Any failed rebuild attempts reduce the chances of successful data recovery.
THE DON’TS LIST
  • Do not use RAID 5 as a backup solution; it is essentially a scheme to increase data availability.
  • Do not opt for rebuilding a RAID 5 as the first data recovery solution since you can ideally read all the data and ensure all the data contained on the subsystem is backed up before rebuilding.
  • Do not continue with any corrective actions once you realize that more than one of the hard drive elements is faulty. Seek professional assistance from the data recovery experts immediately.
  • Do not ever ignore any RAID 5 subsystem fault warning or any behavioral inconsistency. Once one drive fails, perform a backup immediately as you are running on a downgraded RAIDS whereby the fault tolerance is lost and if any other drive malfunctions your data may be lost.
  • Do not remove more than one drive simultaneously from its initially installed position as you may lose track of the sequencing of the drives. It is thus advisable to label the drives matching them with their slot while removing them.
  • Do not allow the controller to execute write operations on any known working drive as it will overwrite the stripping data needed for reconstruction.
  • Do not use CHKDSK or any other disk utility tools but if they should be used, be used with caution. The rate of success when using these tools is very low so, do not risk using them.
  • Do not shuffle the physical arrangement of the drives since the controller might not detect these changes.
  • Do not insist on trying out numerous ‘experiments’ in efforts to bring an inaccessible drive back online. These attempts might increase the damage to the RAID, reduce the chances of data recovery and maybe increase the cost of the data recovery itself. It is therefore recommended you reach out to the data recovery experts sooner rather than later.
  • Perform regular backups on the RAID just like any other data storage media to be safe since you never know when disaster may strike
Scroll to top