S.M.A.R.T. reallocated sector count failure

[Colonel Blip]

Hello, All!

I checked the health of my drives, 2 SATA (Raid0), and 2 IDE drives. All of
them are showing ID5 reallocated sector count failures. I can understand one
showing this but all of them?? Any ideas what could cause this?

Thanks,
Colonel Blip.
E-mail: (e-mail address removed)

 

[Rod Speed]

I checked the health of my drives, 2 SATA (Raid0), and 2 IDE drives. All
of them are showing ID5 reallocated sector count failures. I can
understand one showing this but all of them?? Any ideas what could cause
this?

Some drives like some maxtors appear to deliberately ship them
that way and let the initial use sort out the marginal sectors that way.

Running the drives stinking hot can get that result too.

Presumably running the drives on a marginal power
supply can too, tho I havent actually seen that happen.

 

[Arno Wagner]

Hello, All!

I checked the health of my drives, 2 SATA (Raid0), and 2 IDE drives. All of
them are showing ID5 reallocated sector count failures. I can understand one
showing this but all of them?? Any ideas what could cause this?

A bad PSU can have this effect. Overheating and mechanical shock
or vibration during operation can also cause this. There are
other potential problems that could affect all drives.

Oh, and of course the software may be misreporting things. What
are the raw reallocated count values?

Arno

 

[Colonel Blip]

Folks,

I checked with Everest and HDTune and both give the following, except that
HDTune noted all three failed the ID5.

Data - ID5 Current Worst Threshold
Data

Drive 1 227 227 63
268
Drive 2 100 100 20
1
Drive 3 (raid) 1 1 5
1883


1. Is it possible that a blue screen of death crash (hardware related) could
result in this?

2. Is it possibe the drives are all ok but had to do corrections because of
this kind of event and could be put back in order by reformatting them?

3. If 2. would work, and the backup is an image file (Ghost) would restoring
produce the same results?

Thanks,

Colonel Blip.
E-mail: (e-mail address removed)

??>> Hello, All!
AW> A bad PSU can have this effect. Overheating and mechanical shock
AW> or vibration during operation can also cause this. There are
AW> other potential problems that could affect all drives.

AW> Oh, and of course the software may be misreporting things. What
AW> are the raw reallocated count values?

AW> Arno

 

[Arno Wagner]

Folks,

I checked with Everest and HDTune and both give the following, except that
HDTune noted all three failed the ID5.

Data - ID5 Current Worst Threshold Data
Drive 1 227 227 63 268
Drive 2 100 100 20 1
Drive 3 (raid) 1 1 5 1883

O.k., I will try an interpretation. The last column is the "raw"
value.

Drive1: 268 reallocated sectors. That is relevant. This may or may not be
a real problem. You should run a smart long self-test and see whether the
number changes. If it does the drive has a problem. If not, you
should keep an eye on it, i.e. check it every few days for some weeks.
The "normalised value" is 227, which is significantly larger than the
failed threshold of 63 (larger is better), likely out of a maximum
of 255, i.e. the attribute has dropped from 255 (perfect) to 227
(still not necessarily a problem).

Drive2: 1 reallocated sector. Not an issue at all. The drive is likely
ok. Why your tool reports a failed is beyond me. Maybe it is just
paranoid. The "normalised value" is 100, likely out of 100, i.e.
still perfect. (Some disks use 100 as "best" value, some 255, some
even mix both.)

Drive3: 1883 reallocated sectors. Bad. "Normalised value" 1, which
is below the threshold of 5. This disk actually has a failed smart
status, i.e. a value is below the threshold. This disk is dying and
it may alsready be unreadable in some areas.

Summary: Disk 1 may be o.k. or not. Disk 2 is fine. Disk 3 is dead or
dying.

Todo: - Keep an eye on the raw number of reallocated sectors of disk 1
(the last value in the attribute line) and run a long SMART
self-test on it.
- Replace Disk 3 now.

1. Is it possible that a blue screen of death crash (hardware related) could
result in this?

I doubt it.

