Volumio 4 Feedback Thread

Help and Support Help
536

Hey @maxxxmm,

The image shows exactly what is happening. Your EEPROM configuration is correct - the bootloader IS attempting USB first (“mode USB-MSD 4 order f14”). The USB drive IS detected and enumerated:

USB3[3] 00281203 connected enabled
MSD [02:00] 3.32 0000e003 register MSD
MSD READ_CAPACITY... block-count 60125184 block-size 512

The 30GB SanDisk is recognized at hardware level. However, partition reads fail:

Trying partition: 0
Unable to read partition as FAT
type: 32 lba: 0 ' 1 S' y1L R ' clusters 0 (48)

This is garbled partition data. The bootloader cannot read valid FAT partition structure, so it falls back to SD card.

This is a known problem with SanDisk Ultra Fit drives. These drives have firmware quirks that prevent proper reinitialization during warm reboot because USB power does not cycle - the drive remains powered but does not reset its internal state. Cold boot works because full power cycle forces complete reinitialization.

Had you mentioned the exact USB hardware in your initial post, this would have saved time and effort - SanDisk Ultra Fit compatibility issues with Raspberry Pi bootloaders are well documented.

I researched this problem extensively in the past in this thread:

Your options:

  1. Add EEPROM timing parameters to force USB power cycling during reboot. Edit bootloader config and add:
USB_MSD_PWR_OFF_TIME=1000
USB_MSD_STARTUP_DELAY=2000
USB_MSD_DISCOVER_TIMEOUT=10000

  1. Use a different USB drive. SanDisk Extreme Portable or Samsung drives generally work better. Avoid “Fit” style drives that run hot and have aggressive power management firmware.

  2. Accept the limitation - use cold boot (power cycle) when switching to OSMC, use Volumio reboot only when staying within Volumio.

Kind Regards,

1 Like