Thanks for reporting your experiments. I have seen this sort of behaviour before, I discovered it was related to the start-up power consumption of the hdd. I could reproduce it with one hdd 50% of the time, while another hdd worked without problems. Recently when I add a USB stick in addition to a hdd it has sometimes created the same problem. The Pi supplies a total of 1.2A to all USB devices (the Pi 5 is different), this is just enough for most hdd's, but there is not much headroom. There are a couple of things which you could try:RoyB wrote:...It is kind of trail-and-error to get RuneAudio working again. After several turn off actions (power off / reboots) at last RuneAudio recognizes the drive again and a fully update (seems a complete rebuild) of the MPD Library is then needed.
Of course I checked Debug in the meanwhile several times. Sometimes during the problem period the hdd is reported as a recognized Filesystem mount, but not seen in Sources RuneAudio...
- Clean the USB plugs and sockets
- Try using a different USB port on the Pi
- Try different cables on the hdd
- Use shorter cables on the hdd
- Use only one usb storage device
- Alter the startup delay in the file /boot/config.txt, its the line 'boot_delay=2', change it to 'boot_delay=3' or 'boot_delay=4'
- Try using a different power supply (check the debug, it reports under voltage when it occurs)[/list]
I will try some experiments with mounting usb disks, maybe some things can be done slightly differently.
As a last resort...
A powered USB hub was always advised in the past, but I have had mixed results; there are good and bad products on the market. I dont use them any more. Moving to a moderner hhd or using a ssd will reduce the power consumption. If you have another hdd its worth trying it before buying anything new.
janui