topic Re: Parity Initialization Status in ProLiant Servers (ML,DL,SL)

Parity Initialization Status

AssureWeb_MW — Mon, 31 Oct 2011 08:50:11 GMT

We have a smart array 5i in embedded slot running from a DL380 G2 to a disk sub system (Old I know) configured as a 450 GB raid 5 array the server went down over the weekend for some unknow reason and the controller disabled the logical drive due to errors, we dont have much hope for the data but started an Initialization on the logical drive as the array config utility can still see them in the hope we may be able to recover something, problem is the has now been running for about 72 hours. Does anyone know how long this could pottentially take?

Thanks

Re: Parity Initialization Status

John Kufrovich — Mon, 31 Oct 2011 12:21:40 GMT

The 5i is an embedded SCSI. The largest SCSI drive I recall HP delivering was a 300GB. I doubt the smart array card firmware knows how to handle the extra blocks.

Re: Parity Initialization Status

John Kufrovich — Mon, 31 Oct 2011 12:26:21 GMT

Never mind, you said, 450GB Raid 5 LUN. Not enough coffee.

If you are doing a inititialization again? You deleted the LUN? If you deleted the LUN, the LUN device ID changed, the HOST will see it as a different volume.

Re: Parity Initialization Status

AssureWeb_MW — Mon, 31 Oct 2011 12:52:06 GMT

We didnt delete the LUN when the server came back up we had the option to re enable the disabled logical drive to recover some data which forced the array to initialize, its been stuck here since.

Re: Parity Initialization Status

John Kufrovich — Mon, 07 Nov 2011 12:29:20 GMT

It sounds like the Raidset has hit a URE, unrecoverable read error on one of the members. This will cause the init to stop. You could look at a ADU report and look at the Hard Read Errors, since reset for each member. But in the end, I think you will have backup data, delete the volume and replace a few drives. And recreate everything.