So I'm currently building an mdadm RAID5 array attached to my home server. The hardware is an Odroid N2 SBC with a Mediasonic Probox 4 bay enclosure attached. The array is currently rebuilding and has been for days but moving steadily. I'm using armbian stretch with the legacy 4.9.180 kernel.
Last night, I was using the system (but not the drives) and was running a checksum on a file on a different USB drive. There is currently an unsolved bug in the USB drivers for the N2 that is exacerbated by high I/O activity. The N2 subsequently died around 11:40pm last night.
The N2 came back almost immediately and I didn't even notice until morning. However, the mdadm array rebuild was paused at 75%. I resumed the rebuild and it's progressing happily, but I want to be sure that I didn't do lasting harm to the new array.
Is there any mdadm utility that I can use to confirm there are no errors in the parity data? There is no filesystem on the array so I don't think I can use fsck in this case