SMART Status Thumbs Down

[ruthlessone]

Any ideas?

 

ID#	ATTRIBUTE NAME	FLAG	VALUE	WORST	THRESH	TYPE	UPDATED	FAILED	RAW VALUE
1	Raw Read Error Rate	0x002f	197	197	051	Pre-fail	Always	Never	153335
3	Spin Up Time	0x0027	149	140	021	Pre-fail	Always	Never	9525
4	Start Stop Count	0x0032	094	094	000	Old age	Always	Never	6387
5	Reallocated Sector Ct	0x0033	182	182	140	Pre-fail	Always	Never	260
7	Seek Error Rate	0x002e	200	200	000	Old age	Always	Never	0
9	Power On Hours	0x0032	059	059	000	Old age	Always	Never	30008
10	Spin Retry Count	0x0032	100	100	000	Old age	Always	Never	0
11	Calibration Retry Count	0x0032	100	100	000	Old age	Always	Never	0
12	Power Cycle Count	0x0032	100	100	000	Old age	Always	Never	281
192	Power-Off Retract Count	0x0032	200	200	000	Old age	Always	Never	130
193	Load Cycle Count	0x0032	164	164	000	Old age	Always	Never	110830
194	Temperature Celsius	0x0022	117	098	000	Old age	Always	Never	35
196	Reallocated Event Count	0x0032	001	001	000	Old age	Always	Never	200
197	Current Pending Sector	0x0032	199	066	000	Old age	Always	Never	547
198	Offline Uncorrectable	0x0030	199	199	000	Old age	Offline	Never	651
199	UDMA CRC Error Count	0x0032	200	200	000	Old age	Always	Never	0
200	Multi Zone Error Rate	0x0008	186	134	000	Old age	Offline	Never	4225

[JonathanM]

Any ideas?

Replace the drive?

[trurl]

Not even a borderline case. Replace.

[ruthlessone]

Now its back to green thumbs up? New drives ordered...

 

But whats it doing?

[JonathanM]

Now its back to green thumbs up? New drives ordered...

 

But whats it doing?

It's in the process of failing. Sometimes death is quick and painless, sometimes the struggle is long.

[bonienl]

Now its back to green thumbs up? New drives ordered...

 

But whats it doing?

 

What you are seeing is expected behavior.

 

It turns red upon reboot and the number of re-allocated sectors is greater than zero, this will be reset to green after a minute. From this point on it will become red again if the number of re-allocated sectors starts to climb (and notifications will be given).

 

[trurl]

The current pending sectors and offline uncorrectable are the really worrisome numbers here. Definitely replace.

[ruthlessone]

Should I run a parity check before I replace? Like while I am preclearing?

[TSM]

Should I run a parity check before I replace? Like while I am preclearing?

Personally I wouldn't because I'd be afraid the drive would fail during the parity check.  And if my understanding of the process is correct, depending on how the drive fails you could be in a worse state than you are right now.  And I guess it would depend on whether the check was correcting or non-correcting.  But others here might have a more educated and intelligible reason for doing it or not doing it.  And I could be wrong...

[dgaschk]

Should I run a parity check before I replace? Like while I am preclearing?

 

No. Checks must be done prior to any failure indication. Hopefully your prescience allowed you to do a check just before the problem started. A check now could corrupt parity and make recovery impossible.