2. Is it possibe the drives are all ok but had to do corrections because of
this kind of event and could be put back in order by reformatting them?

No. Reformatting does not work that way today. A reallocated sector is
and stays a reallocated sector. There is nothing the user can do about
it. But these are not defect secotrs. The drive already has mapped the
logical sector numbers to spare sectors. But as some time the good
spares run out and the reallocation is the sign of some more fundamental
problem, that may also kill the disk completely, possibly without
further warning.

3. If 2. would work, and the backup is an image file (Ghost) would restoring
produce the same results?

No. The sectors are allready remapped to good ones.

Arno

 

[Folkert Rienstra]

O.k., I will try an interpretation. The last column is the "raw" value.

Drive1: 268 reallocated sectors. That is relevant. This may or may not
be a real problem. You should run a smart long self-test and see whether
the number changes. If it does the drive has a problem. If not, you
should keep an eye on it, i.e. check it every few days for some weeks.
The "normalised value" is 227, which is significantly larger than the
failed threshold of 63 (larger is better), likely out of a maximum
of 255, i.e. the attribute has dropped from 255 (perfect) to 227
(still not necessarily a problem).

268 bad sectors replaced out of millions of spares is absolute peanuts.

Drive2: 1 reallocated sector. Not an issue at all. The drive is likely
ok. Why your tool reports a failed is beyond me. Maybe it is just
paranoid. The "normalised value" is 100, likely out of 100, i.e.
still perfect. (Some disks use 100 as "best" value, some 255, some
even mix both.)

Drive3: 1883 reallocated sectors. Bad. "Normalised value" 1, which
is below the threshold of 5. This disk actually has a failed smart
status, i.e. a value is below the threshold. This disk is dying and
it may alsready be unreadable in some areas.

1883 reallocated sectors out of millions of spares is peanuts.

Summary: Disk 1 may be o.k. or not. Disk 2 is fine. Disk 3 is dead or dying.

Not with those absolute numbers. Perhaps they were accumulated during
a very short time and that that had an effect on the Normalized values
decreasing faster. If the problem stops the normalized values may return
to more normal values with time.

Todo: - Keep an eye on the raw number of reallocated sectors of disk 1
(the last value in the attribute line) and run a long SMART
self-test on it.

- Replace Disk 3 now.

It's a RAID, babble box. Which one?
The numbers are likely faked anyway.

I doubt it.

If the crash coincided with power failures, sure, why not.

No. Reformatting does not work that way today.

It does on some.

A reallocated sector is and stays a reallocated sector.

Nope. Some drives can retest bad sectors and reformat tracks so that
Logical Block Addresses are sequential again.

There is nothing the user can do about it.

With some drives but not others.

But these are not defect secotrs. The drive already has mapped the
logical sector numbers to spare sectors. But as some time the good
spares run out and the reallocation is the sign of some more fundamental
problem, that may also kill the disk completely, possibly without
further warning.

Not with those absolute peanut numbers.

No. The sectors are allready remapped to good ones.

But it may take care of still pending ones.

 

[Colonel Blip]

Hello, Arno!
You wrote on 24 Feb 2006 12:35:54 GMT:

Thanks for the interpretation and advice. As noted, drive 3 is a RAID array
consisting of 2 identical Maxtor drives (RAID0). Best I can tell only one
drive (1/2 of the capacity) is being reported so I'm not sure what the smart
data source is. Guess if it fails I will have to separate them and test them
as non-raid. May do that before they fail by booting on other
drive/partition.

One other question - how does on run a long SMART test?

Thanks,

Colonel Blip.
E-mail: (e-mail address removed)

??>> Folks,
AW> O.k., I will try an interpretation. The last column is the "raw"
AW> value.

 

[Arno Wagner]

Hello, Arno!
You wrote on 24 Feb 2006 12:35:54 GMT:

Thanks for the interpretation and advice. As noted, drive 3 is a RAID array
consisting of 2 identical Maxtor drives (RAID0). Best I can tell only one
drive (1/2 of the capacity) is being reported so I'm not sure what the smart
data source is.

Good question. Depends on the controller, I guess.

