Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

add spare unit=# disk### -> "Volume # is on the same array, but is not ready for this operation!"

Gunther S.
Occasional Advisor

add spare unit=# disk### -> "Volume # is on the same array, but is not ready for this operation!"

Hi, recovering from a power outage based problem. One disk has disappeared from a RAID1 volume. Status is:

Unit 6:
In PDLA mode, Unit 6 is Lun 7; In VSA mode, Unit 6 is Lun 6.
Unit Identifier :
Device Identifier : 600508B3-0091FB70-A390D1BC-256E0017
Preferred Path : Controller 2 (other controller)
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME USING REGENERATE
Mirror Init Status: Complete
2 Data Disk(s) used by lun 6:
Disk209: Box 2, Bay 09, (B:T:L 1:10:00)
Disk210: Box 2, Bay 10, (B:T:L 1:11:00) DRIVE FAILED! (0x0C)
Spare Disk(s) used by lun 6:
No spare drive is designated.
Logical Volume Raid Level: MIRROR FAULT TOLERANCE (RAID 1)
stripe_size=8kB
Logical Volume Capacity : 69,460MB

This is explained in the manual as a unit where one disk has failed and there is no spare. So, I wanted to assign a spare now to pull it out of a vulnerable phase. Here is the dialog:

CLI-1> add spare unit=6 disk414
Volume 6 is on the same array, but is not ready for this operation!

how do I get volume 6 ready? Trying to get it in a different "state":

CLI-1> accept unit 6
NOTE: Accept Unit will cause a temporary LUN path change to this controller.
No media exchange detected on unit 6.

is not helping. What is the trick here to assign a spare when it is needed?

Thanks!
-Gunther
4 REPLIES
Uwe Zessin
Honored Contributor

Re: add spare unit=# disk### -> "Volume # is on the same array, but is not ready for this operation!"

Maybe a dumb question, but why don't you just replace the failed disk drive? Pull the bad disk drive in Box 2/Bay 10, wait a minute or so and then put in the new disk. The recovery should start automatically.
.
Gunther S.
Occasional Advisor

Re: add spare unit=# disk### -> "Volume # is on the same array, but is not ready for this operation!"

Good question. I am not physically present. Just trying to stabilize the situation for now.
Guber
Occasional Visitor

Re: add spare unit=# disk### -> "Volume # is on the same array, but is not ready for this op

This is so sad. The question was so good, the reason so perfect, and all the people on help groups do is lecture the original asker "why would you want to do that".

Is thre an answer? 

 

Here is another reason why, as if it needed more reasons! What if the MSA30 disk slot itself has failed, then even changing the disk does not work. And deleting and recreating the unit does not work either, not if other units exist after this one.

So what is the solution to add a drive, re-assign a different drive?

Guber
Occasional Visitor

Re: add spare unit=# disk### -> "Volume # is on the same array, but is not ready for this op

Here, example:

Unit 8:
In PDLA mode, Unit 8 is Lun 9; In VSA mode, Unit 8 is Lun 8.
Unit Identifier :
Device Identifier : 600508B3-0091FB70-D335A505-A2780019
Preferred Path : Controller 1 (this controller)
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME USING REGENERATE
Mirror Init Status: Complete
2 Data Disk(s) used by lun 8:
Disk113: Box 1, Bay 13, (B:T:L 0:14:00)
Disk313: Box 3, Bay 13, (B:T:L 2:14:00) DRIVE FAILED! (0x12)
Spare Disk(s) used by lun 8:
No spare drive is designated.
Logical Volume Raid Level: MIRROR FAULT TOLERANCE (RAID 1)
stripe_size=8kB
Logical Volume Capacity : 70,135MB

CLI-1> expand unit 8 disk403
Unit expansion failed.
You have to include all the current disks in the unit when expanding.

 

CLI-1> expand unit 8 disk113 disk313 disk403
The following drive[s] are not present: DISK313
The unit could not be created!

 

Duh! Why do you think I am trying to expand? The MSA slot failed!