Volumio Debian Buster Beta - Raspi images debugging

Great! Nice trick, should ensure you don’t have to edit multiple config files (Airplay/MPD/Spotify)




Not sure if I should build a new image or wait for an “official” beta. I just had a look and it’s close to ~1 year from the first pi Buster beta 3.000 image! :astonished::worried:

Updating to Debian 10 is a big pain if you ask me. I had several weeks to update my server from 9 to 10. And some things (CounterStrike for example) are still not running!
And this is not the first update, i updated from 6 to 7, to 8 to 9 and now to 10. All more or less smooth, only had problems from 9 to 10.

DSP settings for Allo Piano 2.1 are missing in beta 3.015. (e.g. Dual Mono mode). Is it likely that this will be become available again ?
Does ALLO has to contribute something to Volumio or the kernel ?

BR
Josef

Probably something wrong with the Volumio parsing code – can you open up a console and check what what amixer reports?

# Use aplay -l to figure out the correct card number <n>
amixer -c <n>

Thank you - it seems the card is not recognized in any way - though set to Piano 2.1 in Volumio

aplay - l outputs:

volumio@piano3:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3


volumio@piano3:~$ amixer -c 0
Simple mixer control ‘HDMI’,0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined
Playback channels: Mono
Limits: Playback -10239 - 400
Mono: Playback 0 [96%] [0.00dB] [on]


volumio@piano3:~$ amixer -c 1
Simple mixer control ‘Headphone’,0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined
Playback channels: Mono
Limits: Playback -10239 - 400
Mono: Playback -2000 [77%] [-20.00dB] [on]


amixer -c <2 or higher> outputs “invalid device”

Does that help anyhow ?

BR
Josef

Indeed, it doesn’t see your DAC. Can you check what entry is in your /boot/config.txt

cat /boot/config.txt
cat /boot/userconfig.txt

Config.txt:

initramfs volumio.initrd
gpu_mem=32
max_usb_current=1
dtparam=audio=on
audio_pwm_mode=2
dtparam=i2c_arm=on
disable_splash=1
hdmi_force_hotplug=1
enable_uart=1

include userconfig.txt

Volumio i2s setting below: do not alter

dtoverlay=allo-piano-dac-plus-pcm512x-audio


userconfig.txt:

dtoverlay=pi3-miniuart-bt

I installed Volumio3 version 0.015 [Raspberry Pi Volumio-3.015-2021-01-03-pi] on a Rasperry 4B with Allo Digi One and touch display. I had to fix the alsa device index as suggested by @Damien_Servant.
Now i experience a problem with the USB automounting.
udisk sees the device but it is not mounted.

udisksctl status
MODEL                     REVISION  SERIAL               DEVICE
SE16G                               0x79a488e6           mmcblk0
Samsung Flash Drive       1100      0374720070005130     sda

ls -l /media/
total 0

I did a manuell mount with sudo udisksctl mount -b /dev/sda1

But that messed up the permissions:

Failed to register /var/lib/mpd/music/USB/volumio: inotify_add_watch() has failed: Permission denied
Failed to register /var/lib/mpd/music/USB/root: inotify_add_watch() has failed: Permission denied

ls -l /mnt/USB/
total 4
drwxr-x—+ 3 root root 1024 Feb 22 09:06 root
drwxr-x—+ 2 root root 1024 Feb 22 09:05 volumio

I reflashed the image and started over.
USB Device is not mounted.
How to best proceed?

Seems to look fine, could you share a debugging log to figure out why it’s not getting initialised?

USB device mounting is now taken care of by the Volumio Node process – Can you share some logs from a fresh reboot, and then try pluggin in the USB device?

log is:

http://logs.volumio.org/volumio/i33ApHb.html

Best Regards
Josef

Log directly after reboot:

http://logs.volumio.org/volumio/icjKHG2.html

Inserted USB Stick:

http://logs.volumio.org/volumio/fEhGjMM.html

TIA

I also see this error version 3.015 failed to scan the music library on the portable hard drive.

It destroyed all of my music files. frustrating!
Thanks and please check and correct!

1 Like

@mac
Are you sure your files are destroyed?
Hoe did you test this?
The issue i have is that an extenal drive is not mounted.
This is why you are not seeing any files.
You could attach the drive to another computer or try mounting it manually in an ssh terminal.

The one thing i am seeing that might or might not be an issue is:

 sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00

I will investigate further.

For comparison i inserted the USB Drive in a volumio 2.8 Device while running
journalctl -f

it shows:

   Feb 23 09:42:11 volumio-tinke kernel: usb 1-1.4: new high-speed USB device number 5 using dwc2
   Feb 23 09:42:11 volumio-tinke kernel: usb 1-1.4: New USB device found, idVendor=090c, idProduct=1000
   Feb 23 09:42:11 volumio-tinke kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3   
   Feb 23 09:42:11 volumio-tinke kernel: usb 1-1.4: Product: Flash Drive
   Feb 23 09:42:11 volumio-tinke kernel: usb 1-1.4: Manufacturer: Samsung
   Feb 23 09:42:11 volumio-tinke kernel: usb 1-1.4: SerialNumber: 0374720070005130
   Feb 23 09:42:11 volumio-tinke kernel: usb-storage 1-1.4:1.0: USB Mass Storage device detected
   Feb 23 09:42:11 volumio-tinke kernel: scsi host1: usb-storage 1-1.4:1.0
   Feb 23 09:42:15 volumio-tinke kernel: scsi 1:0:0:0: Direct-Access     Samsung  Flash Drive      1100 PQ: 0 ANSI: 6
   Feb 23 09:42:15 volumio-tinke kernel: sd 1:0:0:0: [sdb] 501253132 512-byte logical blocks: (257 GB/239 GiB)
   Feb 23 09:42:15 volumio-tinke kernel: sd 1:0:0:0: [sdb] Write Protect is off
   Feb 23 09:42:15 volumio-tinke kernel: sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
   Feb 23 09:42:15 volumio-tinke kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
   Feb 23 09:42:15 volumio-tinke kernel:  sdb: sdb1
   Feb 23 09:42:15 volumio-tinke kernel: sd 1:0:0:0: [sdb] Attached SCSI removable disk
   Feb 23 09:42:15 volumio-tinke udisks-glue[681]: Device file /dev/sdb inserted
   Feb 23 09:42:15 volumio-tinke udisks-glue[681]: Device file /dev/sdb1 inserted
   Feb 23 09:42:15 volumio-tinke udisks-glue[681]: Trying to automount /dev/sdb1...
   Feb 23 09:42:16 volumio-tinke udisks-glue[681]: Successfully automounted /dev/sdb1 at /media/Samsung USB
   Feb 23 09:42:16 volumio-tinke udisks-glue[681]: Device file /dev/sdb1 mounted at /media/Samsung USB

Note no Synchronize Cache Error there.
So if the mount is working on 014 it could be connected to the kernel version.

I’m sure of this because: I tried lots of different hard drives like: 32 G, 1T, 2 T and 4T.

after plugging into Pi 4 4g with VOlumio 30.015:
1- press scan and it doesn’t scan music files.
2- I took out the hard drive, put the USB into the computer, and it couldn’t recognize the USB, it forced to reformat the hard drive.

I fixed it with Windows 10, but it didn’t work. I have to reformat the USB.
Note: Volumio 3.014 does not happen this problem!
thanks

When you plug in the drive into your Pi4 did you determ it was mounted?
You can test this with an ssh session or look at your log created in /dev
in # mount --------------- section you should see a mount to /media.
When the drive is not mounted the Volumio wont do anything to your drive as it can not access it.
What filesystem was the disk?
Windows can only read NTFS, FAT32 und FAT16 AFAIK.

you do not believe me,
Please experiment with your USB!

thạnk you very much!

It seems to me there was still a handle open when you pulled out the disk, that can definitely cause drive corruption. Just out of interest, how did you format (FAT/NTFS/other) the USB drive before plugging it in your Pi and what kind of files were on there?

I have an 8G USB drive on my desk (no need to look for another), I just imaged 3.015 on a fresh SD card for a Pi2, so I’ll test that first. :slight_smile:

My test case will be:

  • Pi2 with image 3.015
  • USB drive (FAT32 formatted) with a Dire Straits album in FLAC
  • No plugins

Unfortunately I only have one Pi4 and it’s running as a data node in my ELK stack, I might be able to quickly test a thing or two, given I have the right parameters :wink:

Quick test, means quick results…

The log entries I found were:

Feb 23 15:05:08 volumiotest kernel: usb 1-1.4: new high-speed USB device number 4 using dwc_otg
Feb 23 15:05:09 volumiotest kernel: usb 1-1.4: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 1.00
Feb 23 15:05:09 volumiotest kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 23 15:05:09 volumiotest kernel: usb 1-1.4: Product: DataTraveler 3.0
Feb 23 15:05:09 volumiotest kernel: usb 1-1.4: Manufacturer: Kingston
Feb 23 15:05:09 volumiotest kernel: usb 1-1.4: SerialNumber: xxx
Feb 23 15:05:09 volumiotest kernel: usb-storage 1-1.4:1.0: USB Mass Storage device detected
Feb 23 15:05:09 volumiotest kernel: scsi host0: usb-storage 1-1.4:1.0
Feb 23 15:05:09 volumiotest kernel: usbcore: registered new interface driver uas

Feb 23 15:05:10 volumiotest kernel: scsi 0:0:0:0: Direct-Access     Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
Feb 23 15:05:10 volumiotest kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 23 15:05:11 volumiotest kernel: sd 0:0:0:0: [sda] 15364416 512-byte logical blocks: (7.87 GB/7.33 GiB)
Feb 23 15:05:11 volumiotest kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 23 15:05:11 volumiotest kernel: sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
Feb 23 15:05:11 volumiotest kernel: sd 0:0:0:0: [sda] No Caching mode page found
Feb 23 15:05:11 volumiotest kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Feb 23 15:05:11 volumiotest kernel:  sda: sda1
Feb 23 15:05:11 volumiotest kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk

Nothing seemed to happen in Volumio after I rebuilt the database. I couldn’t list the dir tree on sda1

volumio@volumiotest:/media$ tree /dev/sda1
/dev/sda1 [error opening dir]

0 directories, 0 files

Nor were any directories visible for /mnt/USB

volumio@volumiotest:/media$ ll /mnt/USB/
total 2
drwxrwxrwx 2 root root    3 Dec 21 17:31 .
drwxrwxrwx 1 root root 1024 Jan  1  1970 ..

After re-inserting the drive in my Windows PC I saw the pop-up that errors were found on the disk, but I could still browse its contents:

E:\>dir
 Volume in drive E is DATA
 Volume Serial Number is xxx

 Directory of E:\

07-10-2020  08:28    <DIR>          Dire Straits - Brothers in Arms
               0 File(s)              0 bytes
               1 Dir(s)   6.837.096.448 bytes free