Guess if it fails I will have to separate them and test them
as non-raid. May do that before they fail by booting on other
drive/partition.

You should do that as soon as possible. You can e.g. have them as
single disk on an IDE controller and use a Knoppix CD to boot. The
SMART tool there is smartctl (on the commandline).

One other question - how does on run a long SMART test?

I suse smartctl, which is a Unix tool, but also works under Windows.

For long self-test use the following commandline:

smartctl -t long <device>

Arno

 

[Rod Speed]

I checked with Everest and HDTune and both give the following, except
that HDTune noted all three failed the ID5.

Data - ID5 Current Worst Threshold Data

Drive 1 227 227 63 268
Drive 2 100 100 20 1
Drive 3 (raid) 1 1 5 1883

Urk, those are extremely high except for Drive 2 obviously.

1. Is it possible that a blue screen of death crash (hardware related)
could result in this?
Nope.

2. Is it possibe the drives are all ok but had to do corrections because
of this kind of event and could be put back in order by reformatting
them?
Nope.

3. If 2. would work, and the backup is an image file (Ghost) would
restoring produce the same results?

Nope, the drives have already added those bad
sectors to the bad sector list and they wont be
removed from that by restoring an image now.

What is the brand/model detail of the drives ?

Show the full SMART data for all drives, that may
have some extra useful info like the temperatures too.

 

[Rod Speed]

268 bad sectors replaced out of millions of spares is absolute peanuts.

Its still very high for a good drive. Something
must have produced all those bads.

1883 reallocated sectors out of millions of spares is peanuts.

Not a clue, as always.

Not with those absolute numbers. Perhaps they were accumulated
during a very short time and that that had an effect on the Normalized
values decreasing faster. If the problem stops the normalized values
may return to more normal values with time.

Not a clue, as always. It certainly indicates a problem somewhere.

It's a RAID, babble box. Which one?
The numbers are likely faked anyway.

If the crash coincided with power failures, sure, why not.

Very bloody unlikely to produce that many bads.

It does on some.

**** all in fact. And those that do flout the SMART standard.

Nope. Some drives can retest bad sectors and reformat
tracks so that Logical Block Addresses are sequential again.

But they shouldnt remove reallocated sectors, stupid.

With some drives but not others.

**** all in fact. And those that do flout the SMART standard.

Not with those absolute peanut numbers.

Not a clue, as always.

Something must have produced those very high numbers.

But it may take care of still pending ones.

Not what he asked.

 

[Colonel Blip]

Following is the full smart info. The drive in question is the 3rd one,
which is actually 2 SATA 80gb Hitachi drives on a Via m/b controller setup
as RAID0.
Here is info on the Hitachi followed by the SMART for all three. The 2
Hitachi drives are identical.

[ HDS722580VLSA80 (VN6B7SCBE7XXPD) ]

ATA Device Properties:
Model ID HDS722580VLSA80
Serial Number VN6B7SCBE7XXPD
Revision V32OA69A
Parameters 155010 cylinders, 16
heads, 63 sectors per track, 512 bytes per sector
LBA Sectors 156250000
Buffer 7938 KB (Dual
Ported, Read Ahead)
Multiple Sectors 16
ECC Bytes 4
Max. PIO Transfer Mode PIO 4
Max. UDMA Transfer Mode UDMA 5 (ATA-100)
Active UDMA Transfer Mode UDMA 5 (ATA-100)
Unformatted Capacity 76294 MB


--------[
SMART ]-------------------------------------------------------------------------------------------------------

[ Maxtor 6Y080P0 (Y25XADLE) ]

