Speaking about backups, we always mean that our hard drive may fail at any time, and this is completely justified. Unfortunately, the reliability of modern HDD leaves much to be desired, but not only they can be the culprits of data loss.
Naturally, I'm talking about RAID arrays and specifically about the failure of the RAID controller itself. What to do in this situation? In fact, everything is not as scary as it might seem at first glance. The configuration information of the RAID array is stored on the HDDs themselves, included in the array. Usually it is located in the first or last sectors of each disk, and the RAID controller firmware is written there when the array is formed. The configuration block is almost always duplicated on each disk of the array. With the exception of the disk number, the service data on all disks must be identical, and this can be used when restoring an array. Accordingly, all we need is to take a new controller and connect the disks in the same order in which they were connected to the dead controller. ')
But this is all theory, let's check - is it really so? I have 2 servers with integrated RAID controllers:
The results of the check in general did not surprise me personally: When replacing the DL380 controller with Adaptec, the controller saw the array and even tried to start the system from it (though we got kernel panic due to the lack of a driver for the controller in the already installed system), but in any case the data integrity was not compromised and the data is subject to recovery . The test was conducted on both RAID1 and RAID0. With LSI, everything turned out to be more simple and sad - the controller saw the disks, but did not see the array, the rebuild and other tricks did not give positive results. With x3650, the picture was the opposite. Since the M5110e is built on an LSI Logic chip, when replacing the controller with the 9260-8i, the array was seen and exactly the same as in the first case - we managed to get our data safe and sound, but with Adaptec the array refused to be recognized and no tricks helped us. From here we can conclude that the service information of the array is “tied” to a certain brand of manufacturers of RAID controllers. Personally, my recommendations are to try to avoid using built-in RAID controllers, since the selection of a controller, in the event of a failure of an existing one, will be a rather problematic task, which may not be crowned with success. Another thing, if you use an external controller of a particular manufacturer. Manufacturers of expensive controllers (LSI Logic, Adaptec, Intel, Promise) are quite conservative - the same models are produced for quite a long time, plus there is almost a 100% chance that your new model will perfectly see your array and will be fully functional ( In general, this is practically the way companies that provide data recovery services work, either use a similar controller, or use it as a “donor” to restore the old contact Roller, and as the third option - the transfer of non-volatile memory (CMOS) of the failed controller to a new one, in order to save data on the RAID array).