Raspberry Pi does not boot with SSD and Feeder Stick

Hi,

I am using my raspberry pi 3 B over the last years and everything worked fine.
So I decided to upgrade it with a SSD to avoid a crashed SD card.
I cloned my SD card, enabled the usb boot mode and booted from the SSD.
It worked instantly.
The problem began, when I tryed to boot from the SSD with my blue flightaware stick attached. With both USB devices attached the raspberry pi didn’t boot.
I enabled the USB max bit and the increased the usb timeout but nothing worked.

Does anybody have an idea, where the problem is?

Thank you

Tino

You will need a persistent UUID and block device name in order to set the boot partion right.
The Pi looks at the Pro stick first ( assumption) and does not find a bootsection there.
Explanation can be found here
https://wiki.archlinux.org/title/persistent_block_device_naming

1 Like

I have my first feeder still operational with the initial SD card.
This is three years old in July this year.

I never had a single issue with this SD card. It only requires a larger card even if the size is overkill and a good planning to reduce SD card write attempts

I don’t think that is his issue. The USB Stick doesn’t show up as a block device, so i think the problem is somewhere else. Either too much power consumption on the USB ports or a weak power supply for the device itself. (both my assumption)

1 Like

My ssd case has an external power supply and I also have a powered USB hub. When I use one of these two options, the Raspberry Pi 4 still doesn’t start. See picture. Will look to the suggestion from Tom.

Did you upgrade to the latest firmware? Mine is booting from SSD, but only after i installed the latest FW.

If this is done, the device should show “SSD detected” during boot.
There are information on the net how to do it.

Yes. After i saw the date of the firmware (rather old) I’ve updated the Pi’s firmware. Still no luck though. If I plug in the Piaware stick right after detecting the ssd, the Pi will start up, but after some time, say five or ten minutes it is possible that the OS freezes. Starting with an externally powered ssd, will also lock up the boot sequence

Hm,

haven’t seen this. I am using a small Intenso SSD without additional power supply and it works without issues

Sorry can’t help on that

The SSD works without additional power and without a plugged in Piaware USB stick, no problem at all. But it won’t start if the Piaware USB stick is plugged in while booting up, the bootloader comes in a boot loop state, probing the USB ports. With the latest firmware, after some 25ish seconds the Pi searches for a USB attached SSD.

Wil test further and look if I can find a solution.

Did you try putting the Stick to the powered hub?

Yep. We are getting closer… It is a USB 3.1 hub. When I plug it into the USB3 it won’t start, however if I plug it into the USB2 port of the Pi (with PiAware stick) I’m getting the rainbow colored screen. Then the Pi hangs.

Update. Success! I have powered the ssd with a 3.3 volts, 50 mA power supply. This seems to be just enough to start things up. The power supply of the Pi is a 5 volts, 2.5 Amps one.

Get an original RPi power supply, it solves lots of issues.

Unless you have to, i woudln’t use an SSD when feeding ADS-B.
The USB bursts of data cause MLAT data issues and you could get removed from the MLAT pool.

Correct. If there is no other things writing to the disk, it’s not necessary. I’ve also set up log2ram, so the write attempts over a day are a little above zero

Ah thanks for the explanation both of you! Meanwhile I have formatted a 128 GB SD card and installed Raspberry OS. More than enough space. Now busy installing Tar1090 and some feeders.

If you are using Pi for ADSB only, then using 128GB microSD card is like using a Cannon to kill a fly.

By the way all my Pis have 128GB - 120 = 8 GB :wink: microSD cards, running without issue for several years.

If he has it as a spare part it is still cheaper than buying a new one :wink:

2 Likes

Yes, and i do some more things with my pi4.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.