03 Spin Up Time 63 224 223 10235 OK:
Value is normal
04 Start/Stop Count 0 253 253 336 OK:
Always passing
05 Reallocated Sector Count 63 227 227 268 OK:
Value is normal
06 Read Channel Margin 100 253 253 0 OK:
Value is normal
07 Seek Error Rate 0 253 244 0 OK:
Always passing
08 Seek Time Performance 187 252 243 38093 OK:
Value is normal
09 Power-On Time Count 0 199 199 9283 OK:
Always passing
0A Spin Retry Count 157 253 252 0 OK:
Value is normal
0B Calibration Retry Count 223 253 252 0 OK:
Value is normal
0C Power Cycle Count 0 253 253 363 OK:
Always passing
C0 Power-Off Retract Count 0 253 253 0 OK:
Always passing
C1 Load/Unload Cycle Count 0 253 253 0 OK:
Always passing
C2 Temperature 0 253 253 40 OK:
Always passing
C3 Hardware ECC Recovered 0 253 252 5349 OK:
Always passing
C4 Reallocation Event Count 0 253 253 0 OK:
Always passing
C5 Current Pending Sector Count 0 253 253 0 OK:
Always passing
C6 Off-Line Uncorrectable Sector Count 0 253 253 0 OK:
Always passing
C7 Ultra ATA CRC Error Rate 0 199 199 0 OK:
Always passing



[ MAXTOR 6L080L4 (664224152344) ]

01 Raw Read Error Rate 20 100 253 0 OK:
Value is normal
03 Spin Up Time 20 69 64 3920 OK:
Value is normal
04 Start/Stop Count 8 99 99 777 OK:
Value is normal
05 Reallocated Sector Count 20 100 100 1 OK:
Value is normal
07 Seek Error Rate 23 100 93 0 OK:
Value is normal
09 Power-On Time Count 1 61 61 25725 OK:
Value is normal
0A Spin Retry Count 0 100 100 0 OK:
Always passing
0B Calibration Retry Count 20 100 100 0 OK:
Value is normal
0C Power Cycle Count 8 99 99 732 OK:
Value is normal
0D Soft Read Error Rate 23 100 93 0 OK:
Value is normal
C2 Temperature 42 83 77 44 OK:
Value is normal
C3 Hardware ECC Recovered 0 100 31 2098888 OK:
Always passing
C4 Reallocation Event Count 20 100 100 0 OK:
Value is normal
C5 Current Pending Sector Count 20 100 100 0 OK:
Value is normal
C6 Off-Line Uncorrectable Sector Count 0 100 253 0 OK:
Always passing
C7 Ultra ATA CRC Error Rate 0 195 195 5 OK:
Always passing

[ HDS722580VLSA80 (VN6B7SCBE7XXPD) ]

01 Raw Read Error Rate 16 91 91 983078 OK:
Value is normal
02 Throughput Performance 50 118 118 414 OK:
Value is normal
03 Spin Up Time 24 112 112 11796654 OK:
Value is normal
04 Start/Stop Count 0 100 100 147 OK:
Always passing
05 Reallocated Sector Count 5 1 1 1883
Pre-Failure: Imminent loss of data is being predicted
07 Seek Error Rate 67 100 100 0 OK:
Value is normal
08 Seek Time Performance 20 136 136 31 OK:
Value is normal
09 Power-On Time Count 0 99 99 7404 OK:
Always passing
0A Spin Retry Count 60 100 100 0 OK:
Value is normal
0C Power Cycle Count 0 100 100 147 OK:
Always passing
C0 Power-Off Retract Count 50 100 100 430 OK:
Value is normal
C1 Load/Unload Cycle Count 50 100 100 430 OK:
Value is normal
C2 Temperature 0 183 183 23, 30 OK:
Always passing
C4 Reallocation Event Count 0 100 100 2341 OK:
Always passing
C5 Current Pending Sector Count 0 100 100 0 OK:
Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0 OK:
Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 7 OK:
Always passing

 

[Rod Speed]

The data itself looks fine.

Look like Everest is getting its tiny little brain rather scrambled
tho with the drives in RAID0. Same serial number is reported but
with two different reallocated sector counts for the same drive.

I'd image the total RAID0 'drive', break the raid, see what
the SMART data is like with the drives not in RAID anymore,
then restore RAID0 and restore the image.

Following is the full smart info. The drive in question is the 3rd
one, which is actually 2 SATA 80gb Hitachi drives on a Via m/b controller
setup as RAID0.
Here is info on the Hitachi followed by the SMART for all three. The 2
Hitachi drives are identical.

[ HDS722580VLSA80 (VN6B7SCBE7XXPD) ]

ATA Device Properties:
Model ID HDS722580VLSA80
Serial Number VN6B7SCBE7XXPD
Revision V32OA69A
Parameters 155010
cylinders, 16 heads, 63 sectors per track, 512 bytes per sector
LBA Sectors 156250000
Buffer 7938 KB (Dual
Ported, Read Ahead)
Multiple Sectors 16
ECC Bytes 4
Max. PIO Transfer Mode PIO 4
Max. UDMA Transfer Mode UDMA 5
(ATA-100) Active UDMA Transfer Mode UDMA
5 (ATA-100) Unformatted Capacity 76294
MB

--------[
SMART
]-------------------------------------------------------------------------------------------------------

[ Maxtor 6Y080P0 (Y25XADLE) ]

03 Spin Up Time 63 224 223 10235
OK: Value is normal
04 Start/Stop Count 0 253 253 336
OK: Always passing
05 Reallocated Sector Count 63 227 227 268
OK: Value is normal
06 Read Channel Margin 100 253 253 0
OK: Value is normal
07 Seek Error Rate 0 253 244 0
OK: Always passing
08 Seek Time Performance 187 252 243 38093
OK: Value is normal
09 Power-On Time Count 0 199 199 9283
OK: Always passing
0A Spin Retry Count 157 253 252 0
OK: Value is normal
0B Calibration Retry Count 223 253 252 0
OK: Value is normal
0C Power Cycle Count 0 253 253 363
OK: Always passing
C0 Power-Off Retract Count 0 253 253 0
OK: Always passing
C1 Load/Unload Cycle Count 0 253 253 0
OK: Always passing
C2 Temperature 0 253 253 40
OK: Always passing
C3 Hardware ECC Recovered 0 253 252 5349
OK: Always passing
C4 Reallocation Event Count 0 253 253 0
OK: Always passing
C5 Current Pending Sector Count 0 253 253 0
OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 253 253 0
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 199 199 0
OK: Always passing



[ MAXTOR 6L080L4 (664224152344) ]

01 Raw Read Error Rate 20 100 253 0
OK: Value is normal
03 Spin Up Time 20 69 64 3920
OK: Value is normal
04 Start/Stop Count 8 99 99 777
OK: Value is normal
05 Reallocated Sector Count 20 100 100 1
OK: Value is normal
07 Seek Error Rate 23 100 93 0
OK: Value is normal
09 Power-On Time Count 1 61 61 25725
OK: Value is normal
0A Spin Retry Count 0 100 100 0
OK: Always passing
0B Calibration Retry Count 20 100 100 0
OK: Value is normal
0C Power Cycle Count 8 99 99 732
OK: Value is normal
0D Soft Read Error Rate 23 100 93 0
OK: Value is normal
C2 Temperature 42 83 77 44
OK: Value is normal
C3 Hardware ECC Recovered 0 100 31 2098888
OK: Always passing
C4 Reallocation Event Count 20 100 100 0
OK: Value is normal
C5 Current Pending Sector Count 20 100 100 0
OK: Value is normal
C6 Off-Line Uncorrectable Sector Count 0 100 253 0
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 195 195 5
OK: Always passing

[ HDS722580VLSA80 (VN6B7SCBE7XXPD) ]

01 Raw Read Error Rate 16 91 91 983078
OK: Value is normal
02 Throughput Performance 50 118 118 414
OK: Value is normal
03 Spin Up Time 24 112 112 11796654
OK: Value is normal
04 Start/Stop Count 0 100 100 147
OK: Always passing
05 Reallocated Sector Count 5 1 1 1883
Pre-Failure: Imminent loss of data is being predicted
07 Seek Error Rate 67 100 100 0
OK: Value is normal
08 Seek Time Performance 20 136 136 31
OK: Value is normal
09 Power-On Time Count 0 99 99 7404
OK: Always passing
0A Spin Retry Count 60 100 100 0
OK: Value is normal
0C Power Cycle Count 0 100 100 147
OK: Always passing
C0 Power-Off Retract Count 50 100 100 430
OK: Value is normal
C1 Load/Unload Cycle Count 50 100 100 430
OK: Value is normal
C2 Temperature 0 183 183 23, 30
OK: Always passing
C4 Reallocation Event Count 0 100 100 2341
OK: Always passing
C5 Current Pending Sector Count 0 100 100 0
OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 7
OK: Always passing

