Greetings to all, dear readers of the blog site. I think many of you have come across such an interesting expression on the Internet at least once - "RAID array". What it means and why an ordinary user may need it, that's what we will talk about today. It is a well-known fact that it is the slowest component in a PC, and is inferior to the processor and.

To compensate for the "innate" slowness where it is out of place at all (we are talking primarily about servers and high-performance PCs), they came up with a so-called disk array RAID - a kind of "bundle" of several identical hard drives working in parallel. This solution allows you to significantly increase the speed of work, coupled with reliability.

First of all, a RAID array allows you to provide high fault tolerance for hard drives(HDD) of your computer, by combining several hard drives into one logical element. Accordingly, to implement this technology, you will need at least two hard disk ... In addition, RAID is just convenient, because all the information that previously had to be copied to backup sources (, external hard drives), now you can leave "as is", because the risk of its complete loss is minimal and tends to zero, but not always, more on that below.

RAID translates something like this: a secure set of inexpensive disks. The name goes back to the times when large hard drives were very expensive and it was cheaper to assemble one common array of smaller disks. The essence has not changed since then, in general, like the name, only now you can make a giant storage from several HDDs of a large volume, or make it so that one disk will duplicate another. You can also combine both functions, thereby gaining the benefits of one and the other.

All these arrays are under their own numbers, most likely you have heard about them - raid 0, 1 ... 10, that is, arrays of different levels.

Varieties of RAID

Speed ​​Raid 0

Raid 0 has nothing to do with reliability, because it only increases speed. You need at least 2 hard drives, and in this case the data will be "cut" and written to both disks at the same time. That is, the full volume of these disks will be available to you, and theoretically this means that you get 2 times more high speed read / write.

But let's imagine that one of these drives is broken - in this case, the loss of ALL your data is inevitable. In other words, you still have to make regular backups in order to be able to restore information later. It usually uses 2 to 4 discs.

Raid 1 or "mirror"

Reliability does not decrease here. You get the disk space and performance of only one hard drive, but you have double the reliability. One disk breaks - the information will be saved on the other.

An array of RAID 1 does not affect the speed, but the volume - here you have only half of the total disk space, which, by the way, in raid 1 can be 2, 4, etc., that is, an even number. In general, the main feature of the first level raid is reliability.

Raid 10

It combines all the best from the previous types. I propose to analyze how it works on the example of four HDDs. So, the information is written in parallel on two disks, and this data is duplicated on two other disks.

As a result, the access speed is doubled, but also the volume of only two of the four disks in the array. But if any two disks break down, there will be no data loss.

Raid 5

This type of array is very similar to RAID 1 in its purpose, only now you need at least 3 disks, one of them will store the information necessary for recovery. For example, if such an array contains 6 HDDs, then only 5 of them will be used to record information.

Due to the fact that data is written to several hard drives at once, the read speed is high, which is perfect for storing a large amount of data there. But, without an expensive raid controller, the speed will not be very high. God forbid one of the disks breaks - restoring information will take a lot of time.

Raid 6

This array can survive the failure of two hard drives at once. This means that to create such an array, you will need at least four disks, despite the fact that the write speed will be even lower than that of RAID 5.

Please note that without a productive raid controller, such an array (6) is unlikely to be assembled. If you have only 4 hard drives at your disposal, it is better to build a RAID 1.

How to create and configure a RAID array

RAID controller

A raid array can be done by connecting several HDDs to a computer motherboard that supports this technology. This means that such a motherboard has an integrated controller, which, as a rule, is built into. But, the controller can also be external, which is connected via PCI or PCI-E connector. Each controller usually has its own configuration software.

The raid can be organized both at the hardware level and at the software level, the latter option being the most common among home PCs. Users do not like the controller built into the motherboard for its poor reliability. In addition, in case of damage to the motherboard, it will be very problematic to recover data. At the software level, it plays the role of a controller, in which case it will be possible to safely transfer your raid array to another PC.

Hardware

How to make a RAID array? To do this, you need:

1. Get it somewhere with raid support (in the case of hardware RAID);
2. Buy at least two identical hard drives. It is better that they are identical not only in characteristics, but also of the same manufacturer and model, and connect to the mat. board with one.
3. Transfer all data from your HDD to other media, otherwise they will be destroyed in the process of creating a raid.
4. Further, in the BIOS, you will need to enable RAID support, how to do this in the case of your computer - I cannot tell, due to the fact that everyone's BIOS is different. Usually this parameter is named something like this: "SATA Configuration or Configure SATA as RAID".
5. Then restart your PC and a table with more detailed raid settings should appear. You may have to press the "ctrl + i" key combination during the "POST" procedure for this table to appear. For those who have an external controller, most likely it will be necessary to press "F2". In the table itself, click "Create Massive" and select the required array level.

After creating a raid array in BIOS, you need to go to "disk management" in OS -10 and format the unallocated area - this is our array.

Program

There is no need to enable or disable anything in the BIOS to create a software RAID. You actually don't even need raid support motherboard... As mentioned above, the technology is implemented at the expense of the PC's central processor and the means of Windows itself. Yeah, you don't even need to install any third-party software. True, in this way, you can create only RAID of the first type, which is a "mirror".

Right-click on "my computer" - item "management" - "disk management". Then we click on any of the hard drives intended for the raid (disk1 or disk2) and select "Create mirrored volume". In the next window, select a disk that will be a mirror of another hard drive, then assign a letter and format the resulting partition.

In this utility, mirrored volumes are highlighted in one color (red) and are designated by one letter. In this case, files are copied to both volumes, once to one volume, and the same file is copied to the second volume. It is noteworthy that in the window "my computer" our array will be displayed as one section, the second section is, as it were, hidden, so as not to "annoy" the eyes, because there are the same duplicate files.

If any hard drive fails, the error "Failed redundancy" will appear, while on the second section everything will remain intact.

Let's summarize

RAID 5 is needed for a limited range of tasks, when much more (than 4 disks) number of HDDs are collected in huge arrays. For most users, Raid 1 is the best option. For example, if you have four disks with a capacity of 3 terabytes each - in RAID 1, then 6 terabytes of capacity are available. RAID 5 in this case will give more space, however, the access speed will drop dramatically. RAID 6 will give you the same 6 terabytes, but even lower access speed, and it will also require an expensive controller from you.

Let's add more RAID disks and you will see how everything changes. For example, let's take eight disks of the same capacity (3 terabytes). In RAID 1, only 12 terabytes of space will be available for writing, half of the volume will be closed! RAID 5 in this example will give 21 terabytes of disk space + it will be possible to get data from any one damaged hard drive. RAID 6 will give 18 terabytes and data can be retrieved from any two drives.

In general, RAID is not a cheap thing, but personally I would like to have at my disposal a RAID of the first level of 3 terabyte disks. There are even more sophisticated methods, such as RAID 6 0, or "raid from raid arrays", but this makes sense when a large number HDD, at least 8, 16 or 30 - you must agree, this is already far beyond the scope of ordinary "household" use and is in demand for the most part in servers.

Something like this, leave comments, add the site to bookmarks (for convenience), there will be many more interesting and useful things, and see you soon on the blog pages!

R-Studio program a universal tool for extracting information from problem media. It is able to build virtual arrays or sets (Virtual Volume Sets) from physical disks, partitions on them or image files. Arrays of levels 0, 1, 3, 5 are emulated. Latest Versions programs are able to recreate even little-used configurations - these are RAID 4 and RAID 6. Today, in a step-by-step example, we will see how using the program R Studio, restore a RAID array, but first, let's take a closer look at the functionality of this software product.

R Studio.

Data recovery software R Studio designed to restore deleted files that were lost for a variety of reasons (all causes of information loss can be divided into two types: logical and physical, but more on that in another post). Supports file systems FAT12 / 16/32, NTFS, NTFS5, Ext2FS (Linux), which is noteworthy for the NTFS file system, the recovery of encrypted files is supported, and for the NTFS 5.0 version, recovery and alternative data supported by this version of the file system are provided.
STEP 1
Open the previously created images of the disks included in the array using the Drive | Open Image File. As a result, the mounted images will be added to the disk tree marked with Image (Image).
(If you work directly with hard drives, step 1 is skipped.)

STEP 2
Create a virtual array of the same type as the one being restored. Select one of the Create menu items:

Create Virtual Volume Set - analogous to a software array;
Create Virtual Mirror - RAID 1;
Create Virtual Stripe Set - RAID 0;
Create Virtual RAID 5

A new virtual array will be added to the disk tree, and when you click on it, a panel of this virtual set will appear in the right part of the window. The panel consists of two tabs:

Properties - these are the general properties of the entire array;
Parents (literally, Parents) - this tab shows the disks included in the array, and sets the parameters for combining them into a set. The Parents tabs are open by default, and most of the work is done there.

STEP 3
Drag and drop mouse disks or open images from the tree to the Parents tab of the virtual set pane.

STEP 4
Diagram at the bottom of the program tab R Studio displays the order of interleaving of blocks in a virtual array. To the right of the chart, set the block size (the Block size drop-down list), the interleaving order (the Blocks order drop-down list), and the number of rows when interleaved (Rows count). As a rule, the default values ​​(Default) are suitable for the parameters of most arrays - manufacturers of common controllers follow roughly the same rules. To change the striping order, drag and drop the disks in the desired order directly in the list of disks on the Parents tab. The same can be done on an alternation diagram.

STEP 5
In the drive tree, right-click on the virtual set icon and in context menu select the Scan command. The Scan dialog box shown in the figure below will open.

STEP 6
Further scanning and saving the found files is no different from recovering data from a single media.

The main source of problems is the incorrectly specified disk striping order, less often - the incorrect block size. In both cases, some files can be found and extracted, since their signatures are found, and then the program collects the file in accordance with the specified order of stripes.

Small files, the length of which does not exceed the block size, will be recovered perfectly correctly anyway. If the file occupies more than one block, the initial fragment will also be correct. The subsequent contents of the file will be composed of blocks, not all of which actually belong to it. As a result, these files will be "broken" and cannot be opened.

If all the extracted files are clearly damaged and cannot be opened, the program R Studio or in any other program, it is advisable to change the order of blocks or disks in the virtual array, or choose a different block size. It may take several recovery attempts with different parameters to find the block size and interleaving order.

For speed, the scanning process can be interrupted almost at the very beginning - and by selecting it, it is enough to restore only a few files and make sure that the correct combination of parameters has been found. Usually, the search takes from 2 to 10 attempts - creating an array, most users agree with the block size that the controller offers by default (64 or 128 KB), and there are rarely more than three disks.

Program R-Studio once again confirms its reputation. Its tools allow you to perform a full cycle of work: from taking an image to restoring the logical structure or extracting files.

There are many hard drive models on the market today from renowned manufacturers such as Hitachi, Maxtor, Seagate and Western Digital. For the home or office, one drive is usually sufficient. But for corporate networks, clusters or file servers, it is often necessary to use multiple hard drives. This raises a problem - serious RAID controllers are quite expensive.

Many motherboards have built-in RAID controllers, but not all of them are suitable for organizing a file server. Most controllers only support the simplest modes 0 and 1, as well as a combination of two RAID 0 + 1 modes (striping and mirroring). While RAID 0 offers more capacity and superior performance, it also increases the chances of data loss. The more drives in a RAID 0 array, the more likely data loss is due to a single hard drive failure. A good compromise can be considered a RAID 0 + 1 array, where two RAID 0 arrays are duplicated, but the total volume of hard drives should be halved.
If you need high capacity and reliability, then good decision there will be a RAID 5 array, which distributes data across all disks, and also adds parity information one by one to each disk. The total capacity of such an array is equal to the sum of the volumes of all drives minus the volume of one hard disk. But such a solution is not as easy to implement as it seems. Computing parity information, as well as real-time data recovery in the event of a drive failure, consumes a lot of CPU computing resources. To solve this problem, you can buy quite expensive RAID controller with a built-in XOR block, or purchase a cheap model that uses the CPU to calculate XOR operations.
But why do we ignore the software implementation of RAID 5? If your budget is limited, you can deploy a software RAID 5 array in addition to using a simple RAID controller without an XOR block. Windows Server can fit all existing drives into a RAID 5 array, so you don't even need a RAID controller. However, if you need simple file services, then you don't even need to spend money on expensive Windows Server - with some modifications, you can build a powerful RAID array under Windows XP. Just remember that Windows XP supports a maximum of ten network clients connected at the same time.

Deploying a RAID 5 Array under Windows XP

For Windows XP to be able to work with RAID 5, you need to use a hex editor (the same Ultra Edit or Hacker "s View), and also take a CD with Windows XP. First, copy some files to a temporary folder:
C: \ windows \ system32 \ drivers \ dmboot.sys
C: \ windows \ system32 \ dmconfig.dll
C: \ windows \ system32 \ Dmadmin.exe
Then open these files with a hex editor:
Then the files in the Windows System32 directory should be replaced with our modified versions. But a simple rewriting will not work here, since Windows will restore itself original versions files.
If your disk is formatted for FAT32, then just boot into DOS and overwrite the files manually. However, since FAT32 does not provide any kind of file protection, we strongly discourage using this file system.
In an NTFS environment, you will have to boot from the Windows XP CD and launch the recovery console. This can be done by pressing "R" in the first menu. But before that, the modified files should be copied to a floppy disk.
After booting the Recovery Console, go to the Windows directory:
C:
cd \ windows
Now copy all files one by one with the following commands. All files are located in two different directories.
copy a: \ dmboot.sys system32 \ drivers
copy a: \ dmboot.sys system32 \ dllcache
copy a: \ dmconfig.dll system32
copy a: \ dmconfig.dll system32 \ dllcache
copy a: \ dmadmin.exe system32
copy a: \ dmadmin.exe system32 \ dllcache

How to create a RAID 5 array

Now reboot your system. In Windows, launch the management console (right-click on the My Computer icon, then Manage) and select Disk Management. All hard disks that will be used in the RAID 5 array should be converted to dynamic here. To do this, right-click on desired disk and select "Convert to dynamic disk". Well, then you can create new volume.


After modifying the files as shown above, Windows XP will be able to support software RAID 5.


For our test array, we used four Western Digital WD740 Raptor drives.


The following options in windows ...


... do not differ from those specified when creating a regular volume.
Once Windows has finished creating the volume, you can work with the new RAID 5 array under Windows just like a normal hard drive.

Worst case: if the drive fails?

Even the most powerful backup system isn't worth a pittance if it doesn't work. Therefore, in addition to the usual tests, we decided to simulate a drive failure by pulling out the SATA cable.


This screenshot shows what the disk manager looks like a few seconds after the hard disk is removed from the array. Then we plugged the cable back in. For security reasons, Windows will not automatically include the hard drive in the array. All other hard drives in the array have been marked as "failed redundancy" - no redundancy works.

Select "repair volume", after which the process of restoring the array will begin.


Of course, we need one free drive.


The recovery process has begun!

Migrating Windows RAID to Other Systems

We installed a RAID 5 array on Asus board P5DGC-V equipped with the ICH6 southbridge.
Many administrators fear not only drive failure, but controller failure as well. Usually, there is never an identical or at least compatible controller model at hand, so the array is difficult or impossible to run on another controller. The main problem will be that the RAID formats of different RAID controllers are usually not compatible with each other.
Of course, we wanted to check if there was such a problem with Windows RAID arrays: is it possible to migrate an existing RAID array by simply plugging the hard drives into another computer?
The main test machine was powered by an Asus P5GDC-V. It is based on the Intel 915G chipset with ICH6 Southbridge, which provides four native Serial ATA ports. We connected four Western Digital WD740 Raptor hard drives to them.
When we chose the second system to migrate the RAID array, we specifically found a SATA controller that is incompatible with ICH6. The AOpen AX4SPE MAX II board is based on the 865P chipset with the good old ICH5 south bridge. On the one hand, it is not AHCI compliant. On the other hand, this bridge only provides two ports, so we connected the two remaining drives to the Silicon Image Sil3114 controller, also installed on the AOpen board.
Admittedly, we did not expect an easy transfer of the array. But all we had to do was just plug the SATA cables into free ports on the board, and it worked right away. We didn't have to think about the order of connecting the drives to the ports, nor about the type of controller to which the drives were connected. The actuators can be freely connected to the ICH5 and Sil3114 controllers.


Moving a four-drive RAID 5 array to another system was very easy. There was nothing to configure, and the SATA ports were freely selectable.

Test configuration

Intel Processors (Socket 775)
FSB 800 MHz (Dual Channel DDR)	Intel processor Pentium 4 520 (2.8 GHz)
Motherboard
Socket LGA-775	ASUS P5GDC-V Deluxe Intel 915P Chipset BIOS 1002
Memory
DDR SDRAM	2x 512 Crucial Ballistic Delays: CL 2.5-3-3-7
General hardware
Graphic card	NVidia GeForce 6 series GPU: nVidia GeForce 6800 GT Memory: 256MB GDDR3 SDRAM
Hard Drive I - OS	Hitachi HDS722525VLSA80 250 GB, 8 MB cache, 7200 rpm
Hard Drive II - RAID	Western Digital WD 740 Raptor 74 GB, 8 MB cache, 10,000 rpm
DVD / CD-ROM	MSI MS-8216 16x DVD
Software
Graphic nVidia card	nVidia Detonator 61.77
Driver Intel chipset	Installation Utility 6.0.1.1002
DirectX	9.0c
OS	Windows XP Professional 5.10.2600, Service Pack 1
Tests and measurements
Office Applications	ZD WinBench 99 - Business Disk Winmark 2.0 c "t h2benchw
High-end applications	ZD WinBench 99 - High-End Disk Winmark 2.0
performance measurement	c "t h2benchw
I / O performance	Intel I / O meter 2003.05.10

Conclusion

To be honest, the result of installing a RAID 5 array under Windows XP is much better than we expected. Moving the management of a RAID array from a controller to an operating system, of course, cannot be called a performance solution, but here we get high level flexibility and interoperability, so rarely found in the field of data warehousing. Any Windows system XP is technically capable of supporting RAID arrays, of course, if you connect the required number of hard drives. And here it doesn't matter at all which SATA controllers you use. And to enable RAID 5 support under Windows XP, only three files need to be changed.
The simulation of the failure of one hard disk went without any problems, and even not too much can cope with the process of rebuilding the array. experienced users... It also takes about the same amount of time to rebuild as hardware RAID. It should not be mentioned that access to the functions of creating and modifying a RAID array is available only to users with certain rights, that is, the Windows security subsystem will stand in the way of unwary users and attackers.
Another advantage of a RAID 5 array under Windows XP is the great price. Aside from buying hard drives, all you need to do is provide the required number of SATA ports on your motherboard or controller. Well, it is quite possible to refuse to buy an expensive RAID controller.
Finally, let's move on to the disadvantages of such a solution. Software RAID 5 under Windows is not as fast as hardware solutions. However, file servers do not always need maximum performance. If you need to set up a server for infrequent access with a small amount of traffic, then Windows RAID will be sufficient. But be careful. Once you create a RAID array, you cannot migrate it to a hardware RAID controller. To do this, you have to rearrange the entire array.
...

There are situations when HDD fails (due to voltage problems, physical wear and tear, and so on) and it turns out that over the years the information accumulated is irretrievably lost (you can contact data recovery specialists, but as a rule it costs a lot of money and not the fact that the information will be obtained restore) and therefore, in order to save myself from such fears, I decided to set up a RAID1 mirroring system, which I will talk about in this video tutorial.

In general, I will devote 2 lessons to this topic, in this we will consider setting up RAID1 via BIOS, and in the next setting RAID1 programmatically Windows tools 7.

And so, what is RAID in general, the abbreviation itself stands for an independent array of inexpensive disks and in general there are quite a few types of RAIDs, these are RAID 0,1,5,10, but in this video we will analyze the most common RAID1 or mirrored RAID.

What is the essence of RAID1, let's say you have 2 identical hard disks, they are combined into RAID1, and the operating system sees these two disks as one physical and when you write any information to this disc it is duplicated on both disks, it turns out, as it were, a mirror image of information on both disks.

And in case of failure of one of them, all information is saved on the second disk and by replacing the failed disk with a similar one, the mirror backup system is restored.

I would like to say right away that setting through the BIOS is more reliable, but also more complicated and, perhaps, suitable for setting up on backup servers, at home it will be enough to set up the mirrors programmatically.

Well, now let's move on to the direct configuration of RAID1 through the BIOS, since it will not work to record this video from the screen, the setting does not go through Windows, then some screenshots will be of poor quality, but the point is not in the quality but in the usefulness of this information.

First, we go into the BIOS, for me it looks like this. V different models motherboards the setting may differ, but the principle is the same. We need to find the SATA configuration menu or IDE devices, I have this menu located in additionally \ SATA configuration \ Here in the SATA mode menu, select RAID, save the changes and exit the BIOS.

The computer restarts and at startup, before trying to boot the operating system, a message appears, I have this Press Ctrl + I to enter the RAID configuration utility, run the utility.

This window displays the following information

The presence of a RAID - since I have not created it yet, therefore the inscription is not defined here, i.e. No RAID

The serial number of the device, I have 2 of them

Model hard disk(it is advisable to use discs of the same manufacturer and the same brand so that they are absolutely identical)

The volume of each disk (the volume must be the same on both disks, otherwise it will not work to create a mirrored RAID)

And the status, since the RAID has not yet been created, the status is not in the RAID array

In addition to the status table, there is also a menu that consists of the following items:

Creating a RAID array

Removing a RAID array

Resetting all disks to a non-RAID state (if there are several RAIDs, then all RAIDs will be deleted)

At this stage, I did not use the following other points, so I cannot say anything about them.

We enter the name of the RAID, I will call it Mirror, which means a mirror, then in the device manager it is under this name that this disk drive will be displayed.

Now in the information about RAID arrays there is a RAID named Mirror, RAID1 type, with a volume of 931.5 GB, the status is normal and it can be bootable.

If you want an operating system on it, then install the OS on it. Moreover, when I experimented, my operating system was on another disk, and after creating a mirrored RAID array, the operating system stopped loading. Those. dropped out when loading blue screen, therefore, if you have an OS on another disk, you should first create a RAID, and then install the OS so that all drivers are installed correctly!

After starting the OS, go to the device manager \ Disk drives and see the Mirror storage device there, i.e. this is the mirrored RAID1 disk.

After disconnecting one of the disks, the following message with the RAID status Degraded (Degraded, i.e. one of the disks is missing in the RAID) appears at boot, but regardless of this, the operating system continues to boot.

I have now booted from a faulty RAID, you can see this with special program that comes with the motherboard drivers.

Now I reconnect the disk and the RAID state goes into Rebuild (reconstruction, in this state, data from the mirrored disk is copied to the connected disk in order to restore the RAID functionality, depending on the disk size, this process can take a long time)

We load the OS and again look through the program what happens to the RAID, everything is OK, the RAID is restored, and with installed disk reconstruction is in progress. After finishing this process, everything will work as before.

Again, before experimenting with RAID, it's best to save important information to another medium, just in case!

As for the advantages and disadvantages of this system:

The cost of 1 GB is 2 times higher (since you will need to purchase 2 disks to store the same amount of information)

High fault tolerance (although, there are such failures in which all the hardware burns out, but there is no way to protect yourself, except perhaps to store a copy of the documents on a dedicated server) But, again, if the system is implemented on the backup server, then if it all burns out, then, in any case, copies of documents should remain on workstations, well, unless all the computers in office J have burned out

Hardware RAID (software RAID is created using a program, and no program is protected from glitches, therefore RAID through BIOS is more reliable)

Hello. Today I got my hands on two brand new hard drives, I thought for a long time what can be done with them to help my readers. On reflection, I finally decided that it was better than a story about RAID 1, created by myself operating system, I can hardly write anything. So what is RAID 1?

RAID 1 is an array of two disk media, information on which is duplicated on both disks. That is, you have two disks that are full copies each other. Why is this done? First of all, to increase the reliability of information storage. Since the probability of failure of both disks at the same time is small, in the event of failure of one disk, you will always have a copy of all information on the second. You can store any information on a RAID 1 array just like on a regular hard disk, which allows you not to worry about an important project that you have been working on for a very long time.

Today we will look at how a RAID array is created using Windows itself when using two empty disks (I confidently declare that this instruction works on Windows 7, 8 and 8.1). If you are interested in creating a RAID array using an already full disk, then you need one on this topic.

And, in fact, instructions for your acquaintance:

1) First, install hard drives v system unit and start your computer.

2) Open “Control Panel → System and Security → Administrative Tools → Computer Management → Storage Devices → Disk Management”. When you turn it on for the first time, the utility will inform you about the installation of new disk devices and offer to choose a partition for them. If you have a disk of 2.2TB or more, choose GPT, if less, then choose MBR.

3) At the bottom of the window, find one of our new hard drives and right-click on it. We select "Create mirrored volume":

4) The Image Wizard will open. Click further.

5) On this page you need to add a disk that will duplicate the previously selected disk. Therefore, select the disk in the left part and press the "Add" button:



Click further.

6) Select the letter that will be used to designate the new volume. I chose M for Mirror. Click on next.

7) We set file system, cluster size and volume name. I also recommend checking the box next to "Quick Format", let it do everything at once. And again further.

8) We check what we have done, if everything is correct, we press "Finish".