E-Series Data Loss

[#1]

Twice in the last nine months we have had a drive failure followed by significant data loss. Event type is 2046 Isolation of drive causing redundancy mismatch. Tough to lose TB of data and multiple machines running under VMware. Anyone experience this?

[#2]

Hi,

I did a search and found this for you:

https://kb.netapp.com/support/s/article/ka21A0000000jL7/what-does-isolation-of-drive-causing-redundancy-mismatch-mean

https://kb.netapp.com/support/index?page=content&id=2025182

Also I found a related support case for this issue and the solution was in the above KB (to perform a parity scan and repair on the volume)

/Matt

[#3]

Thanks but I can get to the first article but not the second.

[#4]

Hi,

Here is the external link:

https://kb.netapp.com/support/s/article/ka11A0000001aGz/isolation-of-drive-causes-redundancy-mismatch

If you are unable to access the above URL, whilst the KB article does provide technical detail on how to identify the volume requiring a parity scan and perform a repair based on the raw data in the logs, it also contains the following statement:

"WARNING: Isolation of drive causing redundancy mismatch does involve data integrity and any actions should take place under the guidance of NetApp Support. If there are any uncertainties or unexpected results, please engage appropriate resources."

Therefore I'd advise opening a support case as the appropriate course of action.

/Matt