1 |
On Sunday 29 Jun 2014 13:05:04 Rich Freeman wrote: |
2 |
> On Sun, Jun 29, 2014 at 12:44 AM, Dale <rdalek1967@×××××.com> wrote: |
3 |
> > What if I copied data to the drive until it was just about full. I'm |
4 |
> > thinking like maybe 90 or 95% or so. If I do that and run the test |
5 |
> > every few days, would it then catch a error after a few weeks or so of |
6 |
> > testing? I realize no one knows with 100% certainty... |
7 |
> |
8 |
> As you already said, nobody knows with 100% certainty. |
9 |
> |
10 |
> In the failures I've experienced I'd expect it to start catching |
11 |
> errors within a few days. However, on those drives the relocated |
12 |
> sector count never increases, which suggests that the firmware never |
13 |
> relocated those sectors when overwritten, which seems brain-dead to |
14 |
> me. |
15 |
> |
16 |
> If the drive relocates the sectors, then conceivably it could go quite |
17 |
> a long time until having errors, probably in an entirely different set |
18 |
> of sectors. |
19 |
> |
20 |
> Even if it doesn't relocate, the reliability of the bad sectors could |
21 |
> be high or low. |
22 |
> |
23 |
> Rich |
24 |
|
25 |
What triggers a relocation? I also have a drive which shows a sector |
26 |
relocation pending, but for a few days now and after some tests that showed no |
27 |
errors, it won't relocate it. |
28 |
|
29 |
-- |
30 |
Regards, |
31 |
Mick |