What is the brand/model detail of the drives ?

Show the full SMART data for all drives, that may
have some extra useful info like the temperatures too.

----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure
Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World!
120,000+ Newsgroups ----= East and West-Coast Server Farms - Total
Privacy via Encryption =----

 

[Rod Speed]

Edited, I had a brain fart.

The data itself looks fine, the temps arent too bad.

I'd image the total RAID0 'drive', break the raid, see what
the SMART data is like with the drives not in RAID anymore,
then restore RAID0 and restore the image.

Following is the full smart info. The drive in question is the 3rd
one, which is actually 2 SATA 80gb Hitachi drives on a Via m/b controller
setup as RAID0.
Here is info on the Hitachi followed by the SMART for all three. The 2
Hitachi drives are identical.

[ HDS722580VLSA80 (VN6B7SCBE7XXPD) ]

ATA Device Properties:
Model ID HDS722580VLSA80
Serial Number VN6B7SCBE7XXPD
Revision V32OA69A
Parameters 155010
cylinders, 16 heads, 63 sectors per track, 512 bytes per sector
LBA Sectors 156250000
Buffer 7938 KB (Dual
Ported, Read Ahead)
Multiple Sectors 16
ECC Bytes 4
Max. PIO Transfer Mode PIO 4
Max. UDMA Transfer Mode UDMA 5
(ATA-100) Active UDMA Transfer Mode UDMA
5 (ATA-100) Unformatted Capacity 76294
MB

--------[
SMART
]-------------------------------------------------------------------------------------------------------

[ Maxtor 6Y080P0 (Y25XADLE) ]

03 Spin Up Time 63 224 223 10235
OK: Value is normal
04 Start/Stop Count 0 253 253 336
OK: Always passing
05 Reallocated Sector Count 63 227 227 268
OK: Value is normal
06 Read Channel Margin 100 253 253 0
OK: Value is normal
07 Seek Error Rate 0 253 244 0
OK: Always passing
08 Seek Time Performance 187 252 243 38093
OK: Value is normal
09 Power-On Time Count 0 199 199 9283
OK: Always passing
0A Spin Retry Count 157 253 252 0
OK: Value is normal
0B Calibration Retry Count 223 253 252 0
OK: Value is normal
0C Power Cycle Count 0 253 253 363
OK: Always passing
C0 Power-Off Retract Count 0 253 253 0
OK: Always passing
C1 Load/Unload Cycle Count 0 253 253 0
OK: Always passing
C2 Temperature 0 253 253 40
OK: Always passing
C3 Hardware ECC Recovered 0 253 252 5349
OK: Always passing
C4 Reallocation Event Count 0 253 253 0
OK: Always passing
C5 Current Pending Sector Count 0 253 253 0
OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 253 253 0
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 199 199 0
OK: Always passing



[ MAXTOR 6L080L4 (664224152344) ]

01 Raw Read Error Rate 20 100 253 0
OK: Value is normal
03 Spin Up Time 20 69 64 3920
OK: Value is normal
04 Start/Stop Count 8 99 99 777
OK: Value is normal
05 Reallocated Sector Count 20 100 100 1
OK: Value is normal
07 Seek Error Rate 23 100 93 0
OK: Value is normal
09 Power-On Time Count 1 61 61 25725
OK: Value is normal
0A Spin Retry Count 0 100 100 0
OK: Always passing
0B Calibration Retry Count 20 100 100 0
OK: Value is normal
0C Power Cycle Count 8 99 99 732
OK: Value is normal
0D Soft Read Error Rate 23 100 93 0
OK: Value is normal
C2 Temperature 42 83 77 44
OK: Value is normal
C3 Hardware ECC Recovered 0 100 31 2098888
OK: Always passing
C4 Reallocation Event Count 20 100 100 0
OK: Value is normal
C5 Current Pending Sector Count 20 100 100 0
OK: Value is normal
C6 Off-Line Uncorrectable Sector Count 0 100 253 0
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 195 195 5
OK: Always passing

