Reallocated sector count 112 after power disruption/outage

I did a dumb thing and forgot to power off my Unraid box prior to doing some work on my home's AC breaker panel. This led to unexpected disruption in power to the machine. When it came back up, it required a parity check (2-disk parity). The parity check passed, but one of the 8 non-parity disks quickly showed errors at the early portion of the check within the first hour (then no additional errors during the remaining 20+ hrs it took to finish parity check). Should I be concerned? It seems like it has to be due to the power disruption, as it was all clean before, so it's a shame that these sectors are now permanently reallocated (without specialized tools, at least). 

Do hard drives have a limit on how many sectors they will reallocate before total failure? Wasn't clear from online search. I am assuming these reallocations were due to power outage and not a sign of other troubles with the HDD.

I do have a cold spare available, seems like it may be too soon to replace now.

I also have a UPS that I got working with a different Proxmox machine to put it to sleep in event of power loss via NUT server, but have not learned how to use that machine/server to control the Unraid box and tell it to also shut down in case of power loss.

Thank you in advance for any comments from you, the community members

ST14000NM001G

Results of long SMART test performed after the parity check:

ATA Error Count: 3
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 3 occurred at disk power-on lifetime: 12804 hours (533 days + 12 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00      12:03:55.666  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      12:03:55.666  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      12:03:55.666  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      12:03:55.666  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      12:03:55.666  READ FPDMA QUEUED

Error 2 occurred at disk power-on lifetime: 12792 hours (533 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00      00:03:04.460  READ FPDMA QUEUED
  61 00 00 ff ff ff 4f 00      00:03:04.460  WRITE FPDMA QUEUED
  47 00 01 30 03 00 a0 00      00:03:04.439  READ LOG DMA EXT
  47 00 01 30 00 00 a0 00      00:03:04.439  READ LOG DMA EXT
  47 00 01 00 00 00 a0 00      00:03:04.438  READ LOG DMA EXT

Error 1 occurred at disk power-on lifetime: 12792 hours (533 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00      00:03:01.389  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      00:03:01.381  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      00:03:01.380  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      00:03:01.379  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      00:03:01.374  READ FPDMA QUEUED