Raspberry Pi 4 USB mass storage beta (beta means it not ready yet, and not officially released!)

[rasparbarian]

Installed the "2020-05-27 Fix DPI issue - BETA" version of the EEPROM today - I've been trying out the previous betas throughout the last week and weekend.

Before that I had (obviously) updated all possible packages and ran 'sudo rpi-update' + rebooted. After running rpi-eeprom-update with the beta bin from yesterday (05-27-2020), I no longer get the "pre-boot" screen that was in the earlier beta (the one with the QR code on the upright corner.)

Instead, I get the basic rainbow screen IF there is a MicroSD card in the slot. If I try plugging the RPi4B in without a MicroSD card in the slot, or with a bootable USB media in either of the USB ports, I get a black screen and that's all -- according to the LED's, there's not even any disk utilization.

I don't know if this is an intended "feature" or not, but at least in my case it makes the troubleshooting of any possible early-on boot process problems a lot more difficult than what they were.

My MicroSD build still works though, and its Raspbian kernel is now at 5.4.42-v8+. Haven't observed problems in running that. Too bad the USB boot now doesn't seem to work at all.

[bunklung]

Installed the "2020-05-27 Fix DPI issue - BETA" version of the EEPROM today - I've been trying out the previous betas throughout the last week and weekend.

Before that I had (obviously) updated all possible packages and ran 'sudo rpi-update' + rebooted. After running rpi-eeprom-update with the beta bin from yesterday (05-27-2020), I no longer get the "pre-boot" screen that was in the earlier beta (the one with the QR code on the upright corner.)

Instead, I get the basic rainbow screen IF there is a MicroSD card in the slot. If I try plugging the RPi4B in without a MicroSD card in the slot, or with a bootable USB media in either of the USB ports, I get a black screen and that's all -- according to the LED's, there's not even any disk utilization.

I don't know if this is an intended "feature" or not, but at least in my case it makes the troubleshooting of any possible early-on boot process problems a lot more difficult than what they were.

My MicroSD build still works though, and its Raspbian kernel is now at 5.4.42-v8+. Haven't observed problems in running that. Too bad the USB boot now doesn't seem to work at all.

I thought this thread was to be closed/locked?

Head over to here: viewtopic.php?f=63&t=275187. There are updates:

I pushed the fix again, there was a secondary change which appeared in the binary release but not in Git due to finger trouble so I've just replaced it with 2020-05-28. The APT package might not get updated until next week because we are busy with the new Pi OS release.

The binary release rescue image
https://github.com/raspberrypi/rpi-eepr ... 5.28-137ad

It's possible to grab the files from Github but you'll need to add the -i flag to instruct the script to skip the validation against the package manifest checksums because they won't match.

[thatchunkylad198966]

Can anyone recommend a USB3 to SATA adaptor for using an SSD?
The one I have atm gave errors because of storage quirks. want something known to work.

[scaramonga]

Can anyone recommend a USB3 to SATA adaptor for using an SSD?
The one I have atm gave errors because of storage quirks. want something known to work.

One I use, works just fine
https://www.amazon.co.uk/gp/product/B07 ... UTF8&psc=1

[Kendek]

Can anyone recommend a USB3 to SATA adaptor for using an SSD?
The one I have atm gave errors because of storage quirks. want something known to work.

I have very good experiences with StarTech adapter cables. These uses ASMedia ASM1351 and ASM1135E chipsets.
Only thing, a firmware update is required for UNMAP/TRIM support:
ASM1351 - 150708_B1_0A_02
ASM1153E - 140509_A1_82_40 or 141126_A1_EE_82

[rasparbarian]

I thought this thread was to be closed/locked?

Head over to here: viewtopic.php?f=63&t=275187. There are updates:

I pushed the fix again, there was a secondary change which appeared in the binary release but not in Git due to finger trouble so I've just replaced it with 2020-05-28. The APT package might not get updated until next week because we are busy with the new Pi OS release.

The binary release rescue image
https://github.com/raspberrypi/rpi-eepr ... 5.28-137ad

It's possible to grab the files from Github but you'll need to add the -i flag to instruct the script to skip the validation against the package manifest checksums because they won't match.

Thanks for the tip, will do just that. I've got to say it's a "bit" confusing that the threads keep on jumping from one to another and even when I'm trying to be up to date in terms of i.e. getting the latest versions from GitHub, there's already some sidetrack-thread somewhere elsewhere -- not to mention a GitHub link that doesn't even work in the thread that you linked me to! Obviously not your fault, but rather the juggling act between order and chaos from the devs. I'd really hope these shoelaces would get tied in at least somewhat coherent order, but then again, yep. Let's hope for the best and expect the worst Cheers.

[Fredmoy]

Can anyone recommend a USB3 to SATA adaptor for using an SSD?
The one I have atm gave errors because of storage quirks. want something known to work.

One I use, works just fine
https://www.amazon.co.uk/gp/product/B07 ... UTF8&psc=1

I tested several SSD to USB adapters, none of which caused me any problems. the only problem I had and with an M2 to USB adapter with JMicron controller.

[timg236]

Thread locked because there's a new release 2020-05-28 available. Please read the first post on that thread but TLDR the Raspberry Pi Imager - rescue image is the best starting point. Will look at documentation next week to see what needs updating based upon any areas which appear to be unclear.

Thread for new releases viewtopic.php?f=63&t=275187