topic Re: Parity Initialization Progress - CLI Created Logical Volume in ProLiant Servers (ML,DL,SL)

Parity Initialization Progress - CLI Created Logical Volume

pronto — Tue, 03 Dec 2019 16:18:16 GMT

Servus Community,

Yesterday we created a new logical volume in the Command Line Interface with the following command:

/opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=0 create type=ld drives=1I:1:17,1I:1:18,1I:1:19,1I:1:20,1I:1:21,1I:1:22,1I:1:23 raid=6

The volume was immediately visible in the web GUI of our ESX 6.5 and we were able to create a new data store there. This is also usable and we already install some VMDKs there.

What we don't know is the status of the Parity Initialization Progress display, which is still at 0%. For another volume, which already existed and was not created with the CLI, but in the controller BIOS, it will be displayed there: Initialization Completed:

For the new, CLI created volume we got this output:

---snip---

/opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=0 ld 2 show

Smart Array P440ar in Slot 0 (Embedded)

Array B

Logical Drive: 2

Size: 5.46 TB

Fault Tolerance: 6

Heads: 255

Sectors Per Track: 32

Cylinders: 65535

Strip Size: 256 KB

Full Stripe Size: 1280 KB

Status: OK

Unrecoverable Media Errors: None

MultiDomain Status: OK

Caching: Enabled

Parity Initialization Status: In Progress

Parity Initialization Progress: 0% complete

Unique Identifier: 600508B1001C4828A9D9A8C1870E0F8A

Logical Drive Label: 06C4F007PDNLH0BRH78D1217CE

Drive Type: Data

LD Acceleration Method: Controller Cache

---snap---

And for the existing, controller BIOS created Volume, we got this output:

---snip---

[root@localhost:/opt/smartstorageadmin/ssacli/bin] ./ssacli ctrl slot=0 ld 1 show

Smart Array P440ar in Slot 0 (Embedded)

Array A

Logical Drive: 1

Size: 6.55 TB

Fault Tolerance: 6

Heads: 255

Sectors Per Track: 32

Cylinders: 65535

Strip Size: 256 KB

Full Stripe Size: 1536 KB

Status: OK

Unrecoverable Media Errors: None

MultiDomain Status: OK

Caching: Enabled

Parity Initialization Status: Initialization Completed

Unique Identifier: 600508B1001C0FC35B29727B79F53993

Logical Drive Label: 01B0CE71PDNLH0BRH78D12FD28

Drive Type: Data

LD Acceleration Method: Controller Cache

---snap---

We assume that the output 0% is incorrect, but it would be interesting what we have to do, to update it, to the current correct value...

Thx & Bye Tom

Re: Parity Initialization Progress - CLI Created Logical Volume

Pra_Sah — Tue, 10 Dec 2019 09:27:33 GMT

Hello Pronto,

Thank you for your query.

RAID 6 by design takes maximum time to initialize the parity as it is a Dual parity RAID. So in case if the HPE SSA CLI is showing
Parity Initialization Status: In Progress

Parity Initialization Progress: 0% complete

Then it means that pariy initialization is not completed.

So in order to check the exact status of the Parity initialization we will need logs from the server so that we can check background Data of the controller.

Please log a Support Ticket with HPE Technical Team, so that we can check the logs and update you the exact status.

Regards,

Re: Parity Initialization Progress - CLI Created Logical Volume

pronto — Tue, 10 Dec 2019 09:36:06 GMT

Servus Pra_Sah,

which logfile do you need exactly?

Thx & Bye Tom

Re: Parity Initialization Progress - CLI Created Logical Volume

BOYAN BIANDOV — Fri, 27 Dec 2019 18:39:00 GMT

Although I am on a different OS than you what I can share is that following a drive replacement I was stuck at 0% for over 24 hours and I saw that as an anomaly. I opened a case with HPE.

Support suggested to change the surface scan analysis to HIGH and after doing that I immediately saw change from 0% to 1% until completion within 8 hours from making the change: