Hello,

 

my dashboard is showing for my parity disk. I guess this is mainly due to "Reallocated sector count" attribute.  At the very bottom SMART overall-health is marked as: Passed.

 

Should I be worried - change the parity drive?

 

1	Raw read error rate	0x000f	116	081	006	Pre-fail	Always	Never	103825504
3	Spin up time	0x0003	094	094	000	Pre-fail	Always	Never	0
4	Start stop count	0x0032	100	100	020	Old age	Always	Never	850
5	Reallocated sector count	0x0033	100	100	010	Pre-fail	Always	Never	24
7	Seek error rate	0x000f	069	060	030	Pre-fail	Always	Never	10356125
9	Power on hours	0x0032	066	066	000	Old age	Always	Never	30249 (3y, 5m, 11d, 9h)
10	Spin retry count	0x0013	100	100	097	Pre-fail	Always	Never	0
12	Power cycle count	0x0032	100	100	020	Old age	Always	Never	50
183	Runtime bad block	0x0032	100	100	000	Old age	Always	Never	0
184	End-to-end error	0x0032	100	100	099	Old age	Always	Never	0
187	Reported uncorrect	0x0032	001	001	000	Old age	Always	Never	438
188	Command timeout	0x0032	100	096	000	Old age	Always	Never	1 2 11
189	High fly writes	0x003a	097	097	000	Old age	Always	Never	3
190	Airflow temperature cel	0x0022	063	049	045	Old age	Always	Never	37 (min/max 31/44)
191	G-sense error rate	0x0032	100	100	000	Old age	Always	Never	0
192	Power-off retract count	0x0032	100	100	000	Old age	Always	Never	44
193	Load cycle count	0x0032	001	001	000	Old age	Always	Never	207968
194	Temperature celsius	0x0022	037	051	000	Old age	Always	Never	37 (0 20 0 0 0)
197	Current pending sector	0x0012	100	038	000	Old age	Always	Never	0
198	Offline uncorrectable	0x0010	100	038	000	Old age	Offline	Never	0
199	UDMA CRC error count	0x003e	200	200	000	Old age	Always	Never	0
240	Head flying hours	0x0000	100	253	000	Old age	Offline	Never	4309h+06m+38.978s
241	Total lbas written	0x0000	100	253	000	Old age	Offline	Never	18412959336
242	Total lbas read	0x0000	100	253	000	Old age	Offline	Never	51929103162

Thank you.

Edited November 23, 20178 yr by coolpoint

Some reallocated sectors can be OK, though never a good sign, if they keep climbing consider replacing the disk, also running an extended SMART test is a good idea.