Hi,
I got this error today when I tried to play some web radio. I also tried to reboot but it was the same:
Then, from Playback Options, I selected again the same device and the error disappeared. Here is the log:
2 Likes
Tidal appears to be absent on 3.114. Under settings it shows only that Tidal Connect is active, there is no facility to log into Tidal and also the Tidal Input on the main sources screen is absent. I tried Tidal Connect but Volumio does not show up in the list off Tidal Connect devices. All was OK on 3.111. Just reverted to 3.111 and everything is there and functioning. QoBuz seems similaray missing… RPI4 HifiBerry Digi
Tidal and Tidal Connect are working here on 3.114 (RPi 3 + Hifiberry Digi Pro +)
But where can i find the EQ?
1 Like
By the way, my PC has several ALSA devices, but Playback Options panel only shows two (with the same name). In other words, audio cards are recognized but not the single devices. Is that how it is intended to be?
volumio@volumioss:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 0: ALC1220 Analog [ALC1220 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 1: ALC1220 Digital [ALC1220 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
No, this must be an issue with the internal card definitions.
Please report x86 hardware configuration issues in this dedicated thread.
Note: I need hardware information!
1 Like
Hi
I am very exciting to see some progress on multiroom for Volumio. I have been waiting to see this come to reality for a while. Unfortunately, I have so far been unable to getting it to work. My goal is to have 3 RPi’s play in sync and to stream from my deezer app from the ipad via airplay.
I have one RPi connected via LAN and two on the wlan of my Fritzbox 5490. The ones connected via WLAN are within acceptable distance and should have good reception. I first tried grouping two devices at a time and play some webradio stations. unfortunately they stopped playing after 3 secs. Stop and restart would play another 3 secs.
Airplay never worked with multiroom and after trying multiroom airplay doesn’t even play anymore on a single device. I reported a log of when I was first playing a webradio (that worked) and then tried airplay on that same single device (in no group anymore) here. Don’t know if that is of any help. Unfortunately I had to move back to volumio2 for the time being because I need to be able to play music…
Ah one more thing, I didn’t managte to play music on my IQaudio Pi-DigiAMP+ at all. I plugged some small speakers in the headphone jack to test multiroom.
1 Like
Which device?
Please submit a log after you reproduced this problem, not one from another situation😉
I reported the problem there and added lspci and inxi-Fxxxz info.
Hi again
Volumio 3.114 installed
Can’t Access to my external Samsung T5 SSD
when everything is fine with my ex
rnal HDD
Did a full reinstall etc, the SSD
IS not detected or scanned
Here is the log
http://logs.volumio.org/volumiobuster/FC7xeqn.html
Thanks
JMiK
3 Likes
It is detected, according to the log:
Feb 14 10:11:59 volumio3 kernel: usb 1-1.2: New USB device found, idVendor=04e8, idProduct=61f5, bcdDevice= 1.00
Oct 16 12:03:28 volumio3 kernel: usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Oct 16 12:03:28 volumio3 kernel: usb 1-1.2: Product: Portable SSD T5
Oct 16 12:03:28 volumio3 kernel: usb 1-1.2: Manufacturer: Samsung
Oct 16 12:03:28 volumio3 kernel: usb 1-1.2: SerialNumber: 12345688D611
Oct 16 12:03:28 volumio3 kernel: scsi host0: uas
Oct 16 12:03:28 volumio3 kernel: scsi 0:0:0:0: Direct-Access Samsung Portable SSD T5 0 PQ: 0 ANSI: 6
Oct 16 12:03:28 volumio3 kernel: sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Oct 16 12:03:28 volumio3 kernel: sd 0:0:0:0: [sda] Write Protect is off
Oct 16 12:03:28 volumio3 kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Oct 16 12:03:28 volumio3 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
Oct 16 12:03:28 volumio3 kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
Oct 16 12:03:28 volumio3 kernel: sda: sda1 sda2
Oct 16 12:03:28 volumio3 kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Oct 16 12:03:28 volumio3 initramfs: Checking for USB updates
Oct 16 12:03:28 volumio3 kernel: F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Oct 16 12:03:28 volumio3 kernel: F2FS-fs (sda1): Can’t find valid F2FS filesystem in 1th superblock
Oct 16 12:03:28 volumio3 kernel: F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Oct 16 12:03:28 volumio3 kernel: F2FS-fs (sda1): Can’t find valid F2FS filesystem in 2th superblock
Oct 16 12:03:28 volumio3 kernel: EXT4-fs (mmcblk0p3): recovery complete
Oct 16 12:03:28 volumio3 kernel: EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
but doesn’t appear to be mounted.
#df -h ---------------
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 2.5G 1.1G 1.3G 45% /imgpart
/dev/loop0 456M 456M 0 100% /static
overlay 12G 19M 12G 1% /
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 3.9G 9.0M 3.9G 1% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs 3.9G 32K 3.9G 1% /tmp
tmpfs 3.9G 0 3.9G 0% /var/spool/cups
tmpfs 20M 28K 20M 1% /var/log
tmpfs 3.9G 0 3.9G 0% /var/spool/cups/tmp
/dev/mmcblk0p1 92M 61M 31M 67% /boot
2 Likes
Well … Detected but not mounted …
IS this a bug, or something special to do?
JMiK
3 Likes
Looks like it says there is something wrong in the file system - FAT32 actually, SSD formatted on my PC
JMiK.
Hello ,
My 4tb SSD is formatted with NTFS and works without any probs .
But had some with the usb-hdd-adapter on my RPI 4 .
Working one was hard to find . Finally I took one from an old 2.5 case .
2 Likes
Ok, then I can performm a ntfs format and see what’s going to happen.
JMiK
1 Like
Your disk was recognized correctly with UAS compatibility:
Oct 16 12:03:28 volumio3 kernel: scsi host0: uas
Oct 16 12:03:28 volumio3 kernel: scsi 0:0:0:0: Direct-Access Samsung Portable SSD T5 0 PQ: 0 ANSI: 6
However, there is something wrong with your disk formatting
Oct 16 12:03:28 volumio3 kernel: F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Oct 16 12:03:28 volumio3 kernel: F2FS-fs (sda1): Can't find valid F2FS filesystem in 1th superblock
Oct 16 12:03:28 volumio3 kernel: F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Oct 16 12:03:28 volumio3 kernel: F2FS-fs (sda1): Can't find valid F2FS filesystem in 2th superblock
And when Volumio tries to mount the disk, more errors:
Oct 16 12:03:53 volumio3 volumio[892]: error: Cannot associate FS Label, not mounting
Oct 16 12:03:53 volumio3 volumio[892]: error: Cannot associate FS Label, not mounting
Did you eject the device properly from windows?
1 Like
Yes, properly ejected
I’ve just formatted it again, in ntfs with 1024 b blocks.
I’ll tell you later about the results.
JMiK
Well, from what I understand, ejecting an External SSD from Windows properly is not Always possible,
and the consequence is the SSD won’t be mounted on the pi.
The safest way to transfer files from an external device to a pi is via network, lan etc
I’m going to try this I guess, not always practical for me. 
JMiK
Not sure if this is specific to the new beta, but I found that special characters seem to be missing in the artist name and song title on both my local screen, and in the Volumio IOS app. The ó is missing in Jóhann Jóhannsson’s name.
