4K+ does not automount USB drive after reboot

Help and Support Vero 4K / Vero 4K +
1

Hello,

after reboot, no automounted USB drive.

fstab:
UUID=01D5FF69801B4F20 /mnt/mydisk ntfs defaults,auto,users,rw,nofail,umask=000 0$

log entries:
Nov 08 17:30:05 osmc systemd[1]: dev-disk-by\x2duuid-01D5FF69801B4F20.device: Job dev-disk-by\x2duuid-01D5FF69801B4F20.device/start timed out.
Nov 08 17:30:05 osmc systemd[1]: Timed out waiting for device /dev/disk/by-uuid/01D5FF69801B4F20.
Nov 08 17:30:05 osmc systemd[1]: Dependency failed for /mnt/mydisk.
Nov 08 17:30:05 osmc systemd[1]: mnt-mydisk.mount: Job mnt-mydisk.mount/start failed with result ‘dependency’.
Nov 08 17:30:05 osmc systemd[1]: Startup finished in 3.544s (kernel) + 1min 30.420s (userspace) = 1min 33.964s.
Nov 08 17:30:05 osmc systemd[1]: dev-disk-by\x2duuid-01D5FF69801B4F20.device: Job dev-disk-by\x2duuid-01D5FF69801B4F20.device/start failed with result ‘timeout’.

Manual mount works: sudo mount /dev/sda5 /mnt/mydisk/

500GB USB drive.

Any ideas ?

2

It is possible that your disk has changed uuid (although it shouldn’t).

Try posting the result of “blkid”.
Is sda5 a partition of your usb disk and the one which is supposed to be mounted at boot ?

3

Is the drive self powered, or powered via USB. If it’s powered via USB it is probably starving for power. Try using a powered USB hub instead of powering it from the Vero, as it can only supply the .5A max as per the USB spec.

4
  1. blkid: /dev/sda5: UUID=“01D5FF69801B4F20” TYPE=“ntfs” PARTUUID=“10e8f80c-05”
  2. UUID is identical
  3. sda5 a partition of my usb disk and the one which is supposed to be mounted at boot
  4. The drive is powered via USB HUB
5

Does your disk is shown in dmesg ?
The default timeout is 90s, so it’s long enough.

Type dmesg with root and post its content.

6

paste-logs -J -K and sharing the URL is easier :wink:

7

https://paste.osmc.tv/dekovoloya

8

This might be relevant. From the mount(8) man page:

Note that mount(8) uses UUIDs as strings. The UUIDs from the command line or from fstab(5) are not converted to internal binary representation. The string representation of the UUID should be based on lower case characters.

Worth a try.

9

Nice find.
I checked on my servers (not related to kodi or osmc) and the uuid are indeed in lowercase in fstab.

10

Changed to lowercase - now the drive shows in auto-mounted drives, but not in library (via mountpoint).
Fresh messages: https://paste.osmc.tv/kiyedulusa

11

Full logs will be more useful: grab-logs -A (Kodi logs aren’t of interest in this case, but the rest might hold a clue.)

12

Reverted back original fstab entry:

UUID=01D5FF69801B4F20 /mnt/mydisk ntfs defaults,auto,users,rw,nofail,umask=000 0

and everything work fine (moutned and mapped in correct library).

Logs:
https://paste.osmc.tv/duhekogejo

Suspects are:
HDD enclosure - cheap one from Ali
USB powered HUB

13

It could be a dodgy enclosure or hub but to that you can add a dodgy line in /etc/fstab (sorry I missed it before):

UUID=01D5FF69801B4F20 /mnt/mydisk ntfs defaults,auto,users,rw,nofail,umask=000 0 0

It should be user, not users. That said, it’s unnecessary to use user in OSMC since you can always run sudo when mounting. (Just a FYI: default options are rw, suid, dev, exec, auto, nouser and async)

It might also have contributed to this permission-related problem:

Nov 09 18:13:16 osmc udisks-glue[437]: Failed to automount /dev/sda5: Error mounting: mount exited with exit code 1: helper failed with:
Nov 09 18:13:16 osmc udisks-glue[437]: Error opening read-only '/dev/sda5': Permission denied
Nov 09 18:13:16 osmc udisks-glue[437]: Failed to mount '/dev/sda5': Permission denied
Nov 09 18:13:16 osmc udisks-glue[437]: Please check '/dev/sda5' and the ntfs-3g binary permissions,
Nov 09 18:13:16 osmc udisks-glue[437]: and the mounting user ID. More explanation is provided at
Nov 09 18:13:16 osmc udisks-glue[437]: http://tuxera.com/community/ntfs-3g-faq/#unprivileged
1 Like
14

@dillthedog: Good point, thank you man!