Whether it is necessary to do check consistency on reyd at initial setup/installation of the server?

Question

System administration

This is my first raid server, so don't be too hard on me.
R-Style Marshall came with 5 discs, 4 of which were combined in the 10th raid, and 5 were left under hot spare. Everything was done using the built-in utility. And in it VD0 has already been seen. We go further and after loading bios VD0 is no longer visible.
I decided to do check consistency in the same utility, but this check takes a huge amount of time.
Ripe questions
1. Do I need to do this at the initial creation of the raid?
2. Can this process be interrupted without consequences?
3. Maybe I just misconfigured something in bios?

Answer 1

It is worth doing not only during the initial installation of the server, but also from time to time (at least once a month).
In addition, reasonable RAID controllers have a Patrol Read setting that helps detect disk failures in advance (i.e., detect the unreadability of some block before someone needs the data in this sector), which increases safety: )
You can safely and without consequences interrupt, although the check will start again at a new start. This is a check, it (if everything is fine) does not write anything to disks. If problems are found during the check, the controller will probably replace the disk with a spare and start a rebuild, which, although it can be interrupted, is strongly not recommended.
What kind of RAID do you have? What does it call itself? Is it fake, or is the chip built into the board, or does the card cost a separate one? What size disks?