1 |
On Mon, 2008-05-05 at 11:14 +0800, Iain Buchanan wrote: |
2 |
> Hi all, |
3 |
> |
4 |
> I have two 2.5in HD's, one 60Gb with a heap of bad sectors currently |
5 |
> used in external Hd enclosure, and one 100Gb which seems in good |
6 |
> condition, currently in my laptop. |
7 |
> |
8 |
> I'm upgrading my laptop, and I'd like to turn the old one into a myth |
9 |
> frontend or something similar, so I want to put the 60Gb in it. I will |
10 |
> then use the 100Gb in my external enclosure for travelling, backups, |
11 |
> etc. |
12 |
> |
13 |
> The reason the 60Gb has bad sectors (I think) is because I dropped it |
14 |
> (in it's enclosure). This was quite some time ago, and it doesn't seem |
15 |
> to be dying any further, but I haven't done any comparisons on the bad |
16 |
> sector count. I use nearly 100% of the space available, and regularly |
17 |
> compare cksums, so if anything was deteriorating, I would know. |
18 |
> |
19 |
> The question is: should I use it at all (for any use, external HD or |
20 |
> internal with operating system), or is it sufficient to let the fsck |
21 |
> tool mark the bad sectors and just keep using it? |
22 |
> |
23 |
> Is there a way to monitor it's "health" in the external enclosure until |
24 |
> I get my new laptop? Is counting the bad sectors enough? |
25 |
> |
26 |
|
27 |
As I understand it, hard disks usually hide bad blocks from the OS as |
28 |
long as they can utilize spare blocks. That means that there might be a |
29 |
lot more bad blocks than you are aware of. |
30 |
|
31 |
Last week I had my own notebook hard disk (60Gig as well) dying on me: |
32 |
Bad blocks on a single partition, strange noises from time to time and |
33 |
the S.M.A.R.T offline self test aborting with "read error" before it |
34 |
even started. |
35 |
I found smartmontools (or anything that's just polling SMART) |
36 |
inappropriate. They still reported "all is well" although the self tests |
37 |
failed (and were logged as failed) and an overheating occurrence was |
38 |
logged (half a year ago the disk reached 53°C during normal operation |
39 |
for no apparent reason). Bad blocks were not registered at all! |