Kaltar Posted April 24, 2017 Share Posted April 24, 2017 Hey Guys I'm pretty new to Unraid, and something that has caught my attention is the log in the top right corner. It shows that unraid finds a usb hub and then disconnects.. It is doing this all day, 24/7 anyone know what is causing this ? Apr 24 19:18:59 Tower kernel: usb 4-3: USB disconnect, device number 26Apr 24 19:18:59 Tower kernel: usb 4-3: new high-speed USB device number 27 using xhci_hcdApr 24 19:18:59 Tower kernel: hub 4-3:1.0: USB hub foundApr 24 19:18:59 Tower kernel: hub 4-3:1.0: 2 ports detectedApr 24 19:20:04 Tower kernel: usb 4-3: USB disconnect, device number 27Apr 24 19:20:04 Tower kernel: usb 4-3: new high-speed USB device number 28 using xhci_hcdApr 24 19:20:05 Tower kernel: hub 4-3:1.0: USB hub foundApr 24 19:20:05 Tower kernel: hub 4-3:1.0: 2 ports detectedApr 24 19:20:54 Tower kernel: usb 4-3: USB disconnect, device number 28Apr 24 19:20:55 Tower kernel: usb 4-3: new high-speed USB device number 29 using xhci_hcdApr 24 19:20:55 Tower kernel: hub 4-3:1.0: USB hub foundApr 24 19:20:55 Tower kernel: hub 4-3:1.0: 2 ports detectedApr 24 19:21:45 Tower kernel: usb 4-3: USB disconnect, device number 29Apr 24 19:21:45 Tower kernel: usb 4-3: new high-speed USB device number 30 using xhci_hcdApr 24 19:21:45 Tower kernel: hub 4-3:1.0: USB hub foundApr 24 19:21:45 Tower kernel: hub 4-3:1.0: 2 ports detected Everything seems to be working fine. The hardware is a HP Proliant ML310e v2 Xeon 1240v3 32GB Ram 4 * WD red 2tb Any logs I can pull to help troubleshooting this. ? Oh and Unraid is updated to newest version Quote Link to comment
Frank1940 Posted April 24, 2017 Share Posted April 24, 2017 You can get the files needed for the Gurus by going to 'Tools' >>> 'Diagnostics' and that will download a zipped file to your download folder of your browser. Upload that file with your next post. You can also tell us what USB devices are connected to your server. (You have a least one-- your Flash Drive with unRAID on it.) By the way, it is best to use a UBS2 (NOT a USB3) port for your boot drive. The speed of the Flash Drive is not that important as unRAID runs completely from RAM from the time it first boots. Quote Link to comment
Kaltar Posted April 24, 2017 Author Share Posted April 24, 2017 Okay, I've downloaded the diagnostics file and attached it to this post. Also there is no USB devices attached to the server other than the Flashdrive, which is connected to the internal USB 2 port on the motherboard. tower-diagnostics-20170424-2144.zip Quote Link to comment
Frank1940 Posted April 24, 2017 Share Posted April 24, 2017 You have three syslogs files (because the master syslog is being filled with those USB events) in your diagnostics file but the initial one occurred BEFORE the first entry in the earliest log file. You may have to reboot the server and grab a new diagnostics file after the first few occurrences . What we need to see if there is a clue to what triggered the first one. By the way, are you passing a USB port through to a Docker or VM? Quote Link to comment
Kaltar Posted April 24, 2017 Author Share Posted April 24, 2017 Okay, I've restarted the server and downloaded a new diagnosticsfile. Also, I'd like to know, why does my array not automaticly come online when I reboot. It says the configuration is valid, and in settings under disks settings "Enable auto Start" is set to yes tower-diagnostics-20170424-2224.zip Quote Link to comment
Squid Posted April 24, 2017 Share Posted April 24, 2017 41 minutes ago, Kaltar said: Also, I'd like to know, why does my array not automaticly come online when I reboot. Best guess is this: Apr 24 22:18:51 Tower emhttp: err: get_limetech_time: -2 (7) 0 Followed by Apr 24 22:18:51 Tower kernel: mdcmd (28): import 27 Apr 24 22:18:51 Tower kernel: mdcmd (29): import 28 Apr 24 22:18:51 Tower kernel: mdcmd (30): import 29 Apr 24 22:18:51 Tower kernel: md: import_slot: 29 empty Apr 24 22:18:51 Tower emhttp: import flash device: sda Apr 24 22:18:51 Tower emhttp: shcmd (13): /etc/rc.d/rc.nfsd start |& logger Apr 24 22:18:51 Tower root: Starting NFS server daemons: Apr 24 22:18:51 Tower root: /usr/sbin/exportfs -r Apr 24 22:18:51 Tower root: /usr/sbin/rpc.nfsd 8 Apr 24 22:18:51 Tower dhcpcd[1669]: br0: offered 192.168.1.100 from 192.168.1.1 your server didn't get a valid IP until after emhttp started...., and internet access is required for Trial. Since it didn't have it when emhttp loaded, emhttp wouldn't autostart the array. Won't be an issue if/when you purchase. (But, setting a static IP either in unRaid or in your router would probably fix that) No real good answer as to the continual usb hubs being found. A work around would be to disable one at a time the ports in your bios until your find the offending controller and then disable it. As an aside, I had a KVM that also did the exact same thing... While by itself the continual disconnects / reconnects won't cause any issue, the logging spam will... Quote Link to comment
Kaltar Posted April 26, 2017 Author Share Posted April 26, 2017 Noone else have anything on this ? Quote Link to comment
-jim Posted March 1, 2021 Share Posted March 1, 2021 (edited) I seem to be having similar issues: Mar 1 05:28:57 Tower kernel: usb 1-2: USB disconnect, device number 44 Mar 1 05:28:57 Tower kernel: usb 1-2: new full-speed USB device number 45 using xhci_hcd Mar 1 05:28:57 Tower kernel: cdc_acm 1-2:1.0: ttyACM0: USB ACM device Mar 1 05:29:01 Tower kernel: usb 1-2: USB disconnect, device number 45 Mar 1 05:29:01 Tower kernel: usb 1-2: new full-speed USB device number 46 using xhci_hcd Mar 1 05:29:01 Tower kernel: cdc_acm 1-2:1.0: ttyACM0: USB ACM device Any Ideas? In my case, this is the ConbeeII (ZigBee Controller) on Unraid: Conbee II - endless connecting/disconnecting loop on USB level CAN'T READ CONFIGURATIONS, ERROR -110 (CONBEE II USB STICK NOT WORKING) Conbee II issues (with Unraid) since last firmware update unRAID - deCONZ - ConBee II I unplugged it and the errors stopped. Still not certain of the solution to fix the issue. Edited March 1, 2021 by -jim Quote Link to comment
blackbrizz Posted April 7, 2021 Share Posted April 7, 2021 On 3/1/2021 at 12:21 PM, -jim said: I seem to be having similar issues: Mar 1 05:28:57 Tower kernel: usb 1-2: USB disconnect, device number 44 Mar 1 05:28:57 Tower kernel: usb 1-2: new full-speed USB device number 45 using xhci_hcd Mar 1 05:28:57 Tower kernel: cdc_acm 1-2:1.0: ttyACM0: USB ACM device Mar 1 05:29:01 Tower kernel: usb 1-2: USB disconnect, device number 45 Mar 1 05:29:01 Tower kernel: usb 1-2: new full-speed USB device number 46 using xhci_hcd Mar 1 05:29:01 Tower kernel: cdc_acm 1-2:1.0: ttyACM0: USB ACM device Any Ideas? In my case, this is the ConbeeII (ZigBee Controller) on Unraid: Conbee II - endless connecting/disconnecting loop on USB level CAN'T READ CONFIGURATIONS, ERROR -110 (CONBEE II USB STICK NOT WORKING) Conbee II issues (with Unraid) since last firmware update unRAID - deCONZ - ConBee II I unplugged it and the errors stopped. Still not certain of the solution to fix the issue. Exact same issue here with conbee II and I have not been able to solve it either.. My workaround at the moment is to reboot my server every second or third day.... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.