it’s me again. After we finally cracked the Ethernet Issue (see here), I got another one. I did not see - the last time - that my RPI2 does not recognize my HDD anymore.
I just connected it to my Mac and it works like a charm. But as soon as I connect it to the PI it just does nothing. No blink, no reaction, nothing. I do not think the USB Port is broken, because I can use my external keyboard without any problems.
I already tried dmesg but I do not get any response, even after unplugging and plug it in again. Any idea?
Ok, I have posted this too fast. My keyboard does not work either… also the Sundtek TV is gone… btw I use this one here. I did not update the PI or anything and it worked in the morning - because I watch the News before I go to work… help?
here is the output (some of it) of the dmesg after the reboot:
Sure, but (privacy question) is there a way to delete this paste.osmc.io later on? → @Toast until then see PM. feel free to copy & paste the error-logs needed for public reasons. but the other stuff if not, not pls
BTW @Toast: a reboot fixed at least the Keybord + Sundtek issue, but the HDD is not back on. It blinked once and started but then went off again.
Without even checking your logs its pretty clear from the description that you have a hardware issue, probably power related.
All the devices that you are having trouble with run off the onboard USB hub - including the Ethernet controller. It’s well known that when the voltage gets too low the USB hub stops working, this causes all USB devices including Ethernet to drop out.
Before you waste too much more time looking for a software solution to what is very likely a hardware issue, please check your power supply or try another one, and start with a minimum of USB devices attached.
This is a false assumption to make - USB keyboards draw less than 100mA of current, spinning drives draw typically in excess of 500mA some as much as 1000mA.
Also USB keyboards usually operate in USB “Full Speed” mode (12Mbps) while USB hard drives operate in “High Speed” mode which is up to 480Mbps. Apples and Oranges.
Toast sent me a copy of your debug log and two things stand out right away:
Feb 19 18:27:13 osmc kernel: Not tainted 4.4.0-1-osmc #1
Feb 19 18:27:13 osmc kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 19 18:27:13 osmc kernel: kworker/0:0 D 8074c63c 0 4 2 0x00000000
Feb 19 18:27:13 osmc kernel: Workqueue: usb_hub_wq hub_event
Feb 19 18:27:13 osmc kernel: [<8074c63c>] (__schedule) from [<8074cc80>] (schedule+0x5c/0xcc)
Feb 19 18:27:13 osmc kernel: [<8074cc80>] (schedule) from [<8075050c>] (schedule_timeout+0x240/0x2e0)
Feb 19 18:27:13 osmc kernel: [<8075050c>] (schedule_timeout) from [<8074df64>] (wait_for_common.constprop.3+0xa4/0x10c)
Feb 19 18:27:13 osmc kernel: [<8074df64>] (wait_for_common.constprop.3) from [<8074dfe8>] (wait_for_completion+0x1c/0x20)
Feb 19 18:27:13 osmc kernel: [<8074dfe8>] (wait_for_completion) from [<8004d2d8>] (flush_work+0x22c/0x2e4)
Feb 19 18:27:13 osmc kernel: [<8004d2d8>] (flush_work) from [<800507ac>] (cancel_delayed_work_sync+0xb4/0x398)
Feb 19 18:27:13 osmc kernel: [<800507ac>] (cancel_delayed_work_sync) from [<80577138>] (usb_stor_disconnect+0x3c/0x11c)
Feb 19 18:27:13 osmc kernel: [<80577138>] (usb_stor_disconnect) from [<805378e8>] (usb_unbind_interface+0x84/0x2d0)
Feb 19 18:27:13 osmc kernel: [<805378e8>] (usb_unbind_interface) from [<804a9124>] (__device_release_driver+0xbc/0x150)
Feb 19 18:27:13 osmc kernel: [<804a9124>] (__device_release_driver) from [<804a91e4>] (device_release_driver+0x2c/0x38)
Feb 19 18:27:13 osmc kernel: [<804a91e4>] (device_release_driver) from [<804a8b64>] (bus_remove_device+0x11c/0x148)
Feb 19 18:27:13 osmc kernel: [<804a8b64>] (bus_remove_device) from [<804a4354>] (device_del+0x1e8/0x350)
Feb 19 18:27:13 osmc kernel: [<804a4354>] (device_del) from [<80535d08>] (usb_disable_device+0xf8/0x32c)
Feb 19 18:27:13 osmc kernel: [<80535d08>] (usb_disable_device) from [<805293c4>] (usb_disconnect+0xa4/0x250)
Feb 19 18:27:13 osmc kernel: [<805293c4>] (usb_disconnect) from [<8052b3d4>] (hub_event+0x5c4/0x1664)
Feb 19 18:27:13 osmc kernel: [<8052b3d4>] (hub_event) from [<8004f1c8>] (process_one_work+0x158/0x558)
Feb 19 18:27:13 osmc kernel: [<8004f1c8>] (process_one_work) from [<8004f61c>] (worker_thread+0x54/0x5a0)
Feb 19 18:27:13 osmc kernel: [<8004f61c>] (worker_thread) from [<80057774>] (kthread+0x180/0x198)
Feb 19 18:27:13 osmc kernel: [<80057774>] (kthread) from [<80016fc8>] (ret_from_fork+0x14/0x2c)
This is a kernel oops that is a result of an unexpected USB disconnect, so this confirms USB devices are being dropped.
I also see that you do not have max_usb_current=1 in your config.txt - if you are trying to power a USB hard drive and a TV tuner, both of which draw a lot of power, this is never going to work without setting max_usb_current=1, and may be marginal even then.
This config.txt setting will only be useful if the power adaptor itself can supply enough power.
So try adding that setting and rebooting, and try with only one of the hard drive or TV tuner plugged in at a time initially. Not all external drives can be powered from a Pi even with a good power adaptor and max_usb_current=1.
What privacy are you fearing? There is no information in the logs that anyone outside of your network is able to use. And without logs helping is really impossible.
But the solution to your problem is very likely power as also dbmandrake already wrote. So do the following:
Ensure you have a proper powersupply and a proper powercable (and make sure you never ever will see a rainbow color square in the top right)
Add max_usb_current=1 to your /boot/config.txt and reboot
Connect Keyboard and TV Tuner only first to test. If it works you might be able to attach the harddisk also. But you may alternatively connect it with a powered USB hub
I just bought a new USB hub with its own power supply, and now the HDD blinks again (light is on), but (!) I cannot see it though. In the Kodi System Info Screen it is not listed (next to the network drive I have).
What’s up next?
Somewhere below dmesg I saw FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. does this cause the issue?
Feb 20 12:37:56 osmc kernel: usb 1-1.5.1: New USB device found, idVendor=1058, idProduct=1130
Feb 20 12:37:56 osmc kernel: usb 1-1.5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 20 12:37:56 osmc kernel: usb 1-1.5.1: Product: My Book 1130
Feb 20 12:37:56 osmc kernel: usb 1-1.5.1: Manufacturer: Western Digital
Feb 20 12:37:56 osmc kernel: usb 1-1.5.1: SerialNumber: 574341575A30333832313234
Feb 20 12:37:56 osmc kernel: usb-storage 1-1.5.1:1.0: USB Mass Storage device detected
Feb 20 12:37:56 osmc kernel: scsi host0: usb-storage 1-1.5.1:1.0
Feb 20 12:37:56 osmc kernel: usb 1-1.5.2: new high-speed USB device number 6 using dwc_otg
@fzinken I am not sure, but I thought I heard it when the Pi started. But then it went off again and just indicated that it is attached to a hub or gets a “ping” signal or something. But I the PI2 does not read something from it.
I am at the point to give up and reinstall the OSMC, plugins and everything else again… Because it is kinda frustrating… Or do you have any other clue/idea?
Everything worked like a charm for 8 months until I installed the latest update…
Well while I still doubt that the update would have impacted that your harddisk would have been detected (and to be honest it would not be possible that it would have worked with out either a powered hub or the max_usb_current setting) you still could try to downgrade the kernel with
Actually I just remember the other thread. And as you had a filesystem corruption technically it might be possible that some frivers are corrupted and therefore the harddisk not detected. In that case a clean install might be the best
If you have any other power hungry USB devices then yes I would still add it, provided that your power adaptor is rated at at least 2 amps.
TV tuner adaptors and some wifi adaptors are also known to consume enough power to require this setting to work reliably.
Even if your hard drive is now powered off its own power source, if there are any other USB devices drawing too much power they will cause the USB controller to drop out and affect other USB devices - that’s why I also suggested testing with only the hard drive connected, but in your debug log the TV tuner is still connected.
I see the hard drive USB device detected in the log but I don’t see the kernel detecting any partition table on the drive, nor any udisks-glue entries showing attempts to auto mount partitions.
So either there is no partition table on the drive or the drive cannot be read.
Hi, meanwhile I figured out that many issues I had (Ethernet, …) are caused by the HDD. Whenever I do not connect it to my Pi (via HUB or not) everything works like a charm. But when I start my PI with the HDD attached I have these issues.
What’s wrong with my HDD suddenly? Can I somehow fix this without reseting my HDD?