topic Re: Error message Parity Initialization in StoreVirtual Storage

Error message Parity Initialization

Harrygg — Mon, 08 Aug 2022 14:18:41 GMT

Hi everyone

I am getting The 'Data Array 1' Parity Initialization Status is 'Failed'.

however all the disks look ok and this is sometimes there and then not the next.

How can I trace the cause ?

thanks in advance

regards

Harry

Re: Error message Parity Initialization

sbhat09 — Mon, 01 Aug 2022 04:49:32 GMT

Hello @Harrygg,

Can you please provide some more details like what is the StoreVirtual model? If it is VSA, what is the hardware it is installed on? Number of disks, RAID configuration etc?

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.

Re: Error message Parity Initialization

Harrygg — Mon, 01 Aug 2022 12:29:21 GMT

So I have a pair of 4335 units. there are 2 raid5 arrys 3xssd and 5x hdd

Software level is currently 12.6.00.0155.0

Re: Error message Parity Initialization

Harrygg — Mon, 01 Aug 2022 12:30:41 GMT

How do I post a image with all info . in it ?

Re: Error message Parity Initialization

sbhat09 — Mon, 01 Aug 2022 12:39:58 GMT

Hello @Harrygg,

To post the image, click on the 'camera' icon while drafting your post -> choose file -> open -> wait for the image load -> done.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.

Re: Error message Parity Initialization

Harrygg — Mon, 01 Aug 2022 12:43:05 GMT

I think I have gather evrything

error message

raid config

disk config

system details

Re: Error message Parity Initialization

Rachna-K — Tue, 02 Aug 2022 12:29:23 GMT

@Harrygg

Thank you for sharing the details.

Parity Initialization could fail due to one or more of the below reasons.

1. Faulty Hard Drive/s

2. Drive Media Errors

3. Old Firmware of Controller or Drives

This would need an in depth analysis of the Logs to identify the source of the cause. Once we have resolved these issues we might have to put the Node in Repair Mode and Reconfigure the RAID to recover completely from this Error. Hence, request you to log a Support Ticket for further assistance.