When you went to step #3 in the first drive replacement process Boot up the server and acknowledge errors about failed drives, did you DELETE the removed array/logical drive or just mark it as failed? That's probably the source of the problem here. The removed drives still have the RAID metadata on them. Their recommendation was to recreate the RAID array and restore the data, but that doesn't really help my situation. I have already contacted HP support, and they were unable to help. Is there anything I can do to access the data on the old drives? If not, which RAID controllers support this, so I know what to buy in the future?

I can hardly believe that the drives would be rendered inaccessible as soon as they are removed from the original RAID controller. I had assumed that the RAID metadata stored on the disks would be sufficient to bring the old RAID array back online, but that doesn't seem to be the case. Then turn system power OFF and move drives to their original positions. Run Array Diagnostics Utility (ADU) if previous positions are unknown. Insert old drives according to position labels.Īt this point, I get the following error: 1785-Slot 0 Drive Array Not Configured.But some data was missed in the last backup, so I need to recover data from the drives in the original array. Format new array and restore data from tape backup.Insert new drives and create new RAID10 array.Boot up the server and acknowledge errors about failed drives.

Remove drives used in data array and hot spare, and label with their positions.The old drives would be untouched in case any recovery was needed. The plan was to replace the RAID5 array and hot spare with a RAID10 array composed of much larger disks. This server (our file server) needed an upgrade. The RAID controller is refusing to recognize inserted drives as an array. I have an HP ProLiant DL180 G5 server with a Smart Array E200 RAID controller.

Hp smart array p410i controller manual