![]() Yes i've only ever run the full surface scan which takes 6+ hoursĪnd in fact even when you run the short scan, with enough repetitions, the error still comes up So basically, having took delivery on Oct 22nd - 5 weeks later and still no drive to work with.G'day mate I've requested a retest last Monday 22nd - a week on and I still haven't got an answer yet. I would have happily kept the drive if it did not develop WRITE errors (being my main concern other errors include RAW read rate and G-sense errors).Īs I've stated, I was very hesitant in RMA'ing the drive in the first instance, running tests to satisfy myself to avoid the no fault found fee that Scan imposes (not a decision I took lightly). exhibit write errors, with the count rate increasing as more and more data is written to the drive (like mine did)? ![]() pass the new ESTool version after running the FULL 6+hrs diagnostics (I ask as many will pass the short test - like mine, and as I've mentioned previously, will pass the short test on a loop)Ģ. Two things I need to clarify from the outset:ġ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |