Tag: HOW TO RECOVER RAID

HOW TO RECOVER RAID – THINGS TO CONSIDER BEFORE RECOVERING RAID

HOW TO RECOVER RAID

RAID (redundant array of independent disks; originally redundant array of inexpensive disks) provides a way of storing the same data in different places (thus, redundantly) on multiple hard disks (though not all RAID levels provide redundancy).

By placing data on multiple disks, input/output (I/O) operations can overlap in a balanced way, improving performance. Since multiple disks increase the mean time between failures (MTBF), storing data redundantly also increases fault tolerance.

However this doesn’t mean that the RAID disks are fully fault tolerant, meaning that there is a possibility of the drives crashing. You may need to perform some data recovery incase this happens for you to get back your data

Before you can start any recovery on RAID, first consider the following factors:

  • If one of the member disks of RAID 5, RAID 6, RAID 5E or RAID 0+1 is physically damaged (produces unusual sounds, e.g. clicking or repeated spin-up and spin-down sounds), don’t use this disk for recovery.
  • If you cannot avoid using a physically damaged disk, say, for RAID 0 recovery, try to create the disk image file
  • If you have a hardware RAID, you should
  • Clearly label the member disks, the cables, and the controller ports, so that the original setup can be reassembled if need be.
  • Disconnect the array member disks from the RAID controller and then attach them as separate/standalone disks to a non-RAID controller. You need to access the disks separately to be able to reconstruct RAID parameters.
  • If you plan to recover data once the RAID parameters are restored, prepare a free disk space equal to the amount of data which you are going to recover.

Once these factors are put into consideration, you can now begin recovery.

If this doesn’t work for your case or you aren’t willing to take the risk recovering on your own, you can always contact the Data Recovery Experts for professional RAID data recovery.

HOW TO SETUP RAID 1

HOW TO SETUP RAID 1

RAID Level 1 can also be referred to as a mirrored array of hard drives. Mirroring is implemented when fault tolerance is desired. Fault tolerance is the ability of the data contained in the array to remain intact if one of the drives fails. In a mirrored array, all of the data is duplicated across 2 or more hard drives. The general idea: All of one’s important data would be stored on a mirrored array, and if one of the hard drives dies (which should be assumed, they die often), the data is still accessible / usable from the other drive. During a state of “failed redundancy”, the volume is now only one hard disk, and it would be smart to replace the failed disk promptly to rebuild the array. Common categories you may want to store on a redundant (same thing as “fault tolerant”) array: years of pictures, videos, documents, music, and hard-to-replace software install packages.

How to set up a Mirrored Array in Windows 7

  1. Install two hard drives. For my tests, I installed two WD 320 GB RE2 drives. Visit Buildegg’s Component section to see the best hard drives to buy.
  2. Boot up Windows, hit the start button, and in the search box type either “Create and” or “Disk man”, and click “Create and Formant Hard Disk Partitions”. This program is also accessible through Control Panel -> System and Security -> Administrative Tools -> Create and Formant Hard Disk Partitions.
  3. If these drives have never been used, it may ask you to initialize them, in which case you’ll most likely be using “MBR”.
  4. If the new disks do not say “Unallocated” in them, then delete their volumes by right-clicking on each disk’s volume and going to “Delete Volume…”
  5. Now let’s create the RAID: right-click on one of the disk (doesn’t matter which), and go to “New Mirror Volume…”
  6. A series of prompts will ask you about some details of your new mirrored volume (array), like which disks are to be included, size of the volume, drive letter assignment, and volume name. In my example, I chose Disk 1 and Disk 2 (Disk 0 being my original disk with the OS on it), the full size available (its default), drive letter M, quick format, and “WinMirror” as the volume name.

That’s it! Transfer all of your important files to your new “drive” and have a little peace of mind. Here’s an idea… map all of your Windows libraries (those default ones, Documents, Pictures, etc.) to your mirrored array, and you can upgrade hardware / format and reinstall windows all day long and not have to worry about your data.

 

What happens when a hard drive fails? How do you recover?

The whole point for setting up a mirrored array is anticipating the time when one of the hard drives fails and dies. There are two points in time where failure might happen: while the computer is on and you’re using it, or somewhere between the computer being shut off and turned back on. I simulated a drive failure while using the mirrored volume and I was able to continue working on files; accessing them and saving them. What is interesting is that Windows will not inform you that the array in an unhealthy state (at least, it never told me…); you won’t know until Windows is restarted. When you boot your system back up after one of the drives has failed, you will notice your mirrored volume missing (when you go to access something from it). Fear not, your data is still there, just open “Create and Format Disk Partitions” and manage the situation.

Inside Window’s disk manager you’ll find the still functioning disk, and it will be flagged with “Failed Redundancy”, of course meaning that the mirrored volume is no longer redundant because the other drive failed. In the most common situation I can imagine for most of us, you will need access to your files, and it may be a few days (or weeks) before you can replace the failed hard drive.

  1. First let’s gain access to our files. Right-click on the dynamic disks that is still functioning and go to “Remove Mirror…”
  2. Select and remove the missing (failed) disk. In my example, Disk 1 was the disk that failed, so I’m keeping Disk 2 and removing Disk 1 (which is labeled just as “Missing”).
  3. Now you’re left with a “Healthy” simple volume from which you can continue to use all of your data.
  4. Get a replacement hard drive so you can rebuild the mirror. NOTE: Most hard drives now have 3-5 year warranties, and all you have to do is go to the manufacturer’s website, fill out the RMA, and send in the defective drive.
  5. Fast forward to the time that you install a replacement hard drive (this may be an hour later, or weeks later).
  6. Open the Windows disk manager “Create and Format Disk Partitions” and make sure that the new drive is initialized and is unallocated.
  7. Right-click on the disk that survived (the one from the original mirror), and go to “Add Mirror…”. Follow the prompts and add the new drive.
  8. Now you have a new RAID 1, Mirrored Volume. You’ll notice that both drives in the array say “Resynching”, which is pretty much the one drive being copied to the other. This process may take the better part of a day if you have large drives, but that’s okay because it’s being done in the background — you don’t have to worry about it.

When raid fails, it’s important to consult a raid recovery expert before attempting to do it on your own, since this will increase your chances of successfully retaining your data.

HOW TO SETUP RAID 0

HOW TO SETUP RAID 0

RAID has several “levels” that use drives in different ways. Level 0 (RAID 0) spreads or “stripes” data between two or more drives. The problem with striping data across drives is that when things go wrong, they go really wrong: If a single hard drive in a RAID 0 array fails and cannot be recovered, the entire RAID array is lost. On the plus side, RAID 0 combines the drives into a single larger logical drive with a capacity that is the sum of all the drives in the array.

There are three ways to implement RAID: hardware, software, and Fake RAID. Hardware RAID is faster, but it’s also more expensive due to the need for specialized hardware. Software and Fake RAID use the CPU in lieu of a dedicated RAID chip.

Creating a software RAID array in operating system software is the easiest way to go. Windows 8 comes with everything you need to use software RAID, while the Linux package “mdadm” is listed in most standard repositories.

The problem with software RAID is that it only exists in the OS it was created in. Linux can’t see a RAID array created in Windows and vice versa. If you’re dual booting both Linux and Windows and need access to the array from both operating systems, use Fake RAID. Otherwise, stick to software.

In this article we’ll focus on Software RAID:

To ensure the best RAID performance, use identical drives with the same firmware. Mixing drive makes and models may work, but will result in faster drives being slowed down to match the slowest drive in the array. Don’t mix SSDs and mechanical drives in a RAID array; the SSD is faster on its own.

RAID 0 doesn’t protect you from drive failure, so use new drives whenever possible. When connecting your drives, make sure they’re all using the same SATA version as well.

Before a drive can be used in a RAID array, it must be clear of file systems and partitions. If you’re using old drives, make sure you get everything of value off of them first. You can remove any partitions with Disk Management on Windows or “gparted” on Linux. If you’re using Fake RAID, the motherboard’s RAID utility should warn you before it wipes partition tables and the file systems on them.

In your operating system, you’ll need to have elevated permissions to create a RAID array. For Windows, you’ll need to be an Administrator. In Linux, you’ll need either the root password or sudo access.

 

If you want to use Fake RAID, make sure your motherboard supports it. Be warned though: Installing an OS on top of a RAID 0 array can be really risky if your system data is critical.

CREATING RAID ON WINDOWS

Creating a software RAID 0 array on Windows is really easy. The thing is, Microsoft doesn’t call it RAID in Windows 8, opting for “storage spaces” and “storage pools” instead.

Hit Win + S and search for “storage spaces” and open the utility. Next, click Create a new pool and storage space. You’ll be prompted for administrator access. Click Yes to continue.

Windows 8’s built-in RAID software goes by the name “Storage Spaces.”

A window showing all the unformatted disks that can be used will pop up on the screen. Select all the disks you want in the array and click Create pool.

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 Simple (no resiliency. This is the equivalent to RAID0.When you’re ready, click Create storage space to create the array.

While a simple storage space technically only requires one hard disk, you need at least two for it to be a true RAID setup.

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.

When you’re done, you’ll be able to manage your storage spaces, check capacity, and monitor usage.

CREATING RAID ON LINUX

Creating a software RAID in Linux is faster than Windows because it only requires a couple of console commands. First, you need to download and install mdadm from your package manager. In Ubuntu, use aptitude to install the program:

sudo apt-get install mdadm

Once mdadm is installed, you can create your array by typing the following command as root or using sudo:

mdadm –create /dev/mdX –level=0 –raid-devices=[number of drives] [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/mdX where X is the index of the array. Drive names must be valid Linux device paths, e.g., /dev/sda or /dev/disk/by-uuid/[UUID] . In our example, we used the following:

mdadm –create /dev/md0 –level=0 –raid-devices=2 /dev/sda /dev/sdb

To take apart the RAID array, use the following commands:

umount -l /dev/mdX

mdadm –stop /dev/mdX

sudo mdadm –zero-superblock /dev/sdX

sudo mdadm –zero-superblock /dev/sdY

Contact Data Recovery Experts in case of failure

Scroll to top