I have recently purchased a new Raspberry Pi 3 B+ and installed OSMC and Raspbian Stretch full on it. The NTFS partition is the only partition on the USB HDD (it’s a ADATA CH94 500 GB), it has a cluster size of 4 KiB and does not report any errors (with chkdsk under W7). On booting into Raspbian Stretch it automounts, I can see all the files & contents perfectly and everything works. When trying to use it under OSMC it does not auto-mount (I’ve read on this forum that it should). I’ve tried changing in config.txt the USB power setting, I’ve tried both connected directly and through a powered USB hub (I should mention that under Raspbian it works connected directly and with the default settings). Under OSMC I tried mounting it manually either via SSH or by exitting Kodi and logging into OSMC locally with a mouse and keyboard and no matter what I try I always get “Error reading bootsector: Input/Output error
Failed to mount ‘/dev/sda1’ : Input/Output error
NTFS is either inconsistent, or there is a hardware fault, it it’s SoftRAID/FakeRAID hardware…”
I have run chkdsk /f on Windows and it reported no errors, I always safely remove it before disconnecting it (and as I said before I have no problem using it under Raspbian). The drive and partition show up fine with commands like “lsblk” (It shows just the disk and the one partition, /dev/sda and /dev/sda1 with the right sizes and everything…)
I just don’t know what to do, or try anymore?
Other than the HDMI CEC Remote settings and the config.txt USB power settings nothing else was modified in the configuration, and it was last updated today.
Can you post a log? It may give us some clues
Does this help? https://paste.osmc.tv/ajujiqapol
I’m a OSMC newbie
Should I post any other logs?
Oct 06 21:08:49 osmc kernel: sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
...
Oct 06 21:13:23 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Oct 06 21:13:23 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
Oct 06 21:13:23 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x20 ASCQ=0x0
Oct 06 21:13:23 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 3a 38 4f 80 00 00 08 00
Oct 06 21:13:23 osmc kernel: print_req_error: critical target error, dev sda, sector 976768896
The kernel got the info that the hdd consists of 976773168 512 bytes sectors and has a problem to access sector 976768896.
Don’t know whether the addressing scheme starts with 0 or 1 and this means 976773168 is in- or outside the physical range.
Perhaps, you could provide some information after a reboot as well
sudo lsblk -a|paste-log and provide the URL, heresudo apt-get install smartmontoolssudo smartctl -a /dev/sda |paste-log and provide the URL, heresudo fdisk -l|paste-log and provide the URL, heresudo lsusb -v|paste-log and provide the URL, here
If accessing the sector 976768896 is a valid operation (so, no kernel/software issue), something could be wrong with this hdd, at least the last sectors.
smartctl reports: 500,107,862,016 bytes and 512 bytes sector size -> 976773168 sectors
@sam_nazarko: Why the kernel tries to access sector 976773168 instead 976773168-1 assuming sector addressing starts with 0? It is outside physical boundaries, isn’t it?
I think missing udisks-glue is just a follow up by this situation.
So it’s an off-by-one error basically?
Instead of reading sectors 0 to 976773167 it reads from 1 976773168 and it gets an error at the last sector?
What can I do to fix this?
Can you try reformat the disk?
Sam
Thx to mod @dillthedog: There is a mistake in my previous post: The disk has 976773168 sectors but problem sector is 976768896 which is of course within a valid range.
You could search for bad blocks on this hdd as well.
(Windows: chkdsk /r)
I am now running a chkdsk /r but it’s taking a while because it goes file by file and there are 49904 files… Still assuming there is a bad sector, I’m assuming it’s not catastrophic since both W7 & Raspbian mount the HDD and I can access the files without problem. Isn’t there some way to force OSMC to mount a NTFS partition with a bad sector?
If you have a bad sector, then things are only likely to get worse.
Looking at the SMART report, I couldn’t see anything that points to a failing disk. There are no reallocated sectors and nothing has come close to failing.
It’s interesting that lsusb, smartctl and lsblk see the device but fdisk doesn’t seem to.
Rather than running a chkdsk on Windows, you could always use smartctl to run a smart test. They usually run in the background, so shouldn’t lock your system. Run either:
sudo smartctl -t short /dev/sda
or alternatively,
sudo smartctl -t long /dev/sda
which will clearly take longer to run but will be more thorough. You can see the result by running:
sudo smartctl -l selftest /dev/sda
1 Like
chkdsk /r ran for about 3 hours, scanned all 44k files and found no errors or bad sectors. the smartctl test has status “Completed without error”, with 782 hours lifetime remaining and LBA_of_first_error simply says “-”. So I don’t think the drive is bad.
What can I do now? Where do I go from here?
Please, provide a new log set but I’m also somewhat clueless how to continue. Others are welcome.
As already noted, the log shows these repeated messages:
Oct 06 21:13:23 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Oct 06 21:13:23 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
Oct 06 21:13:23 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x20 ASCQ=0x0
Oct 06 21:13:23 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 3a 38 4f 80 00 00 08 00
Oct 06 21:13:23 osmc kernel: print_req_error: critical target error, dev sda, sector 976768896
Unfortunately, it’s not clear if the source of these messages is also the cause of the disk’s reluctance to mount or just a side issue.
Searching around, this type of error message was being reported more than two years ago. For example: https://github.com/raspberrypi/linux/issues/1287 Unfortunately, the thread ends without resolution.
That said, it might still be power-related. I note that you’ve already used a powered hub but they can also sometimes be problematic. Was the original log taken with a directly-attached disk or was it attached via a hub? If directly attached, for completeness could you provide a log when using a hub?
Can you also tell us (a) if you’re using an official power supply for the Pi3B+ and (b) if you’re able to try a substitute power supply.
I’m using an official Raspberry Pi power supply with the output through the USB micro jack (I think it’s rated for 5.1V/2.5A). What substitute power supply should I try?
I will provide logs with the HDD powered through the powered hub.
However I have noticed that while the smartctl short test goes fine, the long test always stops at 90% and it says the test was “Aborted by the host” (while trying to examine with sudo smartctl -l selftest /dev/sda). Any idea how I can look more into this?
If you don’t have another Pi, then we’ll probably have to skip this option. That said, substitution of components is a useful technique for figuring out where a problem lies. So, if you could lay your hands on another USB disk, it would be interesting to know if the problem (ie both those error messages and failure to mount) persists.
Regarding the “Aborted by host” message, this was raised by @JimKnopf as a potential issue, and is occurring because the disk is being put into a standby/hibernate state. This issue is actually included on the smartmontools FAQ page, FAQ – smartmontools . There’s also a link from the FAQ answer to another page that contains nice little job to keep the disk from going to sleep.
I ran the tests again, but this time with the HDD through the powered USB Hub. Here are the logs:
https://paste.osmc.tv/obumecuneh
https://paste.osmc.tv/utilaqaloq
https://paste.osmc.tv/iwexecuvis
https://paste.osmc.tv/yucihuwomu
I also managed to get the read query script working so the HDD won’t go into standby. When the long smartctl SMART test is completed I will post the results.
Here is the SMART test result, the last one is the only extended that completed with a anti-stanby script from the smartmontools forum and it says completed without error. https://paste.osmc.tv/duhomuzibi
What now?
The journalctl -f output
-- Logs begin at Thu 2016-11-03 19:16:42 EET. --
Oct 13 08:46:42 osmc sudo[643]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 13 08:46:42 osmc mediacenter[318]: mv: failed to preserve ownership for '/boot/config.txt': Operation not permitted
Oct 13 08:46:42 osmc sudo[643]: pam_unix(sudo:session): session closed for user root
Oct 13 08:46:45 osmc systemd[1]: Time has been changed
Oct 13 08:46:45 osmc ntpd[470]: receive: Unexpected origin timestamp 0xdf6c0545.4b22dc1a does not match aorg 0000000000.00000000 from server@91.216.151.61 xmt 0xdf6c0545.b9a45b86
Oct 13 08:46:45 osmc systemd[506]: Time has been changed
Oct 13 08:46:45 osmc systemd[1]: apt-daily-upgrade.timer: Adding 44min 26.264131s random time.
Oct 13 08:46:45 osmc systemd[1]: apt-daily.timer: Adding 11h 37min 45.877114s random time.
Oct 13 08:47:01 osmc sudo[935]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/journalctl -f
Oct 13 08:47:01 osmc sudo[935]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
Oct 13 08:47:09 osmc kernel: usb 1-1.1.2.1: new high-speed USB device number 6 using dwc_otg
Oct 13 08:47:09 osmc kernel: usb 1-1.1.2.1: New USB device found, idVendor=125f, idProduct=a94a
Oct 13 08:47:09 osmc kernel: usb 1-1.1.2.1: New USB device strings: Mfr=1, Product=3, SerialNumber=2
Oct 13 08:47:09 osmc kernel: usb 1-1.1.2.1: Product: Portable HDD CH94
Oct 13 08:47:09 osmc kernel: usb 1-1.1.2.1: Manufacturer: ADATA
Oct 13 08:47:09 osmc kernel: usb 1-1.1.2.1: SerialNumber: 0350000028CE
Oct 13 08:47:09 osmc kernel: usb-storage 1-1.1.2.1:1.0: USB Mass Storage device detected
Oct 13 08:47:09 osmc kernel: scsi host0: usb-storage 1-1.1.2.1:1.0
Oct 13 08:47:10 osmc kernel: scsi 0:0:0:0: Direct-Access ADATA HDD CH94 PQ: 0 ANSI: 0
Oct 13 08:47:10 osmc kernel: sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Oct 13 08:47:10 osmc kernel: sd 0:0:0:0: [sda] Write Protect is off
Oct 13 08:47:10 osmc kernel: sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
Oct 13 08:47:10 osmc kernel: sd 0:0:0:0: [sda] No Caching mode page found
Oct 13 08:47:10 osmc kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Oct 13 08:47:10 osmc kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Oct 13 08:47:10 osmc kernel: sda: sda1
Oct 13 08:47:10 osmc kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Oct 13 08:47:12 osmc udisks-glue[378]: Device file /dev/sda inserted
Oct 13 08:47:12 osmc sudo[962]: osmc : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/hdparm -S 240 /dev/sda
Oct 13 08:47:12 osmc sudo[962]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 13 08:47:34 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Oct 13 08:47:34 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
Oct 13 08:47:34 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x20 ASCQ=0x0
Oct 13 08:47:34 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 3a 38 4f 80 00 00 08 00
Oct 13 08:47:34 osmc kernel: print_req_error: critical target error, dev sda, sector 976768896
Oct 13 08:47:34 osmc udisks-glue[378]: SG_IO: bad/missing sense data, sb[]: 70 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Oct 13 08:47:34 osmc udisks-glue[378]: /dev/sda:
Oct 13 08:47:34 osmc udisks-glue[378]: setting standby to 240 (20 minutes)
Oct 13 08:47:34 osmc sudo[962]: pam_unix(sudo:session): session closed for user root
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x20 ASCQ=0x0
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 3a 38 4f 80 00 00 08 00
Oct 13 08:47:45 osmc kernel: print_req_error: critical target error, dev sda, sector 976768896
Oct 13 08:47:45 osmc kernel: Buffer I/O error on dev sda1, logical block 122095856, async page read
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x20 ASCQ=0x0
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x8 08 00 00 00 08 00
Oct 13 08:47:45 osmc kernel: print_req_error: critical target error, dev sda, sector 0
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x20 ASCQ=0x0
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x8 08 00 00 00 08 00
Oct 13 08:47:45 osmc kernel: print_req_error: critical target error, dev sda, sector 0
Oct 13 08:47:45 osmc kernel: Buffer I/O error on dev sda, logical block 0, async page read
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x20 ASCQ=0x0
Oct 13 08:47:45 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x8 08 00 00 00 08 00
Oct 13 08:47:45 osmc kernel: print_req_error: critical target error, dev sda, sector 0
Oct 13 08:47:45 osmc kernel: Buffer I/O error on dev sda, logical block 0, async page read
Oct 13 08:47:45 osmc udisks-glue[378]: Device file /dev/sda1 inserted
Oct 13 08:47:45 osmc udisks-glue[378]: Device /dev/sda1 did not match any rules.
Oct 13 08:47:45 osmc udisks-glue[378]: brw-rw---- 1 root disk 8, 1 Oct 13 08:47 /dev/sda1
Oct 13 08:47:57 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Oct 13 08:47:57 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
Oct 13 08:47:57 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x20 ASCQ=0x0
Oct 13 08:47:57 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 3a 38 4f 80 00 00 08 00
Oct 13 08:47:57 osmc kernel: print_req_error: critical target error, dev sda, sector 976768896
Oct 13 08:48:08 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Oct 13 08:48:08 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
Oct 13 08:48:08 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x20 ASCQ=0x0
Oct 13 08:48:08 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 3a 38 4f 80 00 00 08 00
Oct 13 08:48:08 osmc kernel: print_req_error: critical target error, dev sda, sector 976768896
Oct 13 08:48:08 osmc kernel: Buffer I/O error on dev sda1, logical block 122095856, async page read
Oct 13 08:48:08 osmc udisks-glue[378]: blkid:
Oct 13 08:48:08 osmc udisks-glue[378]: Showing information for /org/freedesktop/UDisks/devices/sda1
Oct 13 08:48:08 osmc udisks-glue[378]: native-path: /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
Oct 13 08:48:08 osmc udisks-glue[378]: device: 8:1
Oct 13 08:48:08 osmc udisks-glue[378]: device-file: /dev/sda1
Oct 13 08:48:08 osmc udisks-glue[378]: presentation: /dev/sda1
Oct 13 08:48:08 osmc udisks-glue[378]: by-id: /dev/disk/by-id/usb-ADATA_HDD_CH94_0350000028CE-0:0-part1
Oct 13 08:48:08 osmc udisks-glue[378]: by-path: /dev/disk/by-path/platform-3f980000.usb-usb-0:1.1.2.1:1.0-scsi-0:0:0:0-part1
Oct 13 08:48:08 osmc udisks-glue[378]: detected at: Sat Oct 13 08:47:45 2018
Oct 13 08:48:08 osmc udisks-glue[378]: system internal: 0
Oct 13 08:48:08 osmc udisks-glue[378]: removable: 0
Oct 13 08:48:08 osmc udisks-glue[378]: has media: 1 (detected at Sat Oct 13 08:47:45 2018)
Oct 13 08:48:08 osmc udisks-glue[378]: detects change: 0
Oct 13 08:48:08 osmc udisks-glue[378]: detection by polling: 0
Oct 13 08:48:08 osmc udisks-glue[378]: detection inhibitable: 0
Oct 13 08:48:08 osmc udisks-glue[378]: detection inhibited: 0
Oct 13 08:48:08 osmc udisks-glue[378]: is read only: 0
Oct 13 08:48:08 osmc udisks-glue[378]: is mounted: 0
Oct 13 08:48:08 osmc udisks-glue[378]: mount paths:
Oct 13 08:48:08 osmc udisks-glue[378]: mounted by uid: 0
Oct 13 08:48:08 osmc udisks-glue[378]: presentation hide: 0
Oct 13 08:48:08 osmc udisks-glue[378]: presentation nopolicy: 0
Oct 13 08:48:08 osmc udisks-glue[378]: presentation name:
Oct 13 08:48:08 osmc udisks-glue[378]: presentation icon:
Oct 13 08:48:08 osmc udisks-glue[378]: automount hint:
Oct 13 08:48:08 osmc udisks-glue[378]: size: 500104691712
Oct 13 08:48:08 osmc udisks-glue[378]: block size: 512
Oct 13 08:48:08 osmc udisks-glue[378]: job underway: no
Oct 13 08:48:08 osmc udisks-glue[378]: usage:
Oct 13 08:48:08 osmc udisks-glue[378]: type:
Oct 13 08:48:08 osmc udisks-glue[378]: version:
Oct 13 08:48:08 osmc udisks-glue[378]: uuid:
Oct 13 08:48:08 osmc udisks-glue[378]: label:
Oct 13 08:48:08 osmc udisks-glue[378]: partition:
Oct 13 08:48:08 osmc udisks-glue[378]: part of: /org/freedesktop/UDisks/devices/sda
Oct 13 08:48:08 osmc udisks-glue[378]: scheme:
Oct 13 08:48:08 osmc udisks-glue[378]: number: 1
Oct 13 08:48:08 osmc udisks-glue[378]: type:
Oct 13 08:48:08 osmc udisks-glue[378]: flags:
Oct 13 08:48:08 osmc udisks-glue[378]: offset: 1048576
Oct 13 08:48:08 osmc udisks-glue[378]: alignment offset: 0
Oct 13 08:48:08 osmc udisks-glue[378]: size: 500104691712
Oct 13 08:48:08 osmc udisks-glue[378]: label:
Oct 13 08:48:08 osmc udisks-glue[378]: uuid:
And the udevadm monitor output:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[33.920280] change /devices/platform/regulatory.0 (platform)
UDEV [33.923848] change /devices/platform/regulatory.0 (platform)
KERNEL[37.120307] change /devices/platform/regulatory.0 (platform)
UDEV [37.125148] change /devices/platform/regulatory.0 (platform)
KERNEL[39.081779] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1 (usb)
KERNEL[39.082022] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0 (usb)
KERNEL[39.087579] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0 (scsi)
KERNEL[39.087735] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/scsi_host/host0 (scsi_host)
UDEV [39.375393] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1 (usb)
UDEV [39.379392] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0 (usb)
UDEV [39.381488] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0 (scsi)
UDEV [39.385337] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/scsi_host/host0 (scsi_host)
KERNEL[40.160784] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0 (scsi)
KERNEL[40.160884] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0 (scsi)
KERNEL[40.160935] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/scsi_disk/0:0:0:0 (scsi_disk)
KERNEL[40.160989] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/scsi_device/0:0:0:0 (scsi_device)
KERNEL[40.161210] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/bsg/0:0:0:0 (bsg)
KERNEL[40.163145] add /devices/virtual/bdi/8:0 (bdi)
UDEV [40.164103] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0 (scsi)
UDEV [40.165692] add /devices/virtual/bdi/8:0 (bdi)
KERNEL[40.172512] add /module/sg (module)
KERNEL[40.172605] add /class/scsi_generic (class)
KERNEL[40.173281] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/scsi_generic/sg0 (scsi_generic)
UDEV [40.173447] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0 (scsi)
UDEV [40.175246] add /module/sg (module)
UDEV [40.176187] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/scsi_disk/0:0:0:0 (scsi_disk)
UDEV [40.178546] add /class/scsi_generic (class)
UDEV [40.179096] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/scsi_device/0:0:0:0 (scsi_device)
UDEV [40.180223] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/bsg/0:0:0:0 (bsg)
UDEV [40.180378] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/scsi_generic/sg0 (scsi_generic)
KERNEL[40.191203] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/block/sda (block)
KERNEL[40.191450] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1 (block)
UDEV [41.735596] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/block/sda (block)
UDEV [75.277256] add /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2.1/1-1.1.2.1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1 (block)