[ HDS722580VLSA80 (VN6B7SCBE7XXPD) ]

01 Raw Read Error Rate 16 91 91 983078
OK: Value is normal
02 Throughput Performance 50 118 118 414
OK: Value is normal
03 Spin Up Time 24 112 112 11796654
OK: Value is normal
04 Start/Stop Count 0 100 100 147
OK: Always passing
05 Reallocated Sector Count 5 1 1 1883
Pre-Failure: Imminent loss of data is being predicted
07 Seek Error Rate 67 100 100 0
OK: Value is normal
08 Seek Time Performance 20 136 136 31
OK: Value is normal
09 Power-On Time Count 0 99 99 7404
OK: Always passing
0A Spin Retry Count 60 100 100 0
OK: Value is normal
0C Power Cycle Count 0 100 100 147
OK: Always passing
C0 Power-Off Retract Count 50 100 100 430
OK: Value is normal
C1 Load/Unload Cycle Count 50 100 100 430
OK: Value is normal
C2 Temperature 0 183 183 23, 30
OK: Always passing
C4 Reallocation Event Count 0 100 100 2341
OK: Always passing
C5 Current Pending Sector Count 0 100 100 0
OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 7
OK: Always passing

What is the brand/model detail of the drives ?

Show the full SMART data for all drives, that may
have some extra useful info like the temperatures too.

 

[Folkert Rienstra]

Its still very high for a good drive.

Something must have produced all those bads.

Yes, and likely it is a cause outside of the drives.

Not a clue, as always.

So I must be among peers.

[mindless repetition snipped]

It certainly indicates a problem somewhere.

And where exactly did I say that there isn't one?

Something upset the SMART system into thinking that the drives
are failing. When that happens to several drives it isn't likely
that the drives are actually failing and the numbers support that.

You just don't put several million spare sectors on a drive to
declare it failed already when only 1 permille are actually used.

Very bloody unlikely to produce that many bads.

Never said that, silly. If it's power failures causing the occasional blue
screen it's possibly the same powerfailures causing the bads. But you
are right, power failures won't usually result in relocates, just pending
bads. A more likely cause for relocates is high temperatures (overheating).

The Maxtor 6L080L4 is high in temperature and also seems to have fluctu-
ated in temperature according to SMART and it has a high ECC count too.
The other drives appear not to log the temperature extreme.

**** all in fact.

Must be easy to prove then. Put-up or shut-up, bitch.

And those that do flout the SMART standard.

That's even too silly to respond to.

But they shouldnt remove reallocated sectors, stupid.

Of course they should if they aren't bad at all under normal
operating conditions.

With some drives but not others.

[mindless repetition snipped]

Not with those absolute peanut numbers.

Not a clue, as always.

So I'm among my peers.

Something must have produced those very high numbers.

Sure. But it isn't the drive(s) failing.

Not what he asked.

As if it is entirely clear what exactly he asked, silly.

 

[Folkert Rienstra]

The data itself looks fine.

Actually, it looks supect.
Especially on the part of Raw Read Error Rate and Hardware ECC Recovered.

[rest of unreadable shit snipped]

 

[Colonel Blip]

Hello, Rod!
You wrote on Sat, 25 Feb 2006 09:32:45 +1100:

"break the raid" - can one simply disconnect one of the SATA drives and
reboot and the remaining drive show up as normal (assumes OS on different
drive altogether).

Thanks,

Colonel Blip.
E-mail: (e-mail address removed)


RS> Edited, I had a brain fart.

RS> The data itself looks fine, the temps arent too bad.

RS> I'd image the total RAID0 'drive', break the raid, see what
RS> the SMART data is like with the drives not in RAID anymore,
RS> then restore RAID0 and restore the image.

 

