Recover Crashed RAID 5EE: Controller or Disk Failure Guide

Learn how to recover crashed RAID 5EE after controller failure (Adaptec ASR-6805T) or multiple disk failures with our essential guide. If you’ve encountered data loss due to a crashed RAID 5EE array, it’s crucial to understand the steps for successful data recovery in such critical situations. In this comprehensive tutorial, we’ll walk you through step-by-step instructions and expert techniques to help you retrieve data from a crashed RAID 5EE array after controller failure or disk failures. From identifying the root causes of the crash to implementing recovery strategies, you’ll learn everything you need to know to ensure successful data retrieval. Don’t let RAID 5EE failures lead to permanent data loss—watch our guide and reclaim your valuable data today.

Recover Crashed RAID 5EE: Controller or Disk Failure Guide

Compared with conventional storage devices, RAID arrays offer much more disk space for all your files and folders. Also, they guarantee data integrity and safe extraction of any materials you store there, even if one of the drives within the storage system fails. Despite the high reliability of such systems, though, important information sometimes gets damaged, lost or inaccessible.

Go to view
🏆 How to Recover a Crashed RAID 5EE After Controller Failure or Multiple Disk Failure 🏆

🏆 How to Recover a Crashed RAID 5EE After Controller Failure or Multiple Disk Failure 🏆

Losing important data is something that you can never predict. Though RAID 5 is considered a very reliable solution to store digital materials, still it doesn’t give you a 100% guaranteed protection against possible data loss. At any time, one or several disks may fail, and this is also true about the controller, or other hardware involved in the process. This situation renders the whole RAID system inoperable, and you will have to find a way to get your data back.

How to create a RAID 5EE system based on an Adaptec ASR-6805T controller

First of all, let’s explore the process of creating a RAID system, the important aspects to be considered when building it, and the settings required to make data recovery possible. Our RAID will consist of six disks working with the controller, Adaptec ASR-6805T.

A high-performance hardware controller Adaptec ASR-6805T designed for storage systems.

In order to access the controller’s BIOS after hardware initialization, you should press the key shortcut Ctrl+A while the computer is booting.

The command to be run  Press & lt;CTRL><A>

In the menu, select Array Configuration Utility.

In the settings menu for Adaptec ASR-6805T select Array Configuration Utility.

In the new window, you need to initialize the disks in order to tell the controller which of them will be used in the array. Find and open the line Initialize Drives.

Select “Initialize Drives” to initialize the disks.

Use the Space or Insert key to select each of the disks, and then press Enter.

Select all drives in the initialization table.

As a result, you will see a notification warning you that information on all initialized disks will be erased. Enter Yes to confirm your choice and launch the initialization process.

The system warns you of initialization consequences.

After initialization, we can start creating the array. In the main menu, open Create Array.

In the settings menu for Adaptec ASR-6805T, select “Create Array”.

In the next page, look at the left panel in the window Select drives to create Array to select the drives which will make up the RAID, and then press Enter.

Select all storage devices.

Now it’s time to configure the array properties. The new page will contain important properties that should be memorized. You will need this information later when you try to recover data from the disks.

Specify the array type, its name and size, block size, caching settings and other properties. In our case, we performed all operations on a RAID 5EE based on an Adaptec hardware controller and including six drives 300 Gb each.

Selecting properties in the page “Array Properties”.

Now the RAID system has been created. It will take some more time to finish the building process, and soon you will be able to boot your computer and use the disk array to store your data safely.

The menu page with the settings.

In the next part of the article, we will find out how to replace a faulty drive and rebuild a damaged array.

How to replace a failed drive and rebuild a RAID array

At this stage, we are going to simulate a scenario when one of the drives fails. RAID 5 is designed in such a way that the whole array remains operable if one of the storage devices breaks down.

After a drive fails, the array becomes degraded, and while the computer is booting, you will see a message like this.

A system warning.

Before you take any action, it’s better to back up all important data. This is crucial because anything may happen during the array rebuilding process (one more disk may fail, the process may freeze, or there might be a hardware issue) and cause a total loss of data. Later on, we will explore what should be done in case of system errors or failures, but now we are about to look into the process of rebuilding the disk array.

