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
DSM 7.1.1-42962U2 driver 2.16.3-2 DSM7.x fails to load automatically at startup/does not default to DHCP #261
Comments
I have not seen this issue normally. BUT!! I have recently redone my nas and did a clean install of the 7.1.1 update 2.. And I did at one point reboot and I had to manually start the package.. I will will check next time I reboot. Thanks for the possible work around if am also seeing this problem. I don't use dhcp on that interface though. But when I started it it did come up with my static settings and everything worked. |
Well I finally got around to shutting down the nas to put in my little velco strips to try and help with the new noisier drives - not sure if it helped any. But anyway upon restart the bb-qq drivers started up on their own. |
Sorry, I'm not sure what your specific environment is, but I have continued to experience this issue at every boot-up. The workaround continues to function, so I'm not fussed about it, but because I'm short on ports on my home network at the moment (waiting for a switch to come back in stock), I don't have the option of keeping a second cable plugged in for troubleshooting. |
My setup is a ds918+ same dsm 7.1.1 u2, but using club 3d usb.. Static IP set, and other end is plugged into pc also using another CAC-1420 usb nic. Running the latest 2.16.3-2 bb-qq.. I rarely reboot my nas.. Other then when update the dsm software. Recently I did an redo of it with bigger drives. I did notice having to run the driver at one point in the process. But when I just recently shut it down to add some velco strips to try and reduce the noise of the drives. When I rebooted it everything came up fine. I will for sure keep an eye on it next time I reboot. |
Could you paste |
Just ran into the same issue. I've updated my DS920+ about 7 days ago; today i had to perform a manually triggered reboot. After rebooting, the package was in "manually stopped" state and missing its configuration for the USB network interface. @bb-qq - these are my
|
Certainly. Would you like me to disable the workaround or keep it when sharing the file? Please accept my apologies for the delayed response, @bb-qq — I'm not getting notifications of replies to this thread. |
Yes, I wanted a log of when the problem was occurring. |
I use this : |
Stil have the issue on my DS215+ with the latest driver. After a reboot the driver is stopped. |
I have the same issue with DS920+ with driver 2.16.3-3 (geminilake). After reboot (because of firmware update) the USB network port will not start automatically, status is stopped Description of products: |
This is not a from the brand Plugable ... |
I have the same issue like mentioned in the thread description. The problem is the driver, not the plug |
The funny thing is that after the first restart it failed to load the driver automatically. Then I fixed it and now it works fine. |
I can confirm that the driver (or service) didn't start after reboot just once, the very first time after installation. The second time it did start automatically. |
I have a DS720+ and my driver package only fails to start when I complete a DSM upgrade. I created a service task to disable/enable the package on boot, so we have to wait until the next DSM Update to see if this works. |
If it did not work, I might be able to investigate if you could paste the contents of |
Is anyone else encountering this problem with 2.16.3-4 or later versions? |
I had this happen on my first installation of 2.17.1-1 with my DS418play and a Plugable USBC-E2500. On the first restart after installation, the driver didn't start, and I had to start it manually via Package Center. After that, it's been working fine after 2 more restarts and one full shutdown/start. Here's my log from
|
Description of problem
Under DSM 7.1.1-42962 Update 2, driver release version 2.16.3-2 DSM7.x, the package does not appear to startup automatically. When started manually, the package does not remember to default to DHCP. I have tried both front and rear ports.
Description of products
Description of environment
NAS connects to Flex XG, M1 Mac Mini with built-in 10Gbe connects to Flex XG. Flex XG is managed by a UDM-SE.
Relevant ifconfig output
Small redactions indicated by [redacted]. ztc interface is a tunnel created by the use of ZeroTier.
Workaround
I've created a task at boot-up that runs as root that toggles the package off and on, and sets the interface to DHCP:
This appears to work and link has been stable for a bit, including ~600GiB transferred. Not sure why this is required though and may be an issue that needs resolution.
The text was updated successfully, but these errors were encountered: