Elnézést, nem szeretném a végtelenségig ragozni, de az általad linkelt Wiki oldal is ezt írja:
Current pending sector count: Count of "unstable" sectors (waiting to be remapped, because of unrecoverable read errors). If an unstable sector is subsequently read successfully, the sector is remapped and this value is decreased. Read errors on a sector will not remap the sector immediately (since the correct value cannot be read and so the value to remap is not known, and also it might become readable later); instead, the drive firmware remembers that the sector needs to be remapped, and will remap it the next time it's written.[33] However some drives will not immediately remap such sectors when written; instead the drive will first attempt to write to the problem sector and if the write operation is successful then the sector will be marked good (in this case, the "Reallocation Event Count" (0xC4) will not be increased). This is a serious shortcoming, for if such a drive contains marginal sectors that consistently fail only after some time has passed following a successful write operation, then the drive will never remap these problem sectors.
Ahogyan más, interneten fellelhető források szerint is a HDD-nek kell kezelni az ilyen jellegű szektor szintű hibákat. Szerintem nem az OS/FS párosnak kell megoldani, hogy a HDD-n nyilván tartsa a gyanús szektorokat, és migrálja róla az adatokat máshová, ha sokáig fennáll ez az állapot (merthogy honnan tudná az OS, hogy a kiszemelt célterület nem egy másik problémás szektor pl.).