Thank you for your donation!


Problem: Installed 6.x - USB media not working (ARM6)
#1
Hi There,

Just having a bit of trouble with USB media on both v6.0 and v6.1 of moode. In both cases I've been trying to diagnose the issue on a fresh install with both an externally powered hard drive as well as a USB flash drive, and both devices DO work if I install a fresh version of v5.3.1. I'm using a Raspberry Pi Zero W.

I've tried to troubleshoot the problem myself, working my way through this thread in particular: http://moodeaudio.org/forum/showthread.php?tid=894 so I'll share my findings thus far.

- if I connect one of the drives and run MPD Update, 'USB' is listed in the media browser, but the folder is empty and likewise nothing is listed in the filter browser.
cat /var/log/mpd/log also returns nothing.
- if I run MPD Re-Gen instead the 'USB' listing disappears, and the mpd log simply lists "Aug 25 23:34 : update: updating SDCARD/Stereo Test/LRMonoPhase4.flac"

- the syslog contains this:

Code:
Aug 25 23:24:08 moode kernel: [  979.744877] usb 1-1: USB disconnect, device number 2
Aug 25 23:24:14 moode kernel: [  985.695276] Indeed it is in host mode hprt0 = 00021501
Aug 25 23:24:14 moode kernel: [  985.905149] usb 1-1: new high-speed USB device number 3 using dwc_otg
Aug 25 23:24:14 moode kernel: [  985.905323] Indeed it is in host mode hprt0 = 00001101
Aug 25 23:24:14 moode kernel: [  986.146080] usb 1-1: New USB device found, idVendor=0781, idProduct=5572, bcdDevice= 1.26
Aug 25 23:24:14 moode kernel: [  986.146100] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 25 23:24:14 moode kernel: [  986.146109] usb 1-1: Product: Cruzer Switch
Aug 25 23:24:14 moode kernel: [  986.146118] usb 1-1: Manufacturer: SanDisk
Aug 25 23:24:14 moode kernel: [  986.146125] usb 1-1: SerialNumber: 20052444311AFB219998
Aug 25 23:24:14 moode kernel: [  986.151095] usb-storage 1-1:1.0: USB Mass Storage device detected
Aug 25 23:24:14 moode kernel: [  986.167580] scsi host0: usb-storage 1-1:1.0
Aug 25 23:24:14 moode mtp-probe: checking bus 1, device 3: "/sys/devices/platform/soc/20980000.usb/usb1/1-1"
Aug 25 23:24:14 moode mtp-probe: bus: 1, device: 3 was not an MTP device
Aug 25 23:24:14 moode mtp-probe: checking bus 1, device 3: "/sys/devices/platform/soc/20980000.usb/usb1/1-1"
Aug 25 23:24:14 moode mtp-probe: bus: 1, device: 3 was not an MTP device
Aug 25 23:24:15 moode kernel: [  987.186672] scsi 0:0:0:0: Direct-Access     SanDisk  Cruzer Switch    1.26 PQ: 0 ANSI: 6
Aug 25 23:24:15 moode kernel: [  987.190814] sd 0:0:0:0: [sda] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
Aug 25 23:24:15 moode kernel: [  987.191340] sd 0:0:0:0: Attached scsi generic sg0 type 0
Aug 25 23:24:15 moode kernel: [  987.192090] sd 0:0:0:0: [sda] Write Protect is off
Aug 25 23:24:15 moode kernel: [  987.192108] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Aug 25 23:24:15 moode kernel: [  987.192895] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Aug 25 23:24:15 moode kernel: [  987.225632]  sda: sda1
Aug 25 23:24:15 moode kernel: [  987.230068] sd 0:0:0:0: [sda] Attached SCSI removable disk
Aug 25 23:24:15 moode systemd-udevd[2380]: Process 'udisks-part-id /dev/sda' terminated by signal SEGV.
Aug 25 23:24:15 moode systemd-udevd[2380]: Failed to wait for spawned command 'udisks-part-id /dev/sda': Input/output error
Aug 25 23:24:16 moode systemd-udevd[2366]: Process 'udisks-part-id /dev/sda1' terminated by signal SEGV.
Aug 25 23:24:16 moode systemd-udevd[2366]: Failed to wait for spawned command 'udisks-part-id /dev/sda1': Input/output error

