HDAT2 só da command aborted quando entra em DCO Frozen

[Arthur Guillermo]

Achei um HD velho de 500GB da WD (WD5000BPVT-22HXZ), queria ver se seria possível isolar os badblock so para usar temporariamente enquanto não tenho condições de comprar um novo, quando tentei rodar pela primeira vez já me deparo que começou e logo em seguida só deu command aborted nos proximos setores, pelo que percebi estaria talvez ligado ao DCO Frozen, pois toda vez que faço o bypass ele volta a fazer o teste, porém depois de um tempo entra em DCO frozen e só gera command aborted, alguém sabe o que posso fazer para evitar isso? Ver se ainda há alguma parte boa no HD?

 

Log:

*******************************************************************************
HDAT2 v7.6 DOS (c) 2025 CBL  08.06.2025 11:29:42
*******************************************************************************
Fix with VERIFY/WRITE/VERIFY [WDC WD5000BPVT-22HXZT1]
*******************************************************************************
Device parameters:
-------------------------------------------------------------------------------
Model         : WDC WD5000BPVT-22HXZT1
Device        : SATA
Serial number : WD-WXE1A5145206
Firmware      : 01.01A01
Device sectors: 976,773,168 [500.11 GB]
Sector size   : physical 4096 bytes = 8 logical x 512 bytes
ATA CHS       : 16383/16/63
Current CHS   : 16383/16/63
BIOS CHS      : 1023/255/63
BIOS sectors  : 16,434,495 [8.41 GB]
DPT CHS       : 16383/16/63 (not valid)
DPT sectors   : 976,773,168 [500.11 GB]
Max. LBA mode : 48-bits
Cache size    : 8.39 MB
SMART         : enabled, status: ALERT
ATA major ver.: ATA/ATAPI 1 2 3 4 5 6 7 8
ATA minor ver.: not reported
Mode supported: Ultra DMA 6/ATA133
Mode active   : Ultra DMA 6/ATA133
Translation   : ?
Base unit size: decimal
AHCI speed    : device not present
-------------------------------------------------------------------------------
Test parameters:
-------------------------------------------------------------------------------
Name of test    : Fix with VERIFY/WRITE/VERIFY
Used commands   :
1. VERIFY       : AHCI/NON_DATA [48-bits]
2. WRITE        : AHCI/DMA [48-bits]
3. VERIFY       : AHCI/NON_DATA [48-bits]
Testing mode    : SECTOR MODE
First LBA sector: 0
Last  LBA sector: 976,773,167
Test sectors    : 976,773,168 [500.11 GB]
Test buffer size: 535 sector(s) [273.92 KB]
Write pattern   : 4844|4154h = 'HDAT'
Test direction  : forward
SMART in test   : disabled
CPU access timer: disabled
Events log      : all events
Number of passes: 1
-------------------------------------------------------------------------------
*** Report: pass 1 of 1 [Forward]

Start time: 08.06.2025 11:29:42.290

1. VERIFY: 0000519,485-0000520,019 0% Timeout waiting for command to complete
--> switch to sector mode
1. VERIFY: 0000519,485 0% Command completion time out
2. WRITE : 0000519,485 0% O.K.
3. VERIFY: 0000519,485 0% O.K.
1. VERIFY: 0000519,744 0% Uncorrectable data error (UNC)
2. WRITE : 0000519,744 0% O.K.
3. VERIFY: 0000519,744 0% O.K.
1. VERIFY: 0000519,752 0% Uncorrectable data error (UNC)
2. WRITE : 0000519,752 0% O.K.
3. VERIFY: 0000519,752 0% O.K.
1. VERIFY: 0000519,856 0% Uncorrectable data error (UNC)
2. WRITE : 0000519,856 0% O.K.
3. VERIFY: 0000519,856 0% O.K.
1. VERIFY: 0000519,864 0% Uncorrectable data error (UNC)
2. WRITE : 0000519,864 0% O.K.
3. VERIFY: 0000519,864 0% O.K.
1. VERIFY: 0000519,904 0% Uncorrectable data error (UNC)
2. WRITE : 0000519,904 0% O.K.
3. VERIFY: 0000519,904 0% O.K.
1. VERIFY: 0000520,020-0000520,554 0% Uncorrectable data error (UNC)
--> switch to sector mode
1. VERIFY: 0000520,048 0% Uncorrectable data error (UNC)
2. WRITE : 0000520,048 0% O.K.
3. VERIFY: 0000520,048 0% O.K.
1. VERIFY: 0000520,072 0% Uncorrectable data error (UNC)
2. WRITE : 0000520,072 0% O.K.
3. VERIFY: 0000520,072 0% O.K.
1. VERIFY: 0000520,080 0% Uncorrectable data error (UNC)
2. WRITE : 0000520,080 0% Command aborted
3. VERIFY: 0000520,080 0% Command aborted
1. VERIFY: 0000520,081 0% Command aborted
2. WRITE : 0000520,081 0% Command aborted
3. VERIFY: 0000520,081 0% Command aborted
1. VERIFY: 0000520,082 0% Command aborted
2. WRITE : 0000520,082 0% Command aborted
3. VERIFY: 0000520,082 0% Command aborted
1. VERIFY: 0000520,083 0% Command aborted
2. WRITE : 0000520,083 0% Command aborted
3. VERIFY: 0000520,083 0% Command aborted
1. VERIFY: 0000520,084 0% Command aborted
2. WRITE : 0000520,084 0% Command aborted
3. VERIFY: 0000520,084 0% Command aborted

As vezes aparece estes erros, não sei se é um diagnostico de que realmente a vida util dele já se foi:

Command completion time out

Timeout waiting for command to complete

 

Queria ver se era possível pois um WD Black de notebook consegui uma vez corrigir boa parte dos setores defeituosos com o HDAT2 e isolei a partição com o DiskGenius supostamente nos setores que estavam bons, até hoje ele esta funcionando salvando 364GB de 500GB....