|
drive burn in
|
10-30-2008, 06:34 PM
RAMd®d wrote: It might run flawlessly for that time, then fail on the next startup or restart. That was my gut reaction as well, and I was just curious if there was any widespread use of these practices that I wasn't aware of... I guess it boils down to this question: what's the simplest, most efficient way to map out bad blocks, both on a new drive, and over time? DiskWarrior should do this, right? |
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
drive burn in - by beerman - 10-27-2008, 05:42 PM
Re: drive burn in - by ztirffritz - 10-27-2008, 05:50 PM
Re: drive burn in - by mattkime - 10-27-2008, 05:56 PM
Re: drive burn in - by Doc - 10-27-2008, 06:08 PM
Re: drive burn in - by beerman - 10-27-2008, 06:11 PM
Re: drive burn in - by Harbourmaster - 10-27-2008, 06:45 PM
Re: drive burn in - by motopsyco - 10-27-2008, 06:50 PM
What is a "burn-in" for an HD? - by RAMd®d - 10-27-2008, 06:51 PM
Re: drive burn in - by ztirffritz - 10-27-2008, 06:59 PM
Re: drive burn in - by beerman - 10-27-2008, 08:43 PM
Re: drive burn in - by beerman - 10-28-2008, 03:06 AM
Re: drive burn in - by john-o - 10-30-2008, 05:52 PM
Re: drive burn in - by RAMd®d - 10-30-2008, 06:12 PM
Re: drive burn in - by john-o - 10-30-2008, 06:34 PM
Re: drive burn in - by ScottG - 10-30-2008, 07:41 PM
Re: drive burn in - by beerman - 10-31-2008, 04:54 PM
|
