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