Hello, new here. So I am running reinitialize disk surface on an HDD that I connect using USB 3.2 (negotiated speed SATA III)
First, I was doing a read test, and I get a single bad sector (99% health), so I try to reinitialize disk surface. When the reinitialize bad sector hit the bad sector, the speed dropped from 32mb/s to 4-6mb/s
and the green color was dark-medium-light pattern or so
is this normal?
thankyou for your responses
Reinitialize disk surface Speed drop after hitting the "bad" repairable block
-
RegisOrion
- Posts: 1
- Joined: 2025.05.11. 05:45
Reinitialize disk surface Speed drop after hitting the "bad" repairable block
- Attachments
-
- 20250511-173624_RI_HGST_HTS541010B7E610_WXF1EB690539_03.01A03-surface-full.jpg (1.06 MiB) Viewed 925 times
-
- 20250511-104353_RI_HGST_HTS541010B7E610_WXF1EB690539_03.01A03-surface-full.jpg (1.02 MiB) Viewed 933 times
-
- 20250511-105120_RI_HGST_HTS541010B7E610_WXF1EB690539_03.01A03-surface-full-st.jpg (701.49 KiB) Viewed 933 times
-
hdsentinel
- Site Admin
- Posts: 3192
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: Reinitialize disk surface Speed drop after hitting the "bad" repairable block
What we can call "normal"?
I mean is a "bad sector" or disk problem/failure normal?
Of course on a perfect drive we would expect the the test will go with (near) constant speed, but on a drive with a problem (even a minor issue) yes, we can encounter that the performance drops as soon as the drive recognised (and repaired) the appropriate sector.
The darker green blocks suggest that the appropriate area is much slower (more dark = more slow) compared to the expected speed.
Probably when the problematic sector reached, the repair required some time and a timeout may happened. As a result, it is possible that the USB enclosure / USB controller automatically decreased the performance.
If I'd see similar, probably I'd cancel the test and would make a complete power off/on cycle of the drive (disconnect and then re-connect the drive as it is connected over USB) and would start the test again, just to verify if the same happens (and at the same position).
I also suggest to use Report menu -> Send test report to developer option, it can help to check the actual situation, the complete status of the disk drive. It may give some further ideas, thoughts.
I mean is a "bad sector" or disk problem/failure normal?
Of course on a perfect drive we would expect the the test will go with (near) constant speed, but on a drive with a problem (even a minor issue) yes, we can encounter that the performance drops as soon as the drive recognised (and repaired) the appropriate sector.
The darker green blocks suggest that the appropriate area is much slower (more dark = more slow) compared to the expected speed.
Probably when the problematic sector reached, the repair required some time and a timeout may happened. As a result, it is possible that the USB enclosure / USB controller automatically decreased the performance.
If I'd see similar, probably I'd cancel the test and would make a complete power off/on cycle of the drive (disconnect and then re-connect the drive as it is connected over USB) and would start the test again, just to verify if the same happens (and at the same position).
I also suggest to use Report menu -> Send test report to developer option, it can help to check the actual situation, the complete status of the disk drive. It may give some further ideas, thoughts.