Apologies, but I have problems understanding you, too. Let's see if we can sort that out. Don't be upset if the following is known to you.
(I was enclosing 'new' between '_' as a sign of emphasis.)
VR uses Window's disks for its pools. Once a disk is a member of a pool you can only get through VR at the disk, because, if I recall correctly, it appears as offline to windows.
There are two ways to create a new pool
1) use an 'unformatted' Windows disk, format it as a VR storage unit and make a new empty pool from it
2) use a Windows disk that has already an NTFS filesystem on it, 'convert' it into a VR storage unit and make a new pool from it, containing one virtual disk. You have kept your data.
Last time I checked it was not possible to take another disk with data on it, add it to an existing pool and have that data being retained. It appears that this has changed with VR version 4.0.
--
Now, you write you have already created a pool. If VR sees only local disks as you say, I have to conclude that you have created a pool on a local disk, right?
Next, you write that you have created a logical disk on the MSA1000 and
created another pool - that sounds to me that you now have two pools:
1. on the local disk
2. on the MSA1000
If above is true, then I don't understand why you say that VR sees only local disks.
Another possibility is that you have created the second pool on another local disk and attempted to add a logical disk from the MSA1000 to this pool.
Then you would have two pools on two local disks.
Which guess is right?
--
Have you checked if you can see the MSA1000 logical disks in Windows' device manager? Is Secure Path somehow involved?
.
