Looking at the diagnostics the check was paused because mover was running. Mover and parity check very badly affect the performance of each other so you do not normally want them running at the same time. Any idea why mover was running? If you have notifications enabled then you should have received one giving the reason why the check was paused.
I also noticed the following:
Aug 1 21:30:46 Tower kernel: critical medium error, dev sdl, sector 1325225704 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3
Aug 1 21:30:46 Tower kernel: Buffer I/O error on dev sdl, logical block 165653213, async page read
which probably needs looking at.