Skip to content
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

DS920+ DSM 7.1.1-42962 U1 -aqc111 (SABRENT NT-SS5G)-geminilake-1.3.3.0-9.spk -> Fix: Edit the Network Interface to reset the IP #84 #86

Open
KipiKland opened this issue Nov 8, 2022 · 17 comments

Comments

@KipiKland
Copy link

I initially connected the USB Ethernet adapter on the back port of the DS920+, and all was working fine.
I changed then to front port and even after a NAS restart IP advertised was the same but could not ping it. I confirm i had to apply the same fix in a different post, that was to change IP to another and revert back to the initial one for the IP to work.

@arthurlockman
Copy link

I'm on the same platform (same DSM version too) with the QNAP adapter. I have a recurring issue where the interface just seems to disable itself until I login and disable/enable the driver. No connectivity though the ports on my switch appear to be lighting up as if it's connected. Unplugging the cable doesn't make a difference - I have to reset the driver.

@bb-qq
Copy link
Owner

bb-qq commented Nov 17, 2022

Could you paste /var/packages/aqc111/var/log/start-stop-status.log here?

@arthurlockman
Copy link

Of course! Here's the last 24 hours or so. The failure was just before 8:30PM pacific yesterday. https://gist.github.com/arthurlockman/cf99a99cfc9d37225370d2acfd06024a

@bb-qq
Copy link
Owner

bb-qq commented Nov 19, 2022

Thanks, @arthurlockman. In your case, changing the USB port to which the adapter is connected may improve the symptoms.

@KipiKland, in your case, there seems to be a problem with the driver's handling of restoring IP settings, so logs are needed to investigate.

@arthurlockman
Copy link

Thanks @bb-qq, I'll give it a shot. I had it plugged into the front USB port but I've moved it to the back. I'll report back if that worked. If it's going to fail again it should fail in the next couple days.

@arthurlockman
Copy link

Hmm, ok, so moving it to the back is a non-starter. For whatever reason when it's plugged into the rear USB port, Bonjour (avahi) refuses to work correctly. It never registers a name, it just keeps counting up trying to register. It only works correctly when the adapter is plugged into the front.

@arthurlockman
Copy link

@bb-qq i managed to fix bonjour on the rear port, so I switched the adapter over there. It worked totally fine for several days but this morning exhibited the same symptoms again. I took a snapshot of the logs: https://gist.github.com/arthurlockman/7ff258245406503e6c64b1347aa09828 The failure was around 07:30AM pacific. Any ideas about what's going on?

@bb-qq
Copy link
Owner

bb-qq commented Dec 3, 2022

Can you please paste the output of dmesg as I need the kernel logs to diagnose the symptoms?
Also, Troubleshooting page might help to improve the situation.

@arthurlockman
Copy link

arthurlockman commented Dec 3, 2022

Sure, if/when it happens again I'll grab a snapshot of dmesg. It seems to be working fine right now, but in dmesg I do see a lot of these errors going on:

image

Maybe these have something to do with it?

And, btw, I did upgrade to 1.3.3.0-10. So I'm on the latest version.

@bb-qq
Copy link
Owner

bb-qq commented Dec 4, 2022

The logs from aqc111 kevent 2 may have been dropped can be ignored if they are infrequent, but from the usbfs one it looks like something bad is happening with this UPS device.

Could you try unplugging all USB devices except the Ethernet dongle to isolate the problem?

@arthurlockman
Copy link

Yeah, I had the same thought and unplugged it this morning. Will report back when it happens again.

@arthurlockman
Copy link

@bb-qq aha, got one! Failure was at 18:06. The logs I captured cover up to when I restarted the driver and the interface came back online right away.

dmesg: https://gist.github.com/arthurlockman/f1aacd814bc1be031dfa70d1a1059e9b

start-stop log: https://gist.github.com/arthurlockman/a7dace6aaffa5b9319d8cf3f72dc5c15

@bb-qq
Copy link
Owner

bb-qq commented Dec 10, 2022

Hmmm///
Changing the USB port to connect the NIC with the other USB devices disconnected does not change the result, right?

@arthurlockman
Copy link

That's right. I get the same results in either USB port and with or without other USB devices attached.

I'm wondering at this point if I just have a bad NIC. The errors I've been seeing just don't make sense. I did try plugging it into a different device (Intel Mac Mini) and I had some really strange results there. It would report as connected and work for a little while, but would very quickly just stop working entirely (after maybe 30 seconds being connected). I might see if I can exchange it for a new one and see if that's any better.

@bb-qq
Copy link
Owner

bb-qq commented Dec 31, 2022

I would like to hear any updates on the situation.

@arthurlockman
Copy link

No updates right now unfortunately. I can't get another NIC for quite a while. Deliveries are a month out, no one has one in stock. I'll update if I manage to get another one.

@arthurlockman
Copy link

I'm trying out one thing in the mean time. I had a hunch that it might be power related - perhaps the dongle is drawing too much power sometimes and shutting the USB port down. I've reinstalled it with a much shorter ethernet cable to the transceiver on the other end. We'll see if that makes a difference. If it does a more permanent solution might be to use a powered USB hub to give the dongle more juice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants