I've looked at similar posts about software RAID, but this is a hardware RAID question, and googling did not turn up anything so I turn to you guys.
I understand that hardware RAID has a single-point of failure, i.e. the RAID controller, but I'm willing to take this risk.
Here's a little background on the situation at hand. I have a DELL Precision T7600 at work that I'm responsible for maintaining, which just lost a hard-drive, thankfully just the /home directory was on it, and has now been recovered. Now I've been tasked with making a RAID 1 of the OS drive so that our downtime is to a minimum.
I plugged in two brand spaking new WD Blacks in the system, and fired up a Manjaro Live USB after making the RAID 1 array using the integrated RAID controller. The distro picked up the RAID array as /dev/md126
, and immediately started a resync with its partner drive. Now this would make sense if one of the drives had just failed and a rebuild was necessary, but this is not the case. They are both new blank drives to reiterate. cat /proc/mdstat
gives me an estimate of ~200 min, which I'm not willing to spend without doing something about it.
So my question to you guys is why is this happening and how can I stop this useless time-wasteful process?
Now granted, I'm very new to RAID, so if I'm misunderstanding something feel free to correct my ignorance :).