You do NOT want to run a correcting check with a disk reporting read errors as this is just likely to end up corrupting parity. This is one of the reasons we recommend that scheduled checks are set non-correcting so you only run correcting checks when you do not have any hardware errors. You might as well cancel the current check if it is still running.
The SMART information for disk5 looks fine, but the syslog shows the drive getting continual resets that look like connection issues prior to starting reporting read errors. I suggest carefully reseating the cabling to the drive (both power and SATA) and then trying the check again (non-correcting).