so to continue following along with the other thread, the output of lsusb DOES list my drive, but it is not mounted in /media

if I try to mount the drive manually (to /tmp/mydrive) as suggested on page 2, it works:

Code:
pi@moode:~ $ sudo mkdir /media/mydrive
pi@moode:~ $ sudo mount /dev/sda1 /media/mydrive/
pi@moode:~ $ mount|grep sda
/dev/sda1 on /media/mydrive type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)

and from the syslog:


Code:
Aug 25 23:31:41 moode kernel: [ 1433.033016] fuse init (API version 7.27)
Aug 25 23:31:41 moode systemd[1]: Mounting FUSE Control File System...
Aug 25 23:31:41 moode ntfs-3g[2991]: Version 2017.3.23AR.3 integrated FUSE 28
Aug 25 23:31:41 moode ntfs-3g[2991]: Mounted /dev/sda1 (Read-Write, label "DAVE", NTFS 3.1)
Aug 25 23:31:41 moode ntfs-3g[2991]: Cmdline options: rw
Aug 25 23:31:41 moode ntfs-3g[2991]: Mount options: allow_other,nonempty,relatime,rw,fsname=/dev/sda1,blkdev,blksize=4096
Aug 25 23:31:41 moode ntfs-3g[2991]: Ownership and permissions disabled, configuration type 7
Aug 25 23:31:41 moode systemd[1]: Mounted FUSE Control File System.

and then if I run MPD Update... we have music in the library! But I'd still like to get to the bottom of what's going on here and restore the plug 'n' play capabilities if possible.

Thanks very much Smile
Dave

EDIT: my apologies for the duplicate, but it appears I'm having the same issue as Wigwam here: http://moodeaudio.org/forum/showthread.php?tid=1662
Reply
#2
@drivedesigned

Ah, there's the smoking gun...udisk isn't mounting your drive, just as Tim speculated in his post on the other thread http://moodeaudio.org/forum/showthread.p...5#pid12545

Code:
Aug 25 23:24:15 moode systemd-udevd[2380]: Process 'udisks-part-id /dev/sda' terminated by signal SEGV.
Aug 25 23:24:15 moode systemd-udevd[2380]: Failed to wait for spawned command 'udisks-part-id /dev/sda': Input/output error
Aug 25 23:24:16 moode systemd-udevd[2366]: Process 'udisks-part-id /dev/sda1' terminated by signal SEGV.
Aug 25 23:24:16 moode systemd-udevd[2366]: Failed to wait for spawned command 'udisks-part-id /dev/sda1': Input/output error


Sorry, I don't have an answer off the top of my head and I won't have time to rummage through Google's closet until late today. Perhaps Tim will have another suggestion in the meantime.

Regards,
Kent
Reply
#3
Oops, I compiled disks-glue on an arm7 Pi and it looks like its segfaulting on arm6 :-0

An arm6 binary should work on both arm6 and arm7. Try the procedure below and let me know how it goes.

Install arm6 binary
Code:
sudo cp /usr/bin/udisks-glue ./udisks-glue-arm7
sudo wget http://moodeaudio.org/test/udisks-glue-arm6
sudo mv ./udisks-glue-arm6 /usr/bin/udisks-glue
sudo chmod 0755 /usr/bin/udisks-glue
sudo reboot

Verify its running 
Code:
pgrep udisks-glue

Plug in USB drive and verify its auto-mounted
Code:
ls /media
Reply
#4
(08-26-2019, 12:50 PM)Tim Curtis Wrote: Verify its running 
Code:
pgrep udisks-glue

OK, carried out the installation process but after reboot this returns nothing.

EDIT: and if I just try to run udisks-glue in the terminal it says "Unable to find the configuration file"

EDIT2: if I cat /etc/udisks-glue.conf sure enough the file exists...
Reply
#5
Look at the launch string for disks-glue in /etc/rc.local. It needs a --config= param
Reply
#6
(08-27-2019, 01:17 AM)Tim Curtis Wrote: Look at the launch string for disks-glue in /etc/rc.local. It needs a --config= param

in there we have:


