Vero 4K+ with Kodi 19 won't boot if a particular usb drive is present on the usb hub

Have you tried with these options removed? I’ve never used them before, so I’m not sure if they could be an issue. If getting rid of both options help, add them back one at a time so we can see which option is the culprit (I’m guessing it’s the uhelper, but it is just a guess) [data=ordered is the default for ext4, so really shouldn’t be needed]

tried, it didn’t help.

If there is a way to have boot logs before the OSMC logo on the light blue screen, I would provide them.

I’ve extracted the OSMC_TGT_vero3_20210808.img and the OSMC_TGT_vero3_20201227.img install images to compare them, but the boot/config-4.9.113-45-osmc file is 149.0 KiB, while the older equivalent boot/config-3.14.29-160-osmc is 91.7 KiB, too many differences, too many changes to narrow down the problem.

Have you tried unmounting the problem drive before rebooting?

sudo umount /media/KodiDisk

Or change the order that the drives are in fstab and see if the problem follows the drive, or stays with the last drive mounted?

Yes I’ve tried unmounting (via ssh), wait a minute, then reboot (via ssh or gui). Or even using hdparm or hd-idle on the command line after exiting kodi with sudo systemctl stop mediacenter. Also changing the order in fstab (I’m thinking, the problem is before mounting during boot, once it passes Please Stand By all goes smoothly). No change.

I know I’m kinda grasping at straws here… But have you swapped ports on the hub? Are the non-problem drives all self powered and the problem drive the only one powered by the hub? Do you have a spare drive you could test with to see if it’s a problem with 3 drives vs. 2? Do you have another hub you could test with?

We seem to be focusing on the power-up sequence, but since you mentioned that if you power the Vero down, connect the problem drive to Debian and then boot the Vero with the drive on the hub that it boots OK makes me think it’s a problem with the power down sequence, not power up.

Have you tried removing the fstab line and letting it automount under /media?

I have tried with an identical drive (even with same ext4 filesystem), it’s indeed this particular model! Here the details on lshw:

             description: Mass storage device
             product: Elements 2620
             vendor: Western Digital
             physical id: 2
             bus info: usb@1:2.2
             logical name: scsi2
             version: 10.18
             serial: 5758373244393050314C3131
             capabilities: usb-2.10 scsi scsi-host
             configuration: driver=usb-storage maxpower=500mA speed=480Mbit/s

I apologize, it’s a WD Elements, not a WD Passport (it’s even engraved on the enclosure…)

the other 2 drives are:

             description: Mass storage device
             product: Elements 2621
             vendor: Western Digital
             physical id: 1
             bus info: usb@1:2.1
             logical name: scsi0
             version: 10.26
             serial: 57584D31414139343945305A
             capabilities: usb-2.10 scsi scsi-host
             configuration: driver=usb-storage maxpower=500mA speed=480Mbit/s
             description: Mass storage device
             product: M3 Portable
             vendor: Seagate
             physical id: 3
             bus info: usb@1:2.3
             logical name: scsi1
             version: 0.00
             serial: NM13HN0W
             capabilities: usb-2.10 scsi scsi-host
             configuration: driver=usb-storage maxpower=100mA speed=480Mbit/s

ironically they don’t give me any problem.
the AUKEY CB-H6 hub appears as:

             description: USB hub
             product: USB2.1 Hub
             vendor: GenesysLogic
             physical id: 4
             bus info: usb@1:2.4
             version: 6.53
             capabilities: usb-2.10
             configuration: driver=hub maxpower=100mA slots=4 speed=480Mbit/s

Sorry I don’t have another powered usb hub to test (the power is needed as one of the other drives, a Maxtor M3 4TB, wasn’t able to play movies without it, but it mounted fine).

didn’t work, but I have an update:
if I shutdown the Vero, disconnect the drive from the hub, disconnect the barrel power plug on the Vero, wait 5 minutes, reconnect the usb drive and then replug the Vero booting it up, everything works! So connecting to a pc was a false flag: it’s something in the power cycle of this disk, I believe.

Are you sure disconnecting Vero is necessary? If so, this script I found on askubuntu might suggest something you could add in the shutdown sequence:


if [ -z $1 ]; then
        echo usage gooseusb [[[bus]-port].subport]
        lsusb -t

# script by Patrick Cronin on askubuntu

#port="1" # replace '1' with actual bus number as shown by lsusb -t: {bus}-{port}(.{subport})

bind_usb() {
  echo "$1" | sudo tee /sys/bus/usb/drivers/usb/bind

unbind_usb() {
  echo "$1" | sudo tee /sys/bus/usb/drivers/usb/unbind

unbind_usb "$port"
sleep 1 # enable delay here
bind_usb "$port"

I have a similar disk

          product: Elements 25A3
          vendor: Western Digital

What is interesting is that yours reports as


While mine reports as


Is yours a 3.5" Disk with own power source?

it a WD Elements, 4TB, self-powered, usb 3.0, 2.5’’, just like this
I have to report that I did buy an OSMC powered hub some time ago, I’ve found it, but the power plug is missing, I don’t know where it is. I have a 5V 3A wall psu with usb cable and interchangable barrel connectors, but I can’t retrieve info on the correct output voltage, is 5V ok?

I’ve tried to unbind it after unmounting:


unbind_usb() {
  echo "$1" | sudo tee /sys/bus/usb/drivers/usb/unbind

idx="1058:2620" # WD Elements 4TB, from lsusb

for pathx in $(ls -l /sys/bus/usb/drivers/usb-storage/ | grep devices/platform/ | sed "s/^.* -> //g;s///g;s|\(.*\)/\(.*\)|\2|") ; do 
  if [[ "$(cat "/sys/bus/usb/drivers/usb-storage/$pathx/uevent" | grep PRODUCT= | sed "s/\//:/g;s/PRODUCT=//g" | cut -f1,2 -d":")" == "$idx" ]]; then 
    portx="$(echo "$pathx" | sed "s/:.*$//g")"
    echo $portx
unset IFS

unbind_usb "$portx"

exit 0

it unbinds successfully. It didn’t help the problem on reboot.


I’m happy to report that using the official OSMC USB Hub, the Vero boots and reboots fine with all the disks. It stays about 60 seconds in the “Please Stand By” screen but it starts up afterwards.
I still don’t know what is causing this issue. The 4TB WD Elements (ID 1058:2620) is one of the most sold 2.5’’ external usb drives, someone is bound to have the same problem in the future. Most likely there is some regression somewhere.
I really appreciate the help I’ve got here because the Vero isn’t at my home but my parents’ house and I’m not able to be always present, so the less manual intervention from the user, the better. Therefore thank you.
I’ll monitor this thread, if someone finds a definitve solution; in the future I’ll report if it the situation improves after updating.

1 Like

Here, I see a firmware update for the USB hub model string … but there is no Information about changes/fixes.

I’ve tried to update but I just can’t and propably I don’t need to.
First, the exact model, written on the back of the item, is AUKEY CB-H6S (with the 3 leftmost ports for charging only), the amazon page was deleted (sigh), but it’s present on the wayback machine and on camelcamelcamel. It’s written “On Amazon since (Date First Available) 8th November 2018”, while the update instructions come in a file dated 15th May 2018, and the actual update file is dated 24th June 2016.
Second, I don’t have a baremetal windows install, only virtual machines on kvm/qemu, and the fixes to pass a usb hub (not the ‘median’ usb device) to a guest are overly complicated for my immediate use.

For other info, I have to report that the same error (being stuck to the Please Stand By screen on boot) happens if I connect a double USB A male cable to the OSMC usb hub on one end and to an Android Philips TV on the usb2 port on the other end (for passing automated adb commands from the Vero to the TV without wifi). If I plug this cable to the Aukey hub everything is ok. Maybe for diagnostic it’s way cheaper to test this configuration buying such a cable that that particular model of usb disk (having a compatible Android television).
Anyway for now the solution remains as it is, to use different usb hubs for different usb things.

I’m still having this problem, I’m marking this thread as unsolved.
After experiencing the random dimming problem as described here (let’s see if the “limited range colors” option helps, as suggested here), my family rebooted the Vero and it stuck on the PleaseStandBy screen. Unplugging the disk, rebooting by hand (replugging the power cord), and replugging the disk during the light blue screen made it work again.

Today I’ve swapped and changed usb3 cables, tried with or without usb hub, I’ve tried other usb hubs (usb2, powered and unpowered), only with this disk connected (directly to a usb port on the Vero), this disk has still the same problem. I’ve also updated the Vero4k+ (stable branch), now dpkg -l shows

$ dpkg -l | grep vero3
ii  vero3-bootloader-osmc                1.7.0-1                             armhf        Vero 4K/4K+ UBoot package
ii  vero3-device-osmc                    1.5.0                               armhf        Vero 3 metapackage
ii  vero3-earlysplash-osmc               1.0.4                               armhf        Vero3 logo partition
ii  vero3-ftr-osmc                       1.5.9                               armhf        First-time-run scripts for OSMC
ii  vero3-fwenv-osmc                     2016.01-4                           armhf        firmware tools for OSMC
ii  vero3-libcec-osmc                    6.0.2-3                             armhf        libcec
ii  vero3-mediacenter-osmc               19.1.0-18                           armhf        Media Center package for OSMC
ii  vero3-secureosmc-osmc                1.3.0-1                             armhf        Vero 3 secureOSMC integration package
ii  vero3-userland-osmc                  1.9.5                               armhf        Vero 3 userland package
ii  vero3-wifi-osmc                      1.5.0-1                             armhf        Broadcom patchram implementation for Vero
ii  vero364-image-4.9.113-48-osmc:arm64  4.9.113-48-osmc                     arm64        Linux OSMC kernel
ii  vero364-kernel-osmc:arm64            3.9.213                             arm64        Kernel meta package bringing in the latest OSMC kernel for this device

My issue is similar to this one.

The weird thing is that this detail is still valid:

if I shutdown the Vero, disconnect the 4TB WD Elements, connect it to a PC (with Debian), mount it, unmount it, reconnect it to the hub and then boot the Vero, everything works (so without manual intervention during powerup time)

I’ve instructed my relatives how to unplug wait and plug the drive at the right time at boot if it’s needed again, but it’s like expecting a passenger to know how to pilot a plane for filling the gas tank during flight, reality isn’t like Air Force One with Harrison Ford, things can go exponentially bad very quickly

Can you see if the drive has a firmware update?

Just to be sure: You still have the problem but now with the OSMC hub instead of the AUKEY CB-H6S with 3 external disks connected?

Can you see if the drive has a firmware update?

None that I can find (the disk if fairly new anyway)

Just to be sure: You still have the problem but now with the OSMC hub instead of the AUKEY CB-H6S with 3 external disks connected?

Booting without disconnecting the disk from this hub worked for a while (weeks), but I had to change ports after that, now it’s the same as with other hubs.

The problem started after the Kodi 19 update in August, before there was none of this. Can vero3-bootloader-osmc or vero3-earlysplash-osmc be downgraded safely, using packages i.e. from It’s an idea, but I don’t want to brick the device, so I’m asking beforehand.

I’d not recommend downloading the bootloader. It will almost certainly break video playback.