rAudio 20250420 USB Lib based album view locks up system

[Sagnasty]

Running rAudio 20250420 Raspberry Pi 3B+ Rev 1.3 > HiFiBerry DAC+ Pro (built up from latest image)

I updated my USB based library and confirmed that the counts and lib info was correct.

Next, I went to the album view and after scrolling down a few pages (album art was shown correctly for the first few pages), the system locked up (also lost hardwired Ethernet connection).

System came back fine after power was cycled.

Issue is repeatable

Jim

[hjfisch]

RPI4 , HiFiBerry Dac+ Pro , 5302 Albums and no lock up while scrolling (takes a few minutes) .

[Sagnasty]

@hjfisch, could you confirm if your library is USB based storage?

I also have no issue with the exact physical library (75000 tracks) that is instead stored on a Synology DS718+ NAS via NFS / Raspberry Pi 5B Rev 1.0

Jim

[hjfisch]

RPI4 with connected 4TB-SSD to USB 3 Port . 2162 Artists and 5302 Albums

[hjfisch]

Maybe you have a power-problem. If you connect a HDD or SSD to the RPI , you need extra power for these devices , because there are only 900 - 1200 ma at the combined USB-Outputs .

[Jez-UK]

@Sagnasty I've reported the same problem with a Raspberry Pi 3B+ and a USB connected SanDisk 1TB SSD.

#1921

[Sagnasty]

@Jez-UK As @hjfisch has suggested, It may be related to a USB power issue. Since you are using a storage device (SSD) which should draw less current than my storage device (rotating HD) do you have any additional devices connect to the remaining USB ports that you could temporarily disconnect for test?

For the record, here are my details:
5V 3A power supply
WD 5TB Elements hard drive USB 3.2 Gen 1 / USB 3.0 - WDBU6Y0050BBK-WESN formatted as exFAT
No other devices on the remaining three USB ports

My thought is that the problem seems to be related to a buffering or fetching/displaying of the album coverart as the lockup occurs more predictably rather than intermittently.

I can play Hi-Res files without issue (12 hours and counting) which seems to indicate it is not a power issue or data transfer bottle neck (but I have not ruled this out).

Jim

[hjfisch]

For sure you cannot use a HDD or a SSD on a RPI without extra power . Playing a song may work but not scannig the drive , which uses more power . A SSD needs about 900ma till 1300 ma , which means 4.5 - 6.5 Watts . A normal HDD needs even more . So you will need an Y-Cable on the device to deliver more power . Data side to the USB-Port of the RPI and the power side direct to the power supply . All + and - of the RPI are connected , so it does not help to connect the y-cable only to the USB-Ports of it . Also you need a power supply with more than 3a for the RPI4 with a connected HDD , because you will need 2.5 a only for the RPI 4 under load. In my case , I use a 6.5a power supply, because I have an USB-CD player connected too .

[Jez-UK]

@Sagnasty It's not a power issue with my setup. Like I reported - the problem doesn't happen with the previous i20250208 release, only since i20250309. My only thought was it might be my SSD is formatted in NTFS - but again, this wasn't an issue with the previous release.

I can only suggest you to try a fresh install of the earlier i20250208 release on a separate SD card and see if that solve your problem, as it did mine. At least it will give you a working backup until rune can identify the problem with i20250309.

Jez

[Sagnasty]

Today, I easily reproduce the problem with exactly the same components and music library with the exception that I used a 4TB Seagate Ironwolf SATA hard drive housed in an externally powered USB 3.0 enclosure.

Further, I could NOT reproduce this issue on the same machine / library running rAudio i20250208 with the USB powered hard drive or the externally powered hard drive as @Jez-UK had suggested.

One other thing to consider is that I have had no issues updating the library for any of these test cases (I would consider this to be a disk intensive process).

Base on these findings, I think it is safe to say that this issue is not USB power related.

Jim

[Sagnasty]

No problem when using rAudio 20250627