3.627 bytes

Service Hints & Tips

Document ID: DDSE-3QQJ6Z

This document is provided to IBM and our Business Partners to help sell and/or service IBM products. It is not to be distributed beyond that audience or used for any other purpose.

Servers - ServeRAID rebuild issue with drive failures on multiple arrays

Applicable to: World-Wide

The problem is regarding a Hot Spare rebuild is as follows:
There are at least two separate arrays defined, each having its own hot spare drive defined. On first array, a drive goes bad (simulated or real), ServeRAID adapter detects that drive has gone bad, automatically substitutes the hot spare into the first array and starts rebuilding.

While first array is being rebuilt, another drive in second array goes bad (simulated or real). Everything continues fine, defective drive in second array is identified. First array rebuilds successfully. Since rebuild engine in firmware is event driven, rebuild engine is not aware of second array having a defective drive while first array is being rebuilt. As a result, once first array is successfully rebuilt, rebuilding of second array does not start automatically.

ServeRAID identifies defunct drive in second array. But, the rebuild has to be started manually from the ServeRAID GUI, it is not done automatically.

Solution:
Development has implemented a Daemon software in firmware which regularly checks for any drive that has gone defunct. If drive has gone defunct, it starts rebuild process. Therefore, in the above example, second array will start rebuilding upon completion of first array rebuild process automatically. If system had any more arrays defined and they had any drives go defunct, they would rebuilt sequentially. This will be implemented in the next firmware releases for original ServeRAID and for the ServeRAID refresh.

Search Keywords

Hint Category

Hard Drives, RAID

Date Created

14-01-98

Last Updated

11-02-99

Revision Date

11-02-2000

Brand

IBM PC Server

Product Family

ServeRAID, Servers

Machine Type

Various

Model

TypeModel

Retain Tip (if applicable)

Reverse Doclinks
and Admin Purposes