-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DS1019+ losing connections #24
Comments
The QNAP QNA-UC5G1T can get very hot, then drop it's connection rate. I would suggest removing the adapter from its enclosure, to see if it still appears to drop the connection with better ventilation. On the QNA-UC6G1T, underneath the Mac address/serial number sticker, there is a small screw. If you remove this screw, you can slide the circuit board out of the enclosure. The black finned heat sink, pictured below, should performs better with some air circulation. The copper heat sink is from a retired motherboard VRM. |
@jmrickerby - Glad to see that they use a screw. I always end up damaging glue-heavy pieces. |
@jmrickerby I'd like to know how the QNAP with heat sink has performed up untill now :)) |
@devedse - So far so good! No performance slow-downs due to thermal throttling that I'm aware of. On an unrelated note, having some issues with 9K Jumbo packets, but I think this ma be related to a Windows update. |
I'm experiencing connection drops and subsequent SMB instability after copying files over the QNAP QNA-UC5G1T. Client is 2.5GbE. How would I go about diagnosing if this is due to overheating? |
Low power mode is enabled by default in recent versions. With this setting, thermal issues are almost non-existent. |
Description of the problem
While copying data the network connection randomly drops. I can go to package center and turn off and on to get it to work again. May or not be related to my 10Gb rj45 sfp+ in my Mikrotik.
Description of your products
Description of your environment
Output of
dmesg
commandOutput of
lsusb
commandOutput of
ifconfig -a
commandThe text was updated successfully, but these errors were encountered: