hp smart array p410i code 785

Hi,

This may or may not be an error. It is simply telling you that the RAID array is being rebuilt in the background (because you replaced a drive).
It may be a problem if it is still running after a week etc. The rebuild time will depend on many things, CPU speed, disk size, disk speed, disk cache, system activity, disk activity - so I can't really tell you how long it will take.

One thing that I have heard can prevent this message from being cleared (because it never completes) is if the system is playing host to VMWare VM's (not sure if limited to VMWare). Apparently stopping the VM's for a few hours usually gives the rebuild time to finalise.

Hope this helps
COlin

Hi,

Thanks for your reply, Its been more than a week.

I am seeing one more actional task.

Logical Drive 2 is undergoing parity initialization"

More than a week does sound a tad excessive.
What is the server used for? Does it host any VM's?
Could you give us a clue on the CPU speed & Disk size?

Colin

Server : HP proliant DL 380 G7
              Xeon E6520 2.4G
               P410I Smart Array
                Windows 2008 r2 64bit  
               2*300 SAS Raid 1   (Bay 1-2)
               6*500 SAS  Raid 5  (bay  3-8)

Bay 3 drive failed and replaced.

before replacing total drive was missing and not showing in Disk Management.

After replacing, showing as raw drive and asking to format.... left for 3 days to sync, so I tried interchanging bay 3 and 4 and kept as it it..

is interchanging bays make any difference?

Thanks

Sreekanth

Unfortunately the problem maybe related to moving bays. I see you have 5 drives in the raid5 array. Is that including 1 hot spare?
Some raid software treats a bay move as a drive replacement and will rebuild the contents. If you moved the drive to another bay while the system was already busy rebuilding the previous failure then it could well lead to data loss.

380 G7 is reasonably old, the 410 controller isn't overly fast and it isn't a full hardware raid (still HBA) and the disks in the RAID5 array sound like Ent SATA not SAS (unless I'm wrong I don't think you can get 500GB SAS, usually 600GB SAS and 500GB Ent SATA) and if they are Ent SATA then they could well be 7.2Krpm drives. Add all this together and the rebuild will take a long time.

Does the Raid card think it's busy? ie: Status shown as rebuilding, or during reboot does it say syncing etc? If it does then it probably is just very slow. Does the server host VM's? If so could you shut them down for a week?

Colin


Regards
Colin

Hi,

Its a ADS and file server and there are no VM's

controller interface shows them as SAS 500GB and showing 6*500 SAS drives. please see the screen shots...

Thanks

Sreekanth
Screen-Shot-07-14-17-at-04.35-PM-001.PNG
Screen-Shot-07-14-17-at-04.35-PM.PNG
Screen-Shot-07-14-17-at-04.34-PM.PNG
Screen-Shot-07-14-17-at-04.33-PM.PNG

The ss at the bottom is useful - but unfortunately you selected the working array.
Could you select the problematic array and resend?

Colin

Bay 3 is the replaced disk

Thanks

Sreekanth
Screen-Shot-07-14-17-at-04.33-PM.PNG
Screen-Shot-07-14-17-at-04.50-PM.PNG

I can't see any errors reported on those screens.
According to the controller the 2nd array is OK.
What/where are you getting errors reported?

Colin

I am not getting any errors...but the D Drive is showing as Raw disk and asking to format...

after a week also the data is not showing up....

Thanks

Sreekanth
Screen-Shot-07-14-17-at-04.59-PM.PNG

Thanks for the details Sreekanth.
I'd take a wild guess that the data is lost.
The bay the drive is in is very important to the controller and the combination of a drive failure & moving another drive around has most likely caused data loss. The array is working correctly and is ready to be used.
I'd suggest pulling the data back from back-up and re-populating the array.

If there was no hot spare as soon as the 1st drive failed the array was no longer fault tolerant and then the task of swapping bays made a 2nd failure and hence loss of data. The replaced drive was probably waiting to be added into the array to get it back to fault tolerant.

I don't think there is much that can be done now, a forensic recovery maybe able to help but it will be very time consuming and expensive.
Do you have a backup?


Colin

Hi,

at present all the 6 disks in logical drive are showing blue LED,

What does that mean,,,is this rebuilding data?

Thanks

Sreekanth

From memory the DL380 shows Blue when fitted with a suitable HDD, but best check the user guide.

The status both arrays is OK and there are no notifications attached to either array.
The array is not rebuilding. It has initialised a new array.

The data is lost. Do you have a backup?

Colin

If you upload an ADU report I will read through it to see what happened but it does seem the data is lost. You should not get "785 Background parity initialization..." unless you deleted the array and created another one. If you upload an ADU report I may be able to tell more, you can get that from the array diagnostic utility or some versions of the ACU.

The drives are showing blue because you have the array highlighted in the ACU.