The drive will be disabled until it is rebuilt. Since a write to it failed, it is out of sync with parity. But the data for that failed write is still in the array from the parity calculation. In fact, Unraid will not even use a disk after it has been disabled. All attempts to access the disk, whether reading or writing, is done by emulating the disk from parity. So, the contents of the disk can still be read, but that is accomplished by reading parity PLUS ALL other disks and calculating the data for the disk. And all writes to the disk don't actually write the disabled disk, it just updates parity as if the disk were written.
So, the disk must be rebuilt. Rebuilding will not delete all of the data off it. It will instead write all of the data onto it, including the failed write and any subsequent writes that didn't actually go to the disk because it was disabled.
The safest approach is to rebuild to a new disk, since that allows you to keep the original disk as a backup in case there is some issue during rebuild. But obviously that requires a spare disk.
The most likely cause of an issue during rebuild is another bad connection, possibly with another disk. All disks must be reliably read in order to calculate the data for the rebuild. When I said check all connections, I meant all, even those for other disks. It is very common for someone to disturb the connections of other disks when they are inside the case.
SMART for that disk looks fine except for the connection issue so if that is fixed it should be OK to reuse.
To rebuild the disk to itself:
Stop array
Unassign disabled disk
Start array so the missing disk is registered
Stop array
Reassign disabled disk
Start array to begin rebuild