RPi4B 8GB - SSD - stuck on first boot at reached target sound card

Hi there,
Hopefully someone can help!
I used pi-imager to write the rpi image for 21.04 Budgie … and it displayed the grey boot screen for a long time, pressed esc to see what was going on, and it seems hung on Reached Target Sound Card … everything is marked with the green OK
My setup:
RPI 4B 8GB
DeskPi case
SSD plugged into the DeskPi SSD add-on board
USB’s appear to be working, i have a wireless logitech keyboard dongle plugged in
Should i just stick it out and wait??

******* EDIT *******
So, after multiple re-flashes, and reboots.
I extracted the img file from the xz file using 7zip…
Reflashed the img file to the SSD
plugged into the pi, and powered on
Had multiple ramfs (something) failures…
Powered off, and power on again…
Finally, it has come up with the System Configuration screen

Seems like try, try and try again till it comes up! :slight_smile:

How are you making out with this? Have you been able to successfully set up the new Budgie install?

If all is running well now, then great!

However, if it is running painfully slow, I am wondering if it may have something to do with the Deskpi case. Some SATA/USB adapters have issues working correctly on the 3.0 ports with the Rasbperry PI 4. I have one such adapter that does something similar to what you describe. I do not have a DeskPi case however, so I can’t test this, but the easiest ways to check if this is the problem would be to either to see if the issue still happens when booting the image from MicroSD, or by connecting the SSD to a USB 2.0 port instead. Unfortunately, if I am looking at the correct DeskPi model, it seems to use a small adapter to connect the SSD drive port to the USB port directly below it, so it most likely means having a spare USB A to A cable lying around, and using that to connect the SSD to one of the left side USB ports instead.

If this makes a very noticeable difference in speed (especially if you try a MicroSD and its far faster than SSD), it may be worth it to check with the manufacturer. I have seen a few mentions of them being aware of USB booting issues, and replacing the PCB boards of those models.

https://www.raspberrypi.org/forums/viewtopic.php?t=296211

Hey Samlane!
Thanks for that…

I am kinda there… I managed to get up and running, and everything seems to be fine, until i enable xrdp … trying to RDP to Budgie, i get the dreaded Oh No Something has gone wrong… logout.

That step has caused me to reflash Budgie 11 times so far today!

I had a similar issue with Debian 11 a few days ago (been experimenting)
I managed to fix that with using unstable apt repos list.
IE:
UNSTABLE UPDATES - in case
sudo nano /etc/apt/sources.list.d/unstable.list

ADD THE FOLLOWING
deb (http_ftp prefix).debian.org/debian/ unstable main
deb-src (http_ftp prefix).debian.org/debian/ unstable main
deb (http_ftp prefix).uk.debian.org/debian/ unstable main contrib

Am about to try that… and see if that works.

But, you might be onto something regarding a potentially flaky board.
I did use a microsd card as well, and performance was terribly slow compared to SSD, and over the years with raspbian, i have had many microsd card failures, hence moving to SSD rather.
Thanks again for your reply!!