hpacucli - can't add spare to RAID1

[wsanders]

 controller slot=0 logicaldrive 1  show detail

Smart Array P410i in Slot 0 (Embedded)

   array A

      Logical Drive: 1
         Size: 465.7 GB
         Fault Tolerance: RAID 1
         Heads: 255
         Sectors Per Track: 32
         Cylinders: 65535
         Strip Size: 256 KB
         Full Stripe Size: 256 KB
         Status: OK
         Caching:  Enabled
         Unique Identifier: 600508B1001CF270594E43EA574A909B
         Disk Name: /dev/sda
         Mount Points: / 446.2 GB
         OS Status: LOCKED
         Logical Drive Label: ADD6BBC85001438022BCED108AF4
         Mirror Group 0:
            physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SATA, 500 GB, OK)
         Mirror Group 1:
            physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SATA, 500 GB, OK)
         Drive Type: Data

=> controller slot=0 array A show detail                     

Smart Array P410i in Slot 0 (Embedded)

   Array: A
      Interface Type: SATA
      Unused Space: 0  MB
      Status: OK
      Array Type: Data

=> controller slot=0 physicaldrive all show       

Smart Array P410i in Slot 0 (Embedded)

   array A

      physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SATA, 500 GB, OK)
      physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SATA, 500 GB, OK)

   unassigned

      physicaldrive 1I:1:3 (port 1I:box 1:bay 3, SATA, 500 GB, OK)

=> controller slot=0 array A add spares=1:3       

Error: Drive 1:3 can not be added to the array as a spare. This drive is not an
       existing spare, is not an unassigned drive or is in a state that is
       preventing the operation from completing. Use the "show" command to
       check the status of the drive you are attempting to use.

The documentation says:

Example commands:
=> ctrl slot=3 array B add spares=1:6

=> ctrl slot=4 arrayall add spares=1:5,1:7

=> ctrl slot=5 array A add spares=1:1,1:5

=> ctrl slot=5 arrayA remove spares=1:1,1:5

What am I doing wrong?

[wsanders]

Needed full drive spec:

controller slot=0 array A add spares=1I:1:3

Volume management bug? That never happens! :-|