The other way around.So you're saying that on 510A firmware, like me you could only connect max 16 drives. But on 602A firmware, you could use more ports for drives and connect 20 drives? That's good to know. I'm pretty sure I never tested that on later FW, because it was only on the 510A firmware that I could get 2 x 6G connections, and there was no way I wanted more drives if I could only use a single lane to the HBA. So I think I only tested >16 drives with 510A FW.
With the 602A firmware, I could not use the top 8087 ports for drives. The drive would appear/disappear.
With 510A, the drive works perfectly in one of the top two ports.
Now, I haven't tried connecting 20 drives t it...yet. But it's promising that the top port works with 510A. Will try and update results here.
Working on it. This was preliminary testing only, to see what can/cannot be done. I ran tests only for a single disk, still need to run for multiple disks. With both firmwares, the single disk was averaging ~150MBps (Hitachi Ultrastar 6G 3TB drive).Are you able to see what total bandwidth you are able to get with 602 or later FW? Have you done any performance test with two cables from HBA to expander, and if so are you able to confirm if the total bandwidth is as expected for 2 x 6G links?
That would not be cool, if that was the case... will need to test.When I tested, the links to HBA always negotiated at 6G, but then the resulting bandwidth was drastically crippled on all FW except 510A. So for example when using 510A with 15 x SATA3 drives, I would see a total write performance of 3+GB/s; each drive around 160MB/s. But when performing the same test with any later FW, this would drop to 1750MB/s - performance per drive of about 115MB/s.