Defragging the drives should speed up the process somewhat (4-7%), but most of the time involved as you say is restripping, and the adapter verifying the media as it is writing.
While you at it, run disk clean-up, delete all files in all tmp directories (profiles/windows temp folder), use search to find all tmp files and delete, then defrag.
One thing you should institute is a scheduled consistency check, weekly or bi-monthly if possible, I also schedule patrol reads to turn on and off, in off hours, every weekend, if off hours permit.
Example of CC command line to place in a scheduled task to check the C: drive
"C:\Program Files\Dell\SysMgt\ArrayManager\amcli.exe" /c1/e0/v
For a D: drive
"C:\Program
Files\Dell\SysMgt\Array Manager\amcli.exe" /c2/e0/v
I use lsilogic's downloaded util for stopping and starting patrol reads, I place the commands in separate .bat file and schedule the bat files to run off hours, every weekend
if possible
start patrol reads...
MegaPR -startPR -a0
Stop it....
MegaPR -stopPR -a0
Patrol reads takes about 2-3 hours to complete on an array of your size, Approx same with a CC. Consistency check primarily concerns itself with parity checking, patrol reads with media errors. Patrol reads are important as it checks all sectors of the disks in the array. Normally an adapter will mark a sector going bad when it reads from a sector with data, it will not check UNUSED sectors, so the danger with arrays is multiple errors can exist in unused sectors, enough that when an array degrades or is migrated the multiple errors show up, too many for the adapter to manage ..end result more than one drive fails at the same time, a complete array failure.
The larger the array size, the more regular runs of the both above are needed. Read the following Intel link, in the section "why raid 6". I not advocating raid 6 here, it just explains the need to run CC checks/patrol reads on larger raid 5 arrays.
Good Luck
........................................
Chernobyl disaster..a must see pictorial