Code:
/usr/bin/udisks-glue --config=/etc/udisks-glue.conf > /dev/null 2>&1
/var/www/command/worker.php > /dev/null 2>&1
Reply
#7
Looking into this a bit further I'm getting same result as you on a 0W with either the arm6 or arm7 binary. It appears to be some sort of fault with the udisks service, possibly related to udisks-glue ??

Code:
pi@rp2:~ $ sudo systemctl status udisks.service
● udisks.service - Disk Manager (legacy version)
  Loaded: loaded (/lib/systemd/system/udisks.service; static; vendor preset: enabled)
  Active: failed (Result: signal) since Mon 2019-08-26 21:32:46 EDT; 1min 3s ago
    Docs: man:udisks(7)
 Process: 1522 ExecStart=/usr/lib/udisks/udisks-daemon --no-debug (code=killed, signal=SEGV)
Main PID: 1522 (code=killed, signal=SEGV)

Aug 26 21:32:46 rp2 systemd[1]: Starting Disk Manager (legacy version)...
Aug 26 21:32:46 rp2 systemd[1]: udisks.service: Main process exited, code=killed, status=11/SEGV
Aug 26 21:32:46 rp2 systemd[1]: udisks.service: Failed with result 'signal'.
Aug 26 21:32:46 rp2 systemd[1]: Failed to start Disk Manager (legacy version).

Note that the udisks-glue package was not carried forward by the RPi Foundation from Stretch to Buster and so it required manual compilation and integration for moOde 6 and works perfectly on arm7 but apparently there are issues on arm6.

-Tim
Reply
#8
(08-27-2019, 01:50 AM)Tim Curtis Wrote: Looking into this a bit further I'm getting same result as you on a 0W with either the arm6 or arm7 binary. It appears to be some sort of fault with the udisks service, possibly related to udisks-glue ??

Code:
pi@rp2:~ $ sudo systemctl status udisks.service
● udisks.service - Disk Manager (legacy version)
  Loaded: loaded (/lib/systemd/system/udisks.service; static; vendor preset: enabled)
  Active: failed (Result: signal) since Mon 2019-08-26 21:32:46 EDT; 1min 3s ago
    Docs: man:udisks(7)
 Process: 1522 ExecStart=/usr/lib/udisks/udisks-daemon --no-debug (code=killed, signal=SEGV)
Main PID: 1522 (code=killed, signal=SEGV)

Aug 26 21:32:46 rp2 systemd[1]: Starting Disk Manager (legacy version)...
Aug 26 21:32:46 rp2 systemd[1]: udisks.service: Main process exited, code=killed, status=11/SEGV
Aug 26 21:32:46 rp2 systemd[1]: udisks.service: Failed with result 'signal'.
Aug 26 21:32:46 rp2 systemd[1]: Failed to start Disk Manager (legacy version).

Note that the udisks-glue package was not carried forward by the RPi Foundation from Stretch to Buster and so it required manual compilation and integration for moOde 6 and works perfectly on arm7 but apparently there are issues on arm6.

-Tim

Interesting... thank you. Unfortunate decision by the RPi Foundation by the sounds of things!
Reply
#9
To be fair, the github repo of the original udisks-glue hasn't been touched in 6 years and the sources apparently in 8 years. I think we've been lucky it's worked for so many releases of Debian -> Raspbian. The Debian package search page doesn't show any hits on udisks-glue after Jessie (oldoldstable) and sid.

The irony is that udisks-glue itself was created to replace functionality in the defunct hal project which had preceded it.
Reply
#10
(08-27-2019, 02:33 AM)TheOldPresbyope Wrote: To be fair, the github repo of the original udisks-glue hasn't been touched in 6 years and the sources apparently in 8 years. I think we've been lucky it's worked for so many releases of Debian -> Raspbian. The Debian package search page doesn't show any hits on udisks-glue after Jessie (oldoldstable) and sid.

The irony is that udisks-glue itself was created to replace functionality in the defunct hal project which had preceded it.

oooff, well there you go, that probably is fair then Blush

so I wonder what the most sensible way forward is? I was thinking of trying udevil as suggested here: https://www.raspberrypi.org/forums/viewt...?p=1514984 but not sure how that might effect any future in-place updates to moode.
Reply


Forum Jump: