Hi,
after switching from RASPBMC to OSMC (fresh install) my USB device is not recognized when doing a “sudo reboot now”. It is only recognized again after disconnecting/reconnecting it.
I also recognized a warning in dmesg about a wrong hdparm ioctl command and incorrect mount options (sync and noatime not applied).
Changing the /etc/udisks-glue.conf like this fixed the problems:
filter disks {
optical = false
partition_table = false
usage = filesystem
}
match disks {
automount = true
automount_options = {sync,noatime}
post_insertion_command = “sudo hdparm -S 240 %device_file”
post_unmount_command = “sudo hdparm -Y %device_file”
}
Frank
Unfortunatly this fix is not working every time.
On some reboots the usb-device (Intenso USB Drive) is not recognized at all in dmesg (this part is missing in the log after a reboot):
[ 208.149252] usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 208.149268] usb 1-1.2: Product: USB 3.0 Device
[ 208.149280] usb 1-1.2: Manufacturer: Intenso
[ 208.149292] usb 1-1.2: SerialNumber: 324000000000000025BD
[ 208.152907] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[ 208.171571] usb-storage 1-1.2:1.0: Quirks match for vid 174c pid 55aa: 400000
[ 208.173370] scsi host0: usb-storage 1-1.2:1.0
[ 208.231099] usbcore: registered new interface driver uas
[ 218.853294] scsi 0:0:0:0: Direct-Access Intenso USB 3.0 Device CC4B PQ: 0 ANSI: 0
[ 218.860446] sd 0:0:0:0: [sda] 732566646 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[ 218.861165] sd 0:0:0:0: [sda] Write Protect is off
[ 218.861198] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[ 218.861863] sd 0:0:0:0: [sda] No Caching mode page found
[ 218.861895] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 218.863404] sd 0:0:0:0: [sda] 732566646 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[ 218.888906] sda: sda1
[ 218.891302] sd 0:0:0:0: [sda] 732566646 4096-byte logical blocks: (3.00 TB/2.72 TiB)
[ 218.892668] sd 0:0:0:0: [sda] Attached SCSI disk
[ 218.941864] sd 0:0:0:0: Attached scsi generic sg0 type 0
In Raspbmc i had this problem only on very rare conditions. In OSMC this seems to happen a lot.
Any ideas?
Btw, the device has it’s own power supply, so no power related problem.
Edit: after a manual reboot the device is also not detected by “lsusb”. Seems like the controller in the external drive is in a state where it doesn’t want to talk 
Found out, that this problem is kernel(uas) related.
There is a patch available for this kind of devices, but i don’t know how to apply it for osmc kernel:-/
See (it’s the problematic Sata-Bridge 174c 55aa)
https://www.marc.info/?l=fedora-extras-commits&m=142107212129952&w=2
If there is someone willing and capable of applying this fix for osmc my problems should be solved ,-)