[Arno Wagner]

Hello, Rod!
You wrote on Sat, 25 Feb 2006 09:32:45 +1100:

"break the raid" - can one simply disconnect one of the SATA drives and
reboot and the remaining drive show up as normal (assumes OS on different
drive altogether).

You should. That is the point of RAID1, after all. If this does not
wotk, you should throw away the controller and get one that works.

And this should still work with the OS on the RAID array as well.
The only possible problem I see with OS on the array is that if
you remove one drive from the RAID and connect it to a regular
controller, your BIOS could decide to boot from the single
drive instead of from the (degraded, but functionsl) RAID array.

Arno

 

[Arno Wagner]

Following is the full smart info. The drive in question is the 3rd one,
which is actually 2 SATA 80gb Hitachi drives on a Via m/b controller setup
as RAID0.
Here is info on the Hitachi followed by the SMART for all three. The 2
Hitachi drives are identical.

[...]

The key line is this one here:

05 Reallocated Sector Count 5 1 1 1883
Pre-Failure: Imminent loss of data is being predicted

You should take the comment literally, until you can confirm otherwise.
If you have no backup yet, that should be your first priority.

Arno

 

[Rod Speed]

Yes, and likely it is a cause outside of the drives.

Maybe. All we really know for sure is that two of the four drives
have a large number of reallocated sectors. That could just be
two drives going bad and that has happened over time and hasnt
been noticed until now, just due to running them much too hot.

We dont even know for sure that there are two drives with that
may reallocated sectors either, the Everest report on the drive
in the RAID0 may be completely misleading etc.

So I must be among peers.

Never ever could bullshit its way out of a wet paper bag.

[mindless repetition snipped]

Never ever could bullshit its way out of a wet paper bag.

And where exactly did I say that there isn't one?

The peanuts comment, you pathetic excuse for a bullshit artist.

Something upset the SMART system into thinking that
the drives are failing. When that happens to several
drives it isn't likely that the drives are actually failing

Wrong if its just two drives out of 4 that are claimed to be failing.

and the numbers support that.

No they dont. You dont see anything like as high reallocated
sector numbers as that without something producing them.

You just don't put several million spare sectors on a drive

Neither of those drives has that many spares.

to declare it failed already when only 1 permille are actually used.

Something is producing all those bads, stupid.

Never said that, silly.

Corse you did, ****wit.

If it's power failures causing the occasional blue screen
it's possibly the same powerfailures causing the bads.

Very unlikely.

But you are right, power failures won't usually result
in relocates, just pending bads. A more likely cause
for relocates is high temperatures (overheating).

The Maxtor 6L080L4 is high in temperature

Those usually are, they need good cooling.

and also seems to have fluctuated
in temperature according to SMART

It'd be more surprising if it didnt with high temps and winter currently.

and it has a high ECC count too.

Not that high for that drive.

The other drives appear not to log the temperature extreme.

Yes, most dont.

Must be easy to prove then. Put-up or shut-up, bitch.

Go and **** yourself, ****wit.

YOU made the claim.

YOU get to do the proving.

THATS how it works.

That's even too silly to respond to.

Never ever could bullshit its way out of a wet paper bag.

Of course they should if they aren't bad
at all under normal operating conditions.

Nothing like your mindless pig ignorant silly stuff about
'so that Logical Block Addresses are sequential again'

[mindless repetition snipped]

Never ever could bullshit its way out of a wet paper bag.

[mindless repetition snipped]

Sure. But it isn't the drive(s) failing.

You dont know that yet if its only 2 out of 4.

As if it is entirely clear what exactly he asked, silly.

Never ever could bullshit its way out of a wet paper bag.

 

[Rod Speed]

Actually, it looks supect.

No it doesnt.

Especially on the part of Raw Read Error Rate
and Hardware ECC Recovered.

Not at all unusual with some manufacturer's drives that are fine and thats
only seen with the one drive with only a single reallocated sector too.

[your pathetic excuse for bullshit flushed where it belongs]