Ok.. I don't think the call error kept it from changing. When I went in to legacy, it was set to disabled... I enabled and disabled again just in case. I've re-run the tests but no change.
I had the drives before I had the parts to build the new system. I connected them in my ubuntu machine and ran the in depth smart tests on them, then I created a ZFS mirror while on that machine and copied a bunch of media over to it. (I was hoping I'd be able to just import the pool on the new system.. but it never saw it). On that system the transfer rates to the drives were normal. I did not blank the drives or anything before putting them into the freenas build... I just created them as a mirror there when it did not see them for import. Could not wiping them cause this trouble? The SSD had been formatted as EXT4 prior to this install.. I had not wiped it either.
Thank you everyone for your time and ideas.. even if not successful I have learned some things and that is always a benefit.
I had the drives before I had the parts to build the new system. I connected them in my ubuntu machine and ran the in depth smart tests on them, then I created a ZFS mirror while on that machine and copied a bunch of media over to it. (I was hoping I'd be able to just import the pool on the new system.. but it never saw it). On that system the transfer rates to the drives were normal. I did not blank the drives or anything before putting them into the freenas build... I just created them as a mirror there when it did not see them for import. Could not wiping them cause this trouble? The SSD had been formatted as EXT4 prior to this install.. I had not wiped it either.
Thank you everyone for your time and ideas.. even if not successful I have learned some things and that is always a benefit.