Dear hhd Gurus
explain to me ( the disk profane ) how the f... can
ONLY 7 BAD CLUSTERS on a 2tb wd blue 3.5 drive ( 44gb user data out of 2tb capacity )
can effing jam and bog down the disk from average normal 30mb/s
to effing 300kb/s and make the disk hardly responsive and slow as f...k !
history:
- used disk was reformatted, checked with chkdsk /r /f /x
and supposed to be used for simple backup of a backup of a backup
- atto benchmarked at up 30mb/s on usb2, ie normal speed
- smart in CrystalDiskInfo is decent, minor bad sectors, caution status
- in win10, copying/backing up files to this external disk
- all going well, decent speed, no problems
- all of the sudden the disk slows down to a crawl
- WTF is uttered, scramble activated
- next, what to do ?
- measured speed in ATTO, effing 300kb/s now
- disk is slow to respond, to mount, reading/writing is virtually unusable
- win explorer -> drive -> tools -> error checking -> took around 2 hours
no errors
- next did chkdsk /f /r /x , took about 1 hour
- found and replaced 7 bad clusters ( see printout below )
- ran atto benchmark again -> SPEED IS BACK UP TO 30mb/s ie PROBLEM SOLVED
now, the question again
how the f...k can only 7 bad clusters virtually make the disk unusable
by slowing it down to a effing crawl ???
please, I need freaking answers, what is happening internally ?
same question/issue "SLOW WD drive" is plastered all over the internet
with no solutions for the common folks, other than clear relo-list for pros
WD is silent on the issue ( probably afraid of class action lawsuit ) other
then we are sorry and start warranty replacement process or replace the drive
bad WD firmware ??? crappy WD implementation ???
what is likely to be the problem ??? really only 7 bad clusters is the disk is kaput !
I can not believe that ONLY 7 effing bad sectors can jam the drive to not usable status !!!
and that fixing those 7 sectors restores disk speed to specifications .
++ I ran chkdsk again on same data ( no data change on disk, no write to disk )
and it found 1 more bad clusters again, what the f...k again?
it appears to be not a consistent algo for finding bad clusters with chkdks
Please experts, drop a few lines of explanations for the poor here...
++ I developed phobia for WD drives... most of them seem to go bad left and right
for minute problems...
( removed file names )
Microsoft Windows [Version 10.0.18363.1500]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Windows\system32>chkdsk /f /r /x F:
The type of the file system is NTFS.
Volume label is WD Blue.
Stage 1: Examining basic file system structure ...
49152 file records processed.
File verification completed.
449 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
8 reparse records processed.
53670 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
8 reparse records processed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
2260 data files processed.
CHKDSK is verifying Usn Journal...
2432976 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
Windows replaced bad clusters in file B725
of name \Archive\LM10\Backup\Grub\...
Windows replaced bad clusters in file B777
of name \Archive\LM10\Documents\...
Windows replaced bad clusters in file B950
of name \Archive\LM10\Documents\Pdfs\...
Windows replaced bad clusters in file B951
of name \Archive\LM10\Documents\Pdfs\...
Windows replaced bad clusters in file BBB3
of name \Archive\LM10\Documents\Pdfs\SPORT\...
Windows replaced bad clusters in file BBE1
of name \Archive\LM10\Documents\Pdfs\...
Windows replaced bad clusters in file BC13
of name \Archive\LM10\Documents\Pdfs\...
49136 files processed.
File data verification completed.
An unspecified error occurred (766f6c756d652e63 470).