Not sure if this will accomplish your objective but you can proactively hot spare a disk drive via the UI or a Secure CLI command. This causes Flare to copy the contents of the drive to a hot spare and then mark the drive as faulted. You would then have to remove and re-insert the "faulted" drive to have the data copied back.

*lol* Since this is a remote site for him and he doesn't have anyone to pull the drive in the first place, this might not be the best solution.

Mind you, I don't have a better answer other than "Road Trip"!!!

found the command to switch a drive off
:-
Navicli ¿h cru_on_off ¿'engineering password' 0_0_4 state



Where 0_0_4 - slot 4 of bus 0 enclosure 0



State - 0 ¿ power off

1 ¿ Power on

The cur_on_off command is an engineering command and can be VERY dangerous to use - use at your own risk! It is not intending for testing.

regards,

glen kelley

I'll bear it in mind Have trie dit today an don eting I noticed, when I failed a disk, the hot spar edidn't kick in, is this normal ? ( we're on falre 24 and 8 disk raid 10 groups)

To me this is normal, as you have administratively powered down the disk - it is not a disk failure - so Hot spare will not be kicked in.

Any different ideas?
Thanks,
Sandip

Note - that's why this command is so dangerous and not to be used at field.

Message was edited by: added note. Sandip

Raid 10 is stripped mirror, when a disk fails the mirror takes over. On a Raid 5 (parity) when a disk fails, the hot spare kicks in.

When you use the cur_on_off, you turn off the disk in the SP side that you sent the command to.

Issue:

navicli -h IP_address_SPx getdisk X_X_X -state

This will tell you the state of the disk on the SPx side.

regards,

glen kelley

Just a follow up.

If want the hot spare to kick in, you need to issue the cru_on_off to both SPA and SPB. Use a Raid 5 LUN to test against and remember the caution about using this command.

regards,

glen