how to replace the failedset in esa12k

[Rambo_1]

A failedset DISK30300 in esa12k Array.
SPARESET spareset

FAILEDSET failedset DISK30300
Switches:
NOAUTOSPARE
esa12k_down>show devices full
...
DISK30200 disk 3 2 0 R3
COMPAQ BD009122C6 B016
Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = 20MHZ (synchronous 20.00 MHZ negotiated)
Size: 17769177 blocks
DISK30300 disk 3 3 0 FAILEDSET
Misconfigured: No device at this PTL, please see product documentation
DISK30800 disk 3 8 0 R5
COMPAQ BD036659CC 3B00
Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = 20MHZ (synchronous 20.00 MHZ negotiated)
Size: 71109623 blocks
Configuration being backed up on this container

who can tell me how to replace the failedset
disk30300 ?
I think the disk30300 belonged to R4
R4 raidset DISK10300 D110
DISK20300
DISK40300
DISK41000
DISK50300
DISK60900
Switches:
POLICY (for replacement) = BEST_PERFORMANCE
RECONSTRUCT (priority) = NORMAL
CHUNKSIZE = 256 blocks
State:
NORMAL
DISK10300 (member 0) is NORMAL
DISK20300 (member 1) is NORMAL
DISK41000 (member 2) is NORMAL
DISK40300 (member 3) is NORMAL
DISK50300 (member 4) is NORMAL
DISK60900 (member 5) is NORMAL
Size: 177713525 blocks


Thanks
Rambo

[Hein van den Heuvel · Accepted solution]

Did you check your documentation?
THis is all well described.

I agree with you that disk30300 probably was member 2 in R4.

Upon failure it was put in the 'failedset' and was automatically replaced by DISK41000 which must have been in the 'spareset'.

You need to decide whether disk30300 is really bad (error logs?) or whether it was just bad luck. Assuming it was really bad, toss it out and stick a fresh disk in its slot. Now add that new disk to the spareset and you are protected again.

hth.
Hein.

[Rambo_1]

Thanks a lot .

[Frank Gessner]

The disatvantage of leaving it as it is could be the failure of shelf 4 with now two
R5-Members in it. The data would be lost.
Therefore I recommend to rebuild the original Configuration after repair/verify of
disk30300.

regards, Frank