Connect a new disk to the controller, turn on the computer, and open controller properties. To access then while the computer is booting, press the key shortcut Ctrl+A. In the window that opens, select Array Configuration Utility. Your first step is to initialize the new disk, so open Initialize Drives.

Select the initialization option in the main menu.

In the next page, select the new disk by pressing the Insert or Space key and hit Enter.

Add a new drive in the left panel.

The operating system will show you a warning saying that one or several drives belong to an array and initialization will destroy the data. Make sure that you selected a new empty drive and type Yes.

The system warning of a possible data loss.

Then type Yes again to agree that the data in this storage device will be erased.

The warning of data to be erased.

Now the initialized drive should be added to the RAID. Open the menu line Manage Arrays, press the key shortcut CTRL+S and access the management page.

The menu page with the settings.

Use the Space or Insert key to select the new drive, and then hit Enter.

In the left panel, select your drive.

A new system notification appears. In the special field, type Yes to confirm.

The system asking for your confirmation to perform action.

After this sequence of steps, the rebuild process should start.

From now on, you can boot the server in normal mode and continue your work. A complete RAID rebuild is quite a long process and it depends on a number of things – the performance of your controller/drives, current controller load/disk load, etc. The time required to rebuild the array will be reduced, and the whole process will go faster if you don’t start using the array right after a new drive was added. If possible, let the controller finish the rebuilding process and only then start using the array the way you prefer.

By now, we have explored the situation when only one drive within the array failed. But what shall we do if several drives no longer work properly, or the controller is dead, or the operating system won’t boot after you added a new drive to the array?

This is when it’s better to use Hetman RAID Recovery.

Recover data from damaged RAID arrays inaccessible from a computer.

This tool lets you recover data from crashed RAID systems or disks that were used in such array; it reads all the information about the controller, the motherboard, or the software used to create a disk array. Also, this product can rebuild the crashed RAID and it lets you copy all important information from there.

How to recover data from a RAID array with a dead controller

If the controller fails, you won’t be able to access the information on the disks. When they are connected directly to the computer, the operating system will ask you to format the disks for further use.

In this case, you will either need a controller of the same model (which doesn’t guarantee the success of this operation, though) or a software tool capable of uniting these disks into a RAID system, displaying and restoring your data.

Connect the hard disks to a properly working Windows computer. In such drives, the file system can’t be identified, so the operating system will label them as RAW.

The primary partition is healthy but can’t be identified by the operating system.

The Disk Management tool will suggest initializing the RAW drives, and the Windows Explorer will ask if you want to format them.

Windows Explorer suggests formatting the drive.

If you value the data on that drive, don’t agree to either option, as it may result in complete data loss.

The system warns you that this location is not available.

Download, install and run Hetman RAID Recovery. A lot of various service data is written to the storage devices included into a RAID system. For example, what disks make up the array, in what order they are connected to the controller, the RAID type, block size and the procedure of writing blocks, number of disk groups, and the data on the array size.

Having collected all the available information from the system and connected disks, the utility displays the automatically built arrays immediately, as soon as the program starts. In most cases, the program manages to restore RAID on the fly and suggests you to analyze the identified partitions and save any available data.

The main window displays general information.

Open the Drive Manager tab, and find the line RAID Arrays to select your storage system from the list. Right-click on it and choose Open.

The line “Open” in the context menu.

Try Fast scan first: if the disk structure is not damaged, this scan type will suffice.

Choose the scan type.

If the Fast scan doesn’t help to find the data, then go for Full analysis.

The mode to look for all available information.

When it’s over, the program will display the results in the right side of the window.

All detected files are displayed for review and further action.

The program has built the RAID without effort and it can now display all the information still available on the disks. In this case, you don’t have to buy a controller of the same model – and as we know, even when you have it, there’s no guarantee you can build the RAID again without losing its information.

SATA Expansion Card

If your motherboard doesn’t have enough SATA ports to connect all the drives that used to be included into your RAID system, you can solve the problem by using a SATA expansion card. There is a wide choice of them, and you can get a card from any specialized store or buy it online – for example, on AliExpress.

The Device Manager app is recognizing the SATA expansion card.

To have all the disks connected to the computer, we used an expansion card Marvell mv92xx (PCE6SAT-M01) with six ports.

