Recover "Current Pending Sector Count" S.M.A.R.T. error

[diybit]

Forget for the block size 1 for the moment.
Look if the orange is now repaired at LBA 997005312, do a Victoria read with block size 2048 from 996960000 to 997050000.
If the block is now fine, redo a full read with the chart, and enlarge the log window for we see the warnings.

[glhd]

I did several tests including the range where the problematic sectors were located in the previous tests.

The exact address of the slow sectors shown in the previous images has changed, but other slow sectors are still detected in the space around 510 and 618 MB.

Below the tests log:

Victoria 5.36 HDD/SSD | Device 1 log file. 19/04/2021
23:08:16 : Starting Victoria 5.36 HDD/SSD. 1xCPU, 2198,09 MHz, Windows 7 x64 found.
23:08:16 : [Hint] Recommend 32-bit Windows XP for a best work!
23:08:16 : Warning! Windows x64 detected! PIO mode supported on Windows x86 only.
23:08:16 : API access enabled, device #0
23:08:17 : Get drive passport... OK
23:08:17 : Model: TOSHIBA MQ01ABD075; Capacity 1465149168 LBAs; SN: *********; FW: AX003J
23:08:17 : Press F1 to About/HELP
23:08:20 : Get drive passport... OK
23:08:20 : Model: TOSHIBA MQ01ABD075; Capacity 1465149168 LBAs; SN: *********; FW: AX003J
23:08:39 : Get drive passport... OK
23:08:39 : Recallibration... OK
23:08:39 : Starting Reading, LBA=0..150000, FULL, sequential access, timeout 10000ms
23:08:40 : *** Scan results: no warnings, no errors. Last block at 150000 (77 MB), time 1 seconds.
23:08:40 : Speed: Maximum 89 MB/s. Average 66 MB/s. Minimum 44 MB/s. 68 points.
23:09:21 : Get drive passport... OK
23:09:22 : Recallibration... OK
23:09:22 : Starting Reading, LBA=996960000..997050000, FULL, sequential access, timeout 10000ms
23:09:23 : Warning! Block start at 997005056 (510 GB) = 1140 ms
23:09:24 : Block start at 997007104 (510 GB) = 625 ms
23:09:24 : *** Scan results: Warnings - 2, errors - 0. Last block at 997050000 (510 GB), time 2 seconds.
23:09:24 : Speed: Maximum 67 MB/s. Average 33 MB/s. Minimum 0 MB/s. 38 points.
23:10:27 : Get drive passport... OK
23:10:27 : Recallibration... OK
23:10:27 : Starting Reading, LBA=1207900000..1208000000, FULL, sequential access, timeout 10000ms
23:10:29 : Block start at 1207945056 (618 GB) = 921 ms
23:10:29 : *** Scan results: Warnings - 1, errors - 0. Last block at 1208000000 (618 GB), time 2 seconds.
23:10:29 : Speed: Maximum 67 MB/s. Average 37 MB/s. Minimum 7 MB/s. 43 points.

[diybit]

I think that those parts are going to stay problematic.

So I recommend you to right partition, that is anyway the most safe way you have.
Use a margin of 250MB that is finally enough, like 250MB-weakpart-250MB.

You will likely have to get 3 partitions, here how to calc them:
250MB = 250*2*1024 = 512000LBA
512000LBA = 512000/2/1024/1024 = 0.24414GB = 0.24GB or 0.25GB

109000-109631
110000+512000 = 622000LBA = 0.29659GB = 0.32 GB first partition start

997005056-997007104
997005000-512000 = 996493000 = 475.16489 = 475.14 GB first partition end
997008000+512000 = 997520000 = 475.65460 = 475.68 GB second partition start

1207945056-1207945552
1207944000-512000 = 1207432000 = 575.74844 = 575.72 GB second partition end
1207946000+512000 = 1208458000 = 576.23767 = 576.26 GB third partition start and go to end

There are lot of chance that the others 500 realloc are part of those defect parts.
I have about added them to the calc, and re-added or sub about 0.02GB margin.

Confirm that your tool for partitioning is reporting your drive as about 699GB capacity before apply those kind of partitions.

I recommend you doing a last full read and adapt your partitions with the help of the slow sectors.
And do not touch the computer while it's scanning. (and disable, exit softs you can)

