[PROBLEM] Moode won't start if a USB stick with music is present

[Ouchita]

Using Release 8.3.1 (2023-04-17)
Pi 3B+ with USB boot and separate USB stick contatining music. HiFiBerry Amp2, v1.1
(Same problem with Suptronix 400 and IqAudio HATS)

If the music USB is plugged in, Moode won't start. The red power LED is on, but the green LED does show anything, I have waited up to 15 minutes !
If the music USB is not mounted, boot occurs, and musc USB can be plugged in when the green USB has been flashing for a couple of minutes (I haven't checked the minimum time !) and Moode cn be used.

I didn't have this problem with earlier releases, eg 1.7


Tony

[Nutul]

Using Release 8.3.1 (2023-04-17)
Pi 3B+ with USB boot and separate USB stick contatining music. HiFiBerry Amp2, v1.1
(Same problem with Suptronix 400 and IqAudio HATS)

If the music USB is plugged in, Moode won't start. The red power LED is on, but the green LED does show anything, I have waited up to 15 minutes !
If the music USB is not mounted, boot occurs, and musc USB can be plugged in when the green USB has been flashing for a couple of minutes (I haven't checked the minimum time !) and Moode cn be used.

I didn't have this problem with earlier releases, eg 1.7


Tony

Hi,

cannot be sure of what I am going to say hereafter, but...
is your USB marked as bootable device, but does not contain any bootloader...? Try reformat it: I have a 1TB NVMe USB device on all the time, and I reboot my Raspberry at least once a week, and never had an issue with it preventing boot.
I must say, though, that the disk in question is formatted as Ext4

[TheOldPresbyope]

I second Al's suspicion that the USB stick with music is marked as bootable. (As always, one has to keep in mind that if the power supply is inadequate, then all sorts of weird behaviors may occur but it sounds like this isn't the case here. One can always check the logs for undervoltage events.)

I routinely run test scenarios, including on a Pi3B+, which boot moOde from one USB stick (actually a uSD card on an USB adapter) and contain test tracks on one or more additional USB sticks. This approach has been working for me since the RPF introduced the ability to boot from USB.

Regards,
Kent

[Ouchita]

I second Al's suspicion that the USB stick with music is marked as bootable. (As always, one has to keep in mind that if the power supply is inadequate, then all sorts of weird behaviors may occur but it sounds like this isn't the case here. One can always check the logs for undervoltage events.)

I routinely run test scenarios, including on a Pi3B+, which boot moOde from one USB stick (actually a uSD card on an USB adapter) and contain test tracks on one or more additional USB sticks. This approach has been working for me since the RPF introduced the ability to boot from USB.

Regards,
Kent

Thanks to both of you. I use 64 Gb Sandisk  Cruzer sticks, NTFS format.
I wasn't aware that a USB stick can be marked as unbootable, despite quite a few creations of loading music on an empty stick.  How do I achieve that?

[TheOldPresbyope]

I second Al's suspicion that the USB stick with music is marked as bootable. (As always, one has to keep in mind that if the power supply is inadequate, then all sorts of weird behaviors may occur but it sounds like this isn't the case here. One can always check the logs for undervoltage events.)

I routinely run test scenarios, including on a Pi3B+, which boot moOde from one USB stick (actually a uSD card on an USB adapter) and contain test tracks on one or more additional USB sticks. This approach has been working for me since the RPF introduced the ability to boot from USB.

Regards,
Kent

Thanks to both of you. I use 64 Gb Sandisk  Cruzer sticks, NTFS format.
I wasn't aware that a USB stick can be marked as unbootable, despite quite a few creations of loading music on an empty stick.  How do I achieve that?

Well, it's still just a conjecture on our part that I'll try to test later today.
 
Meanwhile, from the command line you can run fdisk as superuser and look for an asterisk under "Boot" in the device entries. For example, here's the output for one of my players when I ran fdisk with two USB sticks inserted. One with two partitions and one with only one partition, so there's a total of 3 entries listed in the "Device" groups, none marked bootable. The -l flag means "list" and the /dev/sd* means look only at these removable drives (loosely speaking).

Code:

pi@moode:~ $ sudo fdisk -l /dev/sd*
Disk /dev/sda: 14.84 GiB, 15931539456 bytes, 31116288 sectors
Disk model: STORAGE DEVICE  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb9f96b7c

Device     Boot  Start      End  Sectors  Size Id Type
/dev/sda1         8192   532479   524288  256M  c W95 FAT32 (LBA)
/dev/sda2       532480 31116287 30583808 14.6G 83 Linux