Marvell mv92xx (PCE6SAT-M01).

Initially, the computer was only able to detect 4 disks, and to make it “see” all the disks connected to the expansion card, we had to install corresponding drivers.

Driver information in the properties window for Marvell mv92xx.

Expansion cards may have 2, 4, 6 or 8 ports.

Various expansion card models.

With a card like this, you can connect from two to eight drives. Supposing you have a few vacant ports on the motherboard and a good power supply unit, you can easily connect a dozen storage devices.

Recovering data in a case of dead controller and one hard disk

After that, we simulated a situation, when both the controller and one of the hard disks failed. This RAID type should remain absolutely operable when only one drive is down. However, there is no way to access the information without additional software tools once the controller breaks down too. Still, our program coped with the task. We have connected the remaining five disks directly to the motherboard.

Hetman RAID Recovery detects the RAID type automatically, and displays all the information available about this array.

The main window of the data recovery tool.

To display the contents of the disk, right-click on it and select Open.

The line “Open” in the context menu.

For starters, select Fast scan.

Choose the scan type.

The program has found all the files that have been written to the array.

To recover them, select the ones you need, and then click Recovery,

Select the necessary files, then start the recovery process.

specify the path to another healthy disk, and click Recovery again to save the data.

Give the path to save the files.

The program will recover all the selected files and put them into the specified folder.

Recovering data in a case of dead controller and two hard disks

Then we simulated a situation with a dead controller and two disks that failed at the same time. This scenario should render this RAID type completely inoperable. Replacing the failed hard disks is not going to change anything. The information will be lost anyway.

Now we have four disks connected to the motherboard directly. If you don’t know which disks are still healthy, and which are not, connect all the drives. In our test scenario, we just disconnected two disks out of six.

To restore information from the remaining disks in this array we start Hetman RAID Recovery. In our case, the utility identified the RAID type automatically.

The recovery tool identifies the storage system type.

If your array is not shown on the list of storage devices, use RAID Constructor.

The integrated tool for identifying connected devices.

To rebuild the array in manual mode, you will need all the information you have on this damaged RAID system. Previously, we have described the way of obtaining the required information and suggested memorizing all the important properties.

The information you need in the page “Array Properties”.
Select a suitable option in the Constructor.

If the program has detected the array type automatically, view the information in the next window to make sure that all the properties were detected correctly.

Check the properties.

This is the factor that determines how much data can be recovered. If one of the properties is incorrect, change it. After that, click Add and start scanning the disk array.

In this situation, the program has found the data, but a part of the information is damaged.

Damaged and healthy files in the program’s window.

If the files you need are damaged or not found, run Full analysis. Then the program will be able to find more data which is still intact.

Select the files to be restored, and then click Recovery.

Select files for recovery.

Specify a directory for saving the recovered data and click Recovery.

The path for saving and other important options.

The selected files will be recovered. You will find them in the directory you have specified.


In this tutorial, we have presented two ways of recovering lost information from damaged arrays. Even when two drives and the hardware controller were down, we managed to recover a part of the data. It’s not always that successful, though, because losing two hard disks makes a RAID 5EE system completely inoperable and all the information is lost.

Also, it is always important to back up your files regularly. This is the option that almost always secures your information against all kinds of nasty things you may experience when it is lost. No matter what kind of error or failure occurs, you will be able to rebuild your RAID system and restore it from a backup copy.

Vladimir Artiukh

Author: , Technical Writer

Vladimir Artiukh is a technical writer for Hetman Software, as well as the voice and face of their English-speaking YouTube channel, Hetman Software: Data Recovery for Windows. He handles tutorials, how-tos, and detailed reviews on how the company’s tools work with all kinds of data storage devices.

Oleg Afonin

Editor: , Technical Writer

Oleg Afonin is an expert in mobile forensics, data recovery and computer systems. He often attends large data security conferences, and writes several blogs for such resources as, Elcomsoft and Habr. In addition to his online activities, Oleg’s articles are also published in professional magazines. Also, Oleg Afonin is the co-author of a well-known book, Mobile Forensics - Advanced Investigative Strategies.

Recommended For You

Hello! This is AI-based Hetman Software virtual assistant, and it will answer any of your questions right away.
Start Chat