Thank you for your donation!


Solved: External USB drive not detected under mOode 6.4.0
#1
Hi all,

I have come to this forum to see if anyone is able to shed some possible insight to the problem I have been experiencing. I have recently updated to mOode version 6.4.0. Since updating to this version, I have encountered a problem where my external USB drive cannot be detected, thus I am unable to play songs that I have stored on this drive through mOode Audio and I am only able to play via streaming radio sources. Oddly enough, I did not experience this issue on older versions (around version ~5-ish). 

Has anyone experienced similar issues where the external USB source cannot be detected? Could this be a software issue, or perhaps a hardware issue? 

I would like to add a few more details:
- I have a Pi3 with a Katana DAC on top of the Pi. 
- I am reluctant to say it is an issue with my external USB drive, since I can recognize it on my computer. 

Any assistance/insight is greatly appreciated. Thank you.
Reply
#2
For a start, with your USB drive plugged in, reboot then post the output from the commands below.

Code:
lsusb

ls -l /media
Reply
#3
(01-14-2020, 04:00 AM)Tim Curtis Wrote: For a start, with your USB drive plugged in, reboot then post the output from the commands below.

Code:
lsusb

ls -l /media

Hi Tim,

This is the output that I get after issuing those commands:

Code:
$ lsusb
Bus 001 Device 004: ID 0480:0202 Toshiba America Inc 
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ ls -l /media
total 0

I can see the external drive through the command (Toshiba) but it is not detected on the mOode UI.
Reply
#4
Did you update mpd database ?
Reply
#5
(01-14-2020, 06:00 PM)Smallwire Wrote:
(01-14-2020, 04:00 AM)Tim Curtis Wrote: For a start, with your USB drive plugged in, reboot then post the output from the commands below.

Code:
lsusb

ls -l /media

Hi Tim,

This is the output that I get after issuing those commands:

Code:
$ lsusb
Bus 001 Device 004: ID 0480:0202 Toshiba America Inc 
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ ls -l /media
total 0

I can see the external drive through the command (Toshiba) but it is not detected on the mOode UI.

The empty /media directory indicates the drive was not auto-mounted by udisks-glue.

Couple thoughts:

- udisks-glue does not run on arm6 platforms (Pi-Zero, 1B). You can switch to devmon auto-mounter in System Config
- the drive needs to have a disk label to be auto-mounted
- some drives need to be externally powered
Reply
#6
(01-14-2020, 06:21 PM)TookaFace Wrote: Did you update mpd database ?

Yes, I have.
Reply
#7
(01-14-2020, 06:27 PM)Tim Curtis Wrote:
(01-14-2020, 06:00 PM)Smallwire Wrote:
(01-14-2020, 04:00 AM)Tim Curtis Wrote: For a start, with your USB drive plugged in, reboot then post the output from the commands below.

Code:
lsusb

ls -l /media

Hi Tim,

This is the output that I get after issuing those commands:

Code:
$ lsusb
Bus 001 Device 004: ID 0480:0202 Toshiba America Inc 
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ ls -l /media
total 0

I can see the external drive through the command (Toshiba) but it is not detected on the mOode UI.

The empty /media directory indicates the drive was not auto-mounted by udisks-glue.

Couple thoughts:

- udisks-glue does not run on arm6 platforms (Pi-Zero, 1B). You can switch to devmon auto-mounter in System Config
- the drive needs to have a disk label to be auto-mounted
- some drives need to be externally powered

I see, thanks for your reply. You're right, I do not see the drive under /media. Sad

In response to your thoughts:
- So, I've tried Devmon today, and that still did not work. 
- I also gave it a disk label via ntfslabel on my computer (since it is an NTFS drive). Even after doing that, I couldn't get it to show up on my Pi under /media, or even looking at /dev/disk/by-label (and the other options)...
- My drive should be an internally powered drive. 

I also tried looking at the mpd logs (/var/logs/mpd/log) and system logs (/var/logs/syslog), but didn't really see anything pertaining to my drive there either. Though, the system log did mention that my "Toshiba" drive was detected but nothing more. 

Is it the case that I simply cannot listen to the music through an external source on this version, then? Is there some sort of manual mounting procedure or something?
Reply
#8
@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


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
Reply
#9
A nice simple command to list block devices is 'lsblk'.

As Kent is saying OP, if you can't see the device listed in the output lsusb or lsblk then it's most likely that the disk requires more power to spin up than the Pi or it's power supply can supply.
Reply
#10
Doh. I keep forgetting lsblk (in my defense, it was created long after I "learned" Linux). As @vinnn says, it's nice and simple.

Adding it to my previous post

Code:
pi@moodeLR:~ $ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    0 119.2G  0 disk
└─sda1        8:1    0 119.2G  0 part /media/MUSIC
sdb           8:16   1   244M  0 disk
└─sdb1        8:17   1   243M  0 part /media/CorePlus
mmcblk0     179:0    0  14.9G  0 disk
├─mmcblk0p1 179:1    0   256M  0 part /boot
└─mmcblk0p2 179:2    0  14.6G  0 part /


sda1 is the sole partition on my USB SSD and sdb1 is the sole partition on a USB memory stick.

Neat!

Regards,
Kent
Reply


Forum Jump: