Can't create a pool from a pool, Error "Sequence contains no elements"

[brewfest_]

I am trying to create a pool of pools but stablebit drivepool errors with "Error adding drive" "Sequence contains no elements" when I go to create the top level pool. 

I have two 8TB drives that I have successfully pooled into a virtual 16TB drive. I want to add this new virtual 16TB drive into a pool with other identically pooled virtual 16TB drives and physically 16TB drives. When I click create pool and try adding my the new virtual 16TB pooled drive, it throws the above error.  Both 8TB drives are empty except for the pool information created when creating the 16TB virtual drive.

 

It's my understanding such hierarchical drive structures should be possible? Please help me solve this.

[brewfest_]

Okay I figured out the issue. The problem was I was on DrivePool version 2.3.12.1683 and the in-application update check was broken. manually downloading and installing 2.3.13.1687 resolved the issue and allowed me to create the top level drive.

[brewfest_]

I've tried reformatting them and nothing changed. I've also tried putting a file in each drive before pooling them and again, no change in performance. chkdsk found no issue with each drive. Trying with two other 8TB drives also results in the same failure. I still have plenty of drive letters for windows to use.

For some more background on my system:
AMD FX 8320
Gigabyte 990FXA-UD3
32GB memory (up to 24GB in a dynamic RAM disk)
GTX 1070
LSI 9217-8i
10 8TB HDDs (all of these I want to turn into 16TB virtual drives and then added to the top level pool)
3 16TB HDDs
1 1TB SATA SSD boot drive

The two original disks in question are wired directly to the motherboard and not through the LSI card. 

I have attached captures of the chkdsk results for both drives and exactly what happens when trying to create a new pool from the newly created virtual 16TB drive ( Data Delta One V:\ and Data Delta Two U:\ -> DrivePool D:\ )
 

[Shane]

Hi, yes it should be possible and it sounds like you're doing what you're supposed to do.

Only two times I've heard of that error in relation to DrivePool, #1 was a (fixed) bug related to duplication and #2 it turned out to be a bad drive. You may wish to run chkdsk /r on the drives?

Alternately, if nothing shows up in chkdsk, since they're empty try reformatting them? (if they're old used drives it's possible NTFS has gotten a screw loose)