Question for the experts : Will the mover script pickup this corruption?
No script will pick up on the problem... There is no error returned but the data "written" to the disk is not written to the disk platter.
It is even worse than that... If you do a parity "check" it will read the zeros (or whatever) was in the sectors that should have been written, report a parity error and then update parity to reflect the bad data on the disk. Ouch.
If you disabled the F4 disk (un-assign it) then start the array without it, then stop and re-assign it you can get the parity disk in combination with the other disks to potentially write the correct data to the F4 drive as part of its re-construction. You'll be without parity protection until it completes, but at least your data will be good when it is done.
This will only work if you have not over-written parity with the stock unRAID "Check" button before attempting the drive re-construction.