SMART errors on EDA500 not reported in log

Question

I have two EDA500's attached to my RN516. Current firmware is 6.9.2, but this has apparently been going on in 6.7.5 and 6.8.1 before it (I skipped everything else in between).

I have two drives with increasing SMART errors in one of the EDAs, and there is not one word about it in the main log. One has 153 reallocated sectors and 4 pending sectors and the other 41 reallocated sectors. smart_history.log shows these have been creeping up for months. They were not new when I put them in, and they have 64k and 25k hours respectively, so maybe that's to be expected at least on the one, but I also expect for the log to warn me about this. I only noticed this because the volume scrub locked up and the subsequent re-boot resulted in the volume being out of sync. I looked at the SMART stats to see if there was a clue there and, sure enough, it looks like one or both of those drives could be the culpret..

Note that I do not have an email address entered in the NAS, so I get no email notifications. But I really don't think that should matter. There are no SMART errors on the drives in the 516 itself or the other EDA, so I don't know if log entries would be made for those or not.

Is there a bug, or is it just the way it is that these errors on an EDA500 go unreported? If it's intentional, it needs to be re-thought.

mdgm-ntgr · Answer

We don't send out email alerts for every change. If we did there'd be a flood of alerts.

Sandshark · Answer

I expect a log entry (and am pretty sure I've gotten them on units w/o EDA500) for that many reallocated sectors.&nbsp; I'm not talking about email alerts, I don't have them configured..&nbsp;&nbsp;

mdgm-ntgr · Answer

To get an alert for reallocated sectors one of the following conditions must be met:
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * - 50 reallocated sectors AND power-on hours &lt;= 24
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * - Reallocated sector count increasing at least 10 times in the past 30 days
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp; AND reallocated sector count &gt; 500
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * - Reallocated sector count &gt; 1500

StephenB · Answer

mdgm-ntgr wrote:
To get an alert for reallocated sectors one of the following conditions must be met:
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * - 50 reallocated sectors AND power-on hours &lt;= 24
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * - Reallocated sector count increasing at least 10 times in the past 30 day AND reallocated sector count &gt; 500
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * - Reallocated sector count &gt; 1500

In my opinion these conditions are far too lax.&nbsp; I much prefered the alert policies in OS 4.&nbsp; It's one reason I'm presently keeping my Pro-6 backup NAS running OS 4.2.
&nbsp;
I replace disks when the reallocated+pending sector count exceed 50, and this alert policy forces me to look for at these stats manually instead of depending on the alerts.
&nbsp;
In general, policies on when disks should be taken out of service vary considerably - there is no well-established best-practice.&nbsp; Netgear should provide alerts that can fit a range of policies, and clearly you aren't.&nbsp; &nbsp;And this isn't a small matter - keeping your disks healthy is a critical aspect in managing a RAID array.

mdgm-ntgr · Answer

Custom thresholds for alerts would be a good suggestion for the Idea Exchange.

Forum Discussion

SMART errors on EDA500 not reported in log

8 Replies

Related Content

Bug Report: Orbi App Timed out

What to Include When Reporting an Issue

RN204 and the EDA500

EDA500 Status Lights

EDA500 and UPS

NETGEAR Academy

ProSupport for Business