01-14-2020, 11:43 PM
@Smallwire
No, this version---6.4.0---works just fine with an external USB drive.
You said you have an RPi3 (model A, B, B+?) with a Katana DAC on it. The devmon fix isn't necessary because udisks-glue works fine with this model.
You said "My drive should be an internally powered drive." Does this mean your drive has its own power supply?
Tim's point is that some drives draw too much current to be powered by the Pi via the USB cable so that either a self-powered disk or a disk connected via a powered USB hub is required. If a hard disk, the worst case is during spin up. The USB interface could be working but the disk itself not responding properly.
The disk should be seen in a variety of system output.
For example, considering a small USB-connected SSD on one of my moOde players, hostname moodeLR:
1. it's a partition in fdisk output
2. It shows up in /var/log/syslog (similar lines will be found in dmesg output)
Note that messages are output to syslog asynchronously so may not be in strictly sequential order.
3. It's in the list of filesystems in Linux
I'm curious if you see one or more "Mass Storage" bInterface Class occurences in the voluminous output from this lsusb command (where I took the vendorID:deviceID values from your lsusb output and assumed your Pi's hostname is "moode")
Regards,
Kent
No, this version---6.4.0---works just fine with an external USB drive.
You said you have an RPi3 (model A, B, B+?) with a Katana DAC on it. The devmon fix isn't necessary because udisks-glue works fine with this model.
You said "My drive should be an internally powered drive." Does this mean your drive has its own power supply?
Tim's point is that some drives draw too much current to be powered by the Pi via the USB cable so that either a self-powered disk or a disk connected via a powered USB hub is required. If a hard disk, the worst case is during spin up. The USB interface could be working but the disk itself not responding properly.
The disk should be seen in a variety of system output.
For example, considering a small USB-connected SSD on one of my moOde players, hostname moodeLR:
1. it's a partition in fdisk output
Code:
pi@moodeLR:~ $ sudo fdisk -l
...bunch of moOde partitions...
...this one is mine...
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Disk model:
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x673b75df
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 250069679 250067632 119.2G b W95 FAT32
2. It shows up in /var/log/syslog (similar lines will be found in dmesg output)
Code:
pi@moodeLR:~ $ var /var/log/syslog
...tons of lines, then...
Jan 14 07:28:18 moodeLR kernel: [ 1.118405] scsi host0: uas
Jan 14 07:28:18 moodeLR kernel: [ 1.120011] scsi 0:0:0:0: Direct-Access JMicron 0223 PQ: 0 ANSI: 6
Jan 14 07:28:18 moodeLR kernel: [ 1.122129] sd 0:0:0:0: [sda] Spinning up disk...
...some more lines, then...
Jan 14 07:28:18 moodeLR kernel: [ 2.153402] sd 0:0:0:0: [sda] 250069680 512-byte logical blocks: (128 GB/119 GiB)
Jan 14 07:28:18 moodeLR kernel: [ 2.153416] sd 0:0:0:0: [sda] 4096-byte physical blocks
Jan 14 07:28:18 moodeLR kernel: [ 2.153737] sd 0:0:0:0: [sda] Write Protect is off
Jan 14 07:28:18 moodeLR kernel: [ 2.153750] sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08
Jan 14 07:28:18 moodeLR kernel: [ 2.154463] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 14 07:28:18 moodeLR kernel: [ 2.155471] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
Jan 14 07:28:18 moodeLR kernel: [ 2.175161] sda: sda1
Jan 14 07:28:18 moodeLR kernel: [ 2.179168] sd 0:0:0:0: [sda] Attached SCSI disk
Note that messages are output to syslog asynchronously so may not be in strictly sequential order.
3. It's in the list of filesystems in Linux
Code:
pi@moodeLR:~ $ mount
...lots of moOde filesystem partitions, then...
/dev/sda1 on /media/MUSIC type vfat (rw,nosuid,nodev,noexec,noatime,nodiratime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,errors=remount-ro,uhelper=udisks)
...
I'm curious if you see one or more "Mass Storage" bInterface Class occurences in the voluminous output from this lsusb command (where I took the vendorID:deviceID values from your lsusb output and assumed your Pi's hostname is "moode")
Code:
pi@moode:~ $ sudo lsusb -v -d 0480:0202
Regards,
Kent