[glhd]

I think that those parts are going to stay problematic.
So I recommend you to right partition, that is anyway the most safe way you have ...

Yes, scanning the affected areas with "Block size 1", you can see that there are many dozens of slow sectors. This is the final result of the partitioning:

I recommend you doing a last full read and adapt your partitions with the help of the slow sectors.
And do not touch the computer while it's scanning. (and disable, exit softs you can)

All previous tests were run with Vitoria in API mode on a VmWare virtual machine running Windows 7 Pro 64 bit, using this Usb > Sata adapter

I've repeated all tests running Victoria on Win10XPE x86 connecting the disk directly to the Sata port of the pc: the results of the read tests performed in API mode confirm exactly the errors found in the previous tests.

[glhd]

In the last few days, I first did a complete formatting of the three partitions, then filled the disk with the backup data. Now there are about 50 GB of free space.

After writing the first 145 GB to the first partition and disconnecting and reconnecting the disk, I noticed that Crystal Disk Info reported another reallocation event with 8 more sectors reallocated for a total of 640.

After this reallocation of sectors no other reallocation occurred, but the task of this disk is now to be used for reading operations only if ever needed ...

Thanks to Diybit for the help given.

[diybit]

Be well careful with this drive! because having re-found some bad sectors after all erase/read pass you have done is not promising... and some others may appear later...

Maybe there are another bad spot that we haven't bypass, or/and perhaps we haven't right bypass because of too small margin finally with 250MB...

Also this drive model seems to me more affected by sector problems...

I suggest you doing 2 pass of the SMART extended test before unplug for good this drive.
It will indicate you the exact LBA where it stopped for an eventual error, and this time with the internal scan that seems more sensible to detect problems.

[glhd]

Be well careful with this drive! because having re-found some bad sectors after all erase/read pass you have done is not promising... and some others may appear later...

Yes, but the disk serves as a third backup and I may never need to use it again.

Maybe there are another bad spot that we haven't bypass, or/and perhaps we haven't right bypass because of too small margin finally with 250MB...

Maybe these 8 reallocated sectors are already in the space excluded from partitioning and are due to the scan that the disk does when idle ...

I suggest you doing 2 pass of the SMART extended test before unplug for good this drive.
It will indicate you the exact LBA where it stopped for an eventual error, and this time with the internal scan that seems more sensible to detect problems.

Is there any way to query the disk firmware and get the full list of sectors that have been reallocated, perhaps using Smartclt, the disk serial interface, Victoria in PIO mode or any other means ?

[diybit]

Normally this drive do not have background scan enabled, you can verify it with smartctl --all.
So normally no more defect can happen if all is right bypassed.
Do you hear the drive is doing something when idle? (or touch it)

About the SMART extended test, I have think that perhaps it will anyway fail on the sector that you already know they are "bad"...
The LBA in error where it stopped will be shown in the smartctl report.
So maybe re-done at least a Victoria full read instead, and take the green timings as bad block.

Sadly I do not know a way for reading the G-List on this drive. (maybe try a demo version of sediv)

[glhd]

Normally this drive do not have background scan enabled, you can verify it with smartctl --all.
So normally no more defect can happen if all is right bypassed.
Do you hear the drive is doing something when idle? (or touch it)

No, there is no activity that would suggest that the disk is reading. Smartctl --all does not seem to indicate that the disk is performing a backgroud scan. This is the command output.

Sadly I do not know a way for reading the G-List on this drive. (maybe try a demo version of sediv)

All links to the demo version of SeDiv that I have found are not working. Suggestions of a working link are welcomed.

[diybit]

Auto Offline Data Collection: Disabled.
This is saying you do not have auto background scan.

40 51 02 80 96 0a 40 Error: UNC 2 sectors at LBA = 0x000a9680 = 693888
This is saying that we have at least another bad spot at 693888 LBA.

So do the SMART extended test with "smartctl -t long" and let it go to the end to see if it stop on another error.
You can see the progress somewhere by doing --all during the scan.
The end result will be displayed at the end report "SMART Self-test log structure".

About SeDiv demo, you can found some at hddoracle.com, like there or there.
But not sure that it will be easy to convert what you found to LBA if the soft do not help you about this.