For a long time, I have been using Mellanox 10G SFP+ 10G networking cards between my main PC and my NAS and they have been flawless. The problem is that it restricts my video card to 8x mode. The performance drop is incredibly minor, but it is something that has always bothered me. I recently updated my PC, and an AQC108 10G ethernet port is included on-board. Hooray! No more 8x limitation!
I proceeded with obtaining an Aquantia AQN-107 card, since they are the most reasonably priced option out there. My PC is running Windows 10, while my NAS runs Linux. Unfortunately, I was seeing some very odd behavior. Copying files to my NAS seemed to work great. However, copying files from my NAS would lead to corruption. How this is even possible, I’m not sure — one would think there would be some sort of error checking in the SMB protocol. This is a direct connection and there isn’t a switch involved.
I ran through various tests, using the Intel I219-V (which have always been flawless) and sure enough, there are no issues using 1G networking.
Obviously, I could go and get Intel 10G NICs for 3x the price and probably solve the issue, but it would bring me back to the whole 8x problem. I may be able to install an Intel card on my NAS (using mixed Aquantia-Intel) and solve the problem that way.
It was my thought, that there may be an incompatibility with the drivers and their features though. The Linux driver seems to be quite a ways behind the ones available for Windows in feature set. I proceeded to turn off all options for the Windows card and do a compare. I was using fc to compare the original with what was saved on the NAS. Sure enough, no problems arose! Thankfully, the corruption appears in a few seconds, so testing each option wasn’t a very lengthy procedure.
I eventually came across the culprit: Recv Segment Coalescing
Disabling this option and leaving all the other features (such as checksum offloading, etc) seems to have solved the issue. I copied and did a compare of almost 7 TB of data and no issues were found. I plan on sending a note to Aquantia to see if this is a known issue and I will update when I hear back from them.
I hope to save someone else a lot of time and aggravation with these findings and thankfully the corruption was one-way. It could have been a lot worse since most of my data flow is also copying data to the NAS, and not the other way around. Still, silent corruption is unacceptable as far as Windows is concerned. I really wish it would have raised an error instead of reporting success.
I’ve tried the newest drivers from Aquantia (2.1.17, 03/19/2019) and the same problem still occurs. I have installed an Intel 10G X550-T1 NIC on my NAS and that did not solve the issue either.
3 thoughts on “Aquantia 10G Networking Issues”
Thanks for this, I’m encountering the same issue with my AQN-107 card as well. When directly connected to a Synology NAS, certain file transfers would fail. SMB seems to work (can browse) but any file transfer would cause the connection to seize. Also, FTP did not not work.
Turning off Recv Segment Coalescing solved the issue.
Why would Recv Segment Coalescing cause such a problem!?
It’s good to know that I’m not alone with the issue! I’m hoping it’s a Windows driver issue at this point, since I replaced the Linux side with an Intel NIC. Even after replacing the NIC, I still get 10 GB send (AQN-107 -> Intel) but only 2 GB receive (Intel -> AQN-107). This is the same behavior I got with the standalone Aquantia card on the Linux end, so it seems to be pointing the issue towards the Windows side of things. Completely opposite what I thought it would be!
Just ran into this issue when I changed my router from netgear to a new ASUS to prepare for a 2gig internet upgrade.
Spent a few hours trying to figure it out as it kind of felt like a weird DNS issue that site would work great then most wouldn’t at all. Switched cables, updated drivers to the dec 2021 version, reset my networking, cleared caches, etc etc. Other computers and my phone worked fine but my main system wouldn’t. But then I switched from the aqn-107 to the intel nic (both built into the motherboard) and it worked fine.
After I did some searching and came across a post on the Asus forum, I turned off that setting and bam!, works fine. .
Really don’t understand how a router change (or the switch in the router?) triggered this.