When doing a Write Zeros using Lifeguard Diagnostics (1.27) I noticed that when the process took more than 24 hours the Elapsed Time indicator reset to 00:00:00. So the indicated Elapsed Time is now out by 24 hours.
Hello,
Whats the capacity of your drive? A drive should not take 24 hours to write zeros. Have you tried running a diagnostic to verify the drive’s health?
it’s a 4 year old 2TB Western Digital Green WD20EARS.
And yes, it was having SMART problems with Raw Read Error Rate, Relocated Sector Count, Relocation Event Count and Current Pending Sector Count.
I’d just finished moving everything I could and lost about 60 eBooks.
I tought I’d run the Write Zeros to clear whatever was left on the drive before I pulled it out.
As stated earlier, the Write Zeros ran for more than 24 hours,
It actually ran for 33 hours, 20 minutes and 40 seconds.
I was expecting delays as the drive is on the way out.
Copy under Win 8.1 would go away for anything from minutes to several hours before producing an error.
The point of the post was not that Write Zeros took over 24 hours, but that the the Elapsed Time counter in Lifeguard Diagnostics is displaying incorrect Elapsed Times on tasks that run for more than 24 hours.
I’d consider this to be a bug in the application.
