IBM V7000 drive replacements and forcing copy-back

Very good post by Robert (thank you) on V7000 drive replacements. While you’re at it don’t forget to follow Robert on Twitter @UltraSub

We’re running some V7000′s for some time now, and I’ve seen different results when a drive fails and gets replaced. A few scenario’s I’ve seen:

  • After replacing a drive, it’s automatically added back into the array, and a copyback from spare is started.
  • After replacing a drive, the new drive isn’t seen without running the wizard (or intervening with CLI), after intervention the new drive is added back into the array, and a copyback from spare is started.
  • After replacing a drive, the new drive isn’t seen, and the wizard also doesn’t recognize it, and asks you if you want to add the in use spare permanently to the array, or pick another drive (and you can not pick the new drive you just put in, because it isn’t recognized).

Why I’ve seen different things I haven’t found out yet. All I know is that IBM support has “a fix” for the third scenario, and I don’t like it, since it just adds the spare back into the array, and puts the replacement drive into candidate mode. According to IBM support, this is by design. Of course, it works, but if you have a strict drive/array layout like we do, you won’t like this result. We script our V7000 installs, and want drive and array layout to stay the same.

Read on here

Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s