After the latest update my Pi3 system, which has been working for over a year with no problems, fails to boot, freezing on the blue OSMC logo screen. I have isolated the problem- it only occurs when my external 2TB USB drive is connected. I have reverted to my old setup, done fresh installs, and installed alternative Kodi distributions. This freeze-on-boot condition only happens on OSMC with the latest update applied. The system boots normally without the external drive connected.
The drive has been error checked and is fine. I am mightily struggling to get any logs as the system won’t boot to a useful state with the drive connected, and without, it boots fine and the logs are clean.
I’m hoping someone else has seen this problem and might save me more troubleshooting time. Any thoughts?
I was just about to add something to my post- that’s the other weird thing. If I boot the system, then connect the drive, it’s apparently not detected, and what’s weirder, various things stop working, including various menu items (when selected, nothing happens) and what’s worse, ssh stops working so I can’t investigate what’s going on.
As far as power supply, I have a 4A supply set at 5.1 volts, the voltage is rock solid and as I said, this same setup works perfectly with the latest kodi (and even all my previous plugins and settings) under one of the other Kodi distros (*elec).
I’ll give it a shot- the trick is going to be to get it to drop to a command prompt somehow.
The thing is, the only thing that has changed about the setup is the last update, so I was hoping someone a little more familiar with OSMC might know of something that changed in this update that could be related. It’s not the latest Kodi as that works with OSes.
Hehe, I wasn’t going to trouble you for those instructions, but thanks for that. I did google it and find my way to the prompt.
So, the good news is that the drive isn’t crashing the system or anything. It even automounts and I can get into the drive and access all the contents, etc. The one thing is that dmesg gives a bunch of weird feedback, such as “tag#0 UNKNOWN(0x2003) Result: hostbyte…”
I’m not sure these are actually errors, but I’ve never seen them before. Like I said, the drive does mount successfully and I can use the files from the prompt.
Ah, you mentioned filesystem, it is NTFS… wonder if this new kernel is doing something different with the NTFS driver?
geez, I’m punchy this morning. I didn’t read the whole way back through the dmesg…
As it’s mounting the drive, I get a “The driver for the USB controller dwc_otg_hcd does not support scatter-gather which is required by the UAS driver. Please try an other USB controller if you wish to use UAS.” Related possibly?
Thanks to you guys for looking in to this issue. I just applied the update and unfortunately, it makes no difference in my case- the system still hangs during boot with the external drive connected. I’m supposed to be working now so I won’t be able to test further until later on. I do appreciate the help though!
Are you still getting the message: “The driver for the USB controller dwc_otg_hcd does not support scatter-gather which is required by the UAS driver. Please try an other USB controller if you wish to use UAS.”
Updated logs and output of “lsusb -v” would be useful.