@travisdh1 said in Blind swap / automatic rebuild on linux:
@Pete-S said in Blind swap / automatic rebuild on linux:
I often see that the argument for using hardware raid is to be able to initiate an automatic rebuild by just swapping a faulty drive for a new one.
A lot of people assume that software raid can't do that. But that's incorrect.
Software raid on linux (as in md
managed by mdadm
) can do the exact the same thing.
It's under policy and partition policy in mdadm.conf
. You'll find on the man mdadm.conf
page.
The spare-same-slot
option would be the one that works the same way as hardware controllers usually do.
I haven't used it myself since I prefer to initiate the rebuild myself. But I wonder if you guys have used it?
I don't think blind swap is about automatic rebuild, that's a given no matter what software/hardware RAID is running. It's more about seeing the light is red instead of green on drive 6, so you know that is the one to replace.
The only example of not having that available, that I can think of, is https://www.45drives.com/
I don't know man.
A typical SMB would have no monitoring and any server would be stuck in a closet somewhere. Nobody would notice any red lights until several months later or until something breaks and then they'd have no clue what to do about it, wouldn't know who to call and wouldn't have any idea if the server even has warranty (it never has). A spare drive wouldn't be available unless it was an old discarded drive left on the shelf from the last time something was replaced.
If it was someone who knows what they're doing then a red light or not doesn't make much of a difference. Any drive that gets kicked out of an array doesn't have any activity. So it's always the one that doesn't blink.
BTW, Supermicro has better toploading servers than 45drives. You still have drive activity LEDs on those and you can hotplug any drive while it's running.
Storage server porn:
Youtube Video