- Urgent
After 2 drives dropped offline, a segfault occured in emhttpd which resulted in inaccurate health and status displays on the dashboard, and aslo the nightly health report email to erroneously report that the array was healthy. No indication from the server that anything was wrong, save for the entries in the syslog which I happened to read by chance.
When this happened back on 6.11.1 during a parity re-build, the correct FAIL email was sent so I'm not sure if this is specific to 6.12.3