Disk /dev/sda1: 256 MiB, 268435456 bytes, 524288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000


Disk /dev/sda2: 14.58 GiB, 15658909696 bytes, 30583808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdb: 28.64 GiB, 30752636928 bytes, 60063744 sectors
Disk model:  SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1          32 60063743 60063712 28.6G  c W95 FAT32 (LBA)


Disk /dev/sdb1: 28.64 GiB, 30752620544 bytes, 60063712 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
pi@moode:~ $

Regards,
Kent

[HifiPenguin]

Hi,

Did you waited long enough or moOde to boot ?

I've seen it taking a LONG time to boot when a USB stick with music was hooked up at boot.

Regards.

[Ouchita]

I second Al's suspicion that the USB stick with music is marked as bootable. (As always, one has to keep in mind that if the power supply is inadequate, then all sorts of weird behaviors may occur but it sounds like this isn't the case here. One can always check the logs for undervoltage events.)

I routinely run test scenarios, including on a Pi3B+, which boot moOde from one USB stick (actually a uSD card on an USB adapter) and contain test tracks on one or more additional USB sticks. This approach has been working for me since the RPF introduced the ability to boot from USB.

Regards,
Kent

Thanks to both of you. I use 64 Gb Sandisk  Cruzer sticks, NTFS format.
I wasn't aware that a USB stick can be marked as unbootable, despite quite a few creations of loading music on an empty stick.  How do I achieve that?

Well, it's still just a conjecture on our part that I'll try to test later today.
 
Meanwhile, from the command line you can run fdisk as superuser and look for an asterisk under "Boot" in the device entries. For example, here's the output for one of my players when I ran fdisk with two USB sticks inserted. One with two partitions and one with only one partition, so there's a total of 3 entries listed in the "Device" groups, none marked bootable. The -l flag means "list" and the /dev/sd* means look only at these removable drives (loosely speaking).

Code:

pi@moode:~ $ sudo fdisk -l /dev/sd*
Disk /dev/sda: 14.84 GiB, 15931539456 bytes, 31116288 sectors
Disk model: STORAGE DEVICE  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb9f96b7c

Device     Boot  Start      End  Sectors  Size Id Type
/dev/sda1         8192   532479   524288  256M  c W95 FAT32 (LBA)
/dev/sda2       532480 31116287 30583808 14.6G 83 Linux


Disk /dev/sda1: 256 MiB, 268435456 bytes, 524288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000


Disk /dev/sda2: 14.58 GiB, 15658909696 bytes, 30583808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdb: 28.64 GiB, 30752636928 bytes, 60063744 sectors
Disk model:  SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1          32 60063743 60063712 28.6G  c W95 FAT32 (LBA)


Disk /dev/sdb1: 28.64 GiB, 30752620544 bytes, 60063712 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
pi@moode:~ $

Regards,
Kent

Thanks for that. I followed these instructions to use diskpart on Windows, to create an 'unbootable' drive. It didn't work!
##########
Step 1. Click Start, in the Run box, type diskpart, and press "Enter" to start the diskpart command prompt. 

Step 2. Type the following commands and press "Enter" after each move. 

list disk
select disk X (replace X with the disk number of your bootable USB drive)
clean
create partition primary
format fs=fat32 quick or format fs=ntfs quick (select one file system based on your own needs)
exit

After completing the steps, the USB flash drive will be formatted with the option that you specified.
##########
But I got no improvement, when I tried to boot with that USB drive inserted, it wouldn't..
I'm experimenting......

[TheOldPresbyope]

@Ouchita

I’m preoccupied with my HoneyDo list at the moment

I seem to recall there were some USB booting issues discussed in the past over on the Raspberry Pi Forum concerning certain drive models or their capacities. Also about the Pi4B USB3.0 ports if they’re involved. Something like that.

You might want to check there for useful tidbits.

Just a thought. Could be irrelevant.

Regards,
Kent

[Ouchita]

@Ouchita

I’m preoccupied with my HoneyDo list at the moment

I seem to recall there were some USB booting issues discussed in the past over on the Raspberry Pi Forum concerning certain drive models or their capacities. Also about the Pi4B USB3.0 ports if they’re involved. Something like that.

You might want to check there for useful tidbits.

Just a thought. Could be irrelevant.

Regards,
Kent

Hi Kent, thanks for taking the time.
I checked my sda devices as you suggested, and it pretty much matches yours, In particular, there are no astericks under the Boot heading.
I'll check the RPForum you suggest, although I'll point out that Im using a Pi3B+ with USB 2 only.

[Tim Curtis]

Swap in a different power supply rated for 3 Amps.