I/O error with external SSD at the RPI4 [SOLVED]

[samo]

Hi,

my SanDisk Extreme Pro Portable SSD doesn't work stable with my Raspberry Pi 4. I can mount it without problems:

Code: Select all

[    0.809119] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    0.962994] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.20
[    0.963039] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    0.963065] usb 1-1: Product: USB2.0 Hub
[    0.965116] hub 1-1:1.0: USB hub found
[    0.965401] hub 1-1:1.0: 4 ports detected
[    1.093484] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[    1.114460] usb 2-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[    1.114504] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    1.114528] usb 2-1: Product: Extreme SSD
[    1.114549] usb 2-1: Manufacturer: SanDisk
[    1.114569] usb 2-1: SerialNumber: 323033344339343031313038
[    1.158763] scsi host0: uas
[    2.036787] scsi 0:0:0:0: Direct-Access     SanDisk  Extreme SSD      0111 PQ: 0 ANSI: 6
[    2.039411] scsi 0:0:0:1: Enclosure         WD       SES Device       0111 PQ: 0 ANSI: 6
[    2.039580] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    2.039825] sd 0:0:0:0: [sda] Write Protect is off
[    2.039853] sd 0:0:0:0: [sda] Mode Sense: 4b 00 10 00
[    2.040167] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.040971] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
[    2.045895]  sda: sda1
[    2.048526] sd 0:0:0:0: [sda] Attached SCSI disk

But when I start reading the directories of the SSD I get the following error:

Code: Select all

[  181.765108] usb 2-1: USB disconnect, device number 2
[  181.766034] print_req_error: I/O error, dev sda, sector 0
[  181.770344] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  182.009133] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[  182.317445] usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[  182.338325] usb 2-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[  182.338342] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  182.338355] usb 2-1: Product: Extreme SSD
[  182.338366] usb 2-1: Manufacturer: SanDisk
[  182.338378] usb 2-1: SerialNumber: 323033344339343031313038
[  182.348065] scsi host1: uas
[  183.208651] scsi 1:0:0:0: Direct-Access     SanDisk  Extreme SSD      0111 PQ: 0 ANSI: 6
[  183.211543] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[  183.211720] sd 1:0:0:0: [sdb] Write Protect is off
[  183.211737] sd 1:0:0:0: [sdb] Mode Sense: 4b 00 10 00
[  183.212043] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[  183.212682] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes
[  183.215519] scsi 1:0:0:1: Enclosure         WD       SES Device       0111 PQ: 0 ANSI: 6
[  183.218420]  sdb: sdb1
[  183.227353] sd 1:0:0:0: [sdb] Attached SCSI disk

The problem also occurs with over_voltage=1 in config.txt.
The SDD works without problems with USB2 at the RPI4 and also with USB3 at my PC.
Does someone have an idea how to fix this problems?
BR

[NeddySeagoon]

samo,

Don't use uas.

[Tony0945]

https://acronyms.thefreedictionary.com/UAS

[samo]

samo,

Don't use uas.

Thanks, I will try it out.

[samo]

Without UAS the issue still occurs:

Code: Select all

[  445.280805] usb 2-1: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[  445.301667] usb 2-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[  445.301683] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  445.301695] usb 2-1: Product: Extreme SSD
[  445.301706] usb 2-1: Manufacturer: SanDisk
[  445.301716] usb 2-1: SerialNumber: 323033344339343031313038
[  445.304045] usb-storage 2-1:1.0: USB Mass Storage device detected
[  445.304766] scsi host0: usb-storage 2-1:1.0
[  447.093024] scsi 0:0:0:0: Direct-Access     SanDisk  Extreme SSD      0111 PQ: 0 ANSI: 6
[  447.201128] scsi 0:0:0:1: Enclosure         WD       SES Device       0111 PQ: 0 ANSI: 6
[  447.201328] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[  447.202668] sd 0:0:0:0: [sda] Write Protect is off
[  447.202683] sd 0:0:0:0: [sda] Mode Sense: 4b 00 10 00
[  447.204069] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[  447.212486]  sda: sda1
[  447.215501] sd 0:0:0:0: [sda] Attached SCSI disk
[  527.643372] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

Code: Select all

[  626.704469] usb 2-1: USB disconnect, device number 4
[  626.705329] print_req_error: I/O error, dev sda, sector 0
[  626.724403] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  626.725377] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
[  627.044807] usb 2-1: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[  627.065716] usb 2-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[  627.065730] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  627.065741] usb 2-1: Product: Extreme SSD
[  627.065752] usb 2-1: Manufacturer: SanDisk
[  627.065762] usb 2-1: SerialNumber: 323033344339343031313038
[  627.068017] usb-storage 2-1:1.0: USB Mass Storage device detected
[  627.069226] scsi host1: usb-storage 2-1:1.0
[  628.852102] scsi 1:0:0:0: Direct-Access     SanDisk  Extreme SSD      0111 PQ: 0 ANSI: 6
[  628.958593] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[  628.958814] scsi 1:0:0:1: Enclosure         WD       SES Device       0111 PQ: 0 ANSI: 6
[  628.959351] sd 1:0:0:0: [sdb] Write Protect is off
[  628.959367] sd 1:0:0:0: [sdb] Mode Sense: 4b 00 10 00
[  628.960557] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[  628.968931]  sdb: sdb1
[  628.972369] sd 1:0:0:0: [sdb] Attached SCSI disk
[  638.272032] EXT4-fs error (device sda1): ext4_find_entry:1455: inode #2: comm ls: reading directory lblock 0

[samo]

Also with quirks it does not work.

Code: Select all

[    0.808556] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    0.959035] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.20
[    0.959081] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    0.959105] usb 1-1: Product: USB2.0 Hub
[    0.960976] hub 1-1:1.0: USB hub found
[    0.961224] hub 1-1:1.0: 4 ports detected
[    1.084902] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[    1.105767] usb 2-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[    1.105810] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    1.105833] usb 2-1: Product: Extreme SSD
[    1.105853] usb 2-1: Manufacturer: SanDisk
[    1.105873] usb 2-1: SerialNumber: 323033344339343031313038
[    1.108925] usb-storage 2-1:1.0: USB Mass Storage device detected
[    1.113559] usb-storage 2-1:1.0: Quirks match for vid 0781 pid 55a8: 800000
[    1.113723] scsi host0: usb-storage 2-1:1.0
[    2.900681] scsi 0:0:0:0: Direct-Access     SanDisk  Extreme SSD      0111 PQ: 0 ANSI: 6
[    3.697594] scsi 0:0:0:1: Enclosure         WD       SES Device       0111 PQ: 0 ANSI: 6
[    3.697858] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    3.699102] sd 0:0:0:0: [sda] Write Protect is off
[    3.699131] sd 0:0:0:0: [sda] Mode Sense: 4b 00 10 00
[    3.700345] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    3.709109]  sda: sda1
[    3.711912] sd 0:0:0:0: [sda] Attached SCSI disk

Code: Select all

[    4.116543] usb 2-1: USB disconnect, device number 2
[    4.118027] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[    4.118157] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
[    4.468963] usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[    4.493813] usb 2-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[    4.493855] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    4.493879] usb 2-1: Product: Extreme SSD
[    4.493899] usb 2-1: Manufacturer: SanDisk
[    4.493918] usb 2-1: SerialNumber: 323033344339343031313038
[    4.496172] usb-storage 2-1:1.0: USB Mass Storage device detected
[    4.496595] usb-storage 2-1:1.0: Quirks match for vid 0781 pid 55a8: 800000
[    4.496741] scsi host0: usb-storage 2-1:1.0
[    6.260900] scsi 0:0:0:0: Direct-Access     SanDisk  Extreme SSD      0111 PQ: 0 ANSI: 6
[    7.066759] scsi 0:0:0:1: Enclosure         WD       SES Device       0111 PQ: 0 ANSI: 6
[    7.067025] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    7.070534] sd 0:0:0:0: [sda] Write Protect is off
[    7.070551] sd 0:0:0:0: [sda] Mode Sense: 4b 00 10 00
[    7.071212] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    7.142169]  sda: sda1
[    7.145131] sd 0:0:0:0: [sda] Attached SCSI disk

[pa4wdh]

My first guess would be power. SSD's use a lot more power when they read/write compared to idle, are you sure your Pi's power supply is able to power the SSD? It would explain the difference with lower speeds (USB2) and your PC (better power supply).

An easy way to test this is to connect the SSD via a powered hub and see if the problem persists.

[samo]

If the output of lsusb is correct, the maximum current consumption of the SSD is 896mA. According to the documentation the RPI4 provides up to 1.2A on the USB ports. My power supply provides 3A and the SSD is the only USB device.

But due to the lack of alternatives I will have to try out the hub proposal.

[NeddySeagoon]

samo,

That 896mA is just under the 900mA that a USB 3 root hub can supply and well above the 500mA permitted by USB2.

I run my Pi4 with a USB3 powers SSD off a 2.5A PoE HAT with no problems.
Measuring my SSD power consumption shows that for reads and writes its about 200mA. The label on the SSD says 2.5A.
It will be higher when its doing erase cycles but erase is not under user control.

[samo]

NeddySeagoon,

Thanks for the hint. Then I can save the money for an active USB hub for now.

BR

[samo]

Could the temperature cause the problems? My RPI4 has only a few small heatsinks.

[NeddySeagoon]

samo,

Unlikely. The Pi4 will thermal throttle when it gets to 80C.

I would not rule out the PSU. If you are using a mobile phone charger that will be a problem.

First, its around 4.7v because its designed to charge a lihtium battery.
The Pi wants 5.1 at its power input pins, so its already low.
When the Pi input voltage falls to 4.65v the Red LED is turned off and you get an undervolt warning in dmesg.

Taken together it appears that there is a 50mV margin. Now add in the dynamic regulation from the PSU and its a problem waiting to happen.

USB power supplies are rated at the output pins. That matters there.
If the PSU has a detachable cable, the rated voltage appears at the input to the cable, not the Pi end, so you have the voltage drop in the cable against you.
If the cable is fixed, the output voltage is at the Pi end of the cable.

Long story short, get a Pi PSU if you don't have one.

[samo]

I have the official Raspberry Pi USB-C power supply.

[NeddySeagoon]

samo,

That's the right answer :)
What does

Code: Select all

lsusb

say about your USB/SATA bridge chip?
Do you use a short USB3 cable without an extender?
What is the make/model of your USB enclosure?

Tony0945,

USB Attached SCSI (UAS) is part of the USB3 Specification.
Ordinary bulk mode, operates like IDE. Give a command, get the answer, give the next command ...
There is no DMA. Bulk mode still works on USB3 too.

UAS brings overlapped commands, trim, DMA, NCQ and all the other good things that SATA does.
a) when its implemented by the USB/SATA bridge.
b) when it works properly.

[samo]

NeddySeagoon,

I'm not sure how to get/access the information you asked for. lsusb -vvv tells me nothing about a bridge.

Bus 002 Device 023: ID 0781:55a8 SanDisk Corp. Extreme SSD
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.20
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0781 SanDisk Corp.
idProduct 0x55a8
bcdDevice 1.11
iManufacturer 2 SanDisk
iProduct 3 Extreme SSD
iSerial 1 323033344339343031313038
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0079
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 896mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 32
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 32
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 32
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
Command pipe (0x01)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 0x002a
bNumDeviceCaps 3
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x0000f41e
BESL Link Power Management (LPM) Supported
BESL value 1024 us
Deep BESL value 61440 us
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
SuperSpeedPlus USB Device Capability:
bLength 20
bDescriptorType 16
bDevCapabilityType 10
bmAttributes 0x00000001
Sublink Speed Attribute count 1
Sublink Speed ID count 0
wFunctionalitySupport 0x1100
bmSublinkSpeedAttr[0] 0x000a4030
Speed Attribute ID: 0 10Gb/s Symmetric RX SuperSpeedPlus
bmSublinkSpeedAttr[1] 0x000a40b0
Speed Attribute ID: 0 10Gb/s Symmetric TX SuperSpeedPlus
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x000c
(Bus Powered)
U1 Enabled
U2 Enabled

Also in the datasheet of the SDD I can't find any info about the bridge.

The cable is very short.

BTW: fstrim is not (yet) supported

BR

[NeddySeagoon]

samo,

What does

Code: Select all

rpi4-eeprom-updater

tell about your firmware versions?

Is the USB cable permanently attached to the drive or does it have a connector like this one?
That's a micro USB3 connector and they are usually bad news.

[samo]

NeddySeagoon,

The command rpi4-eeprom-updater is not available. I emerged raspberrypi-firmware-9999.

The cable is USB Type-C and USB 3.1 Type-A

BR

[NeddySeagoon]

samo,

Ahh. rpi4-eeprom-updater is one of Sakakis ebuilds.
Its also in my fork of Sakkaks overlay on github.
It probably depends on several other ebuilds there too.

I got the name of the command wrong, sorry, its rpi-eeprom-update. The package is dev-embedded/rpi4-eeprom-updater

Code: Select all

# rpi-eeprom-update
BCM2711 detected
VL805 firmware in bootloader EEPROM
BOOTLOADER: up-to-date
CURRENT: Thu  3 Sep 12:11:43 UTC 2020 (1599135103)
 LATEST: Thu  3 Sep 12:11:43 UTC 2020 (1599135103)
 FW DIR: /lib/firmware/raspberrypi/bootloader/beta
VL805: up-to-date
CURRENT: 000138a1
 LATEST: 000138a1

The VL805 is the USB3 chip on the Pi4. Some version of firmware work better than others.
That's what I am using now.

USB C is robust. At least, I've not broken one yet. Microusb3 sockets were very difficult to attach to the device and the normal stains of everyday use would make the solder joints on the inside of the device fracture.

[samo]

NeddySeagoon,

I try to add the genpi64-overlay to layman without success:

Code: Select all

rpi4 / # layman -o https://github.com/NeddySeagoon/genpi64-overlay/blob/master/repositories.xml -f -a genpi64-overlay
 
 * Fetching remote list...
 * XML DBHandler - ET.ParseError: not well-formed (invalid token): line 67, column 89
 * DbBase; error, Failed to read database at "/var/lib/layman/cache_1eb64e6457adc4ab96e574b2e447a788.xml"
 * Hint: If you manually set db_type. Please reset it and let layman-updater
 * migrate it. Otherwise layman's database is not initialized, nor populated
 * with any existing data.
 * Run the following: "layman-updater -m <db_type>"

I don't know which db_type is meant.

BR

[NeddySeagoon]

samo,

I may have made a mess of my fork of the genpi64 overlay.
I did edit the repositories.xml file.

To read the firmware versions the code in Sakakis genpi64 overlay will work.
It may not report the latest available firmware correctly.

[samo]

NeddySeagoon,

I get the same error with Sakakis overlay.

BR

[NeddySeagoon]

samo,

I think I used

Code: Select all

eselect repository

to set it up on my Pi.

[samo]

NeddySeagoon,

looks a little bit out-dated.

Code: Select all

# rpi-eeprom-update
BCM2711 detected
Dedicated VL805 EEPROM detected
*** UPDATE AVAILABLE ***
BOOTLOADER: update available
CURRENT: Mo 15. Jul 12:59:55 UTC 2019 (1563195595)
 LATEST: Do 3. Sep 12:11:43 UTC 2020 (1599135103)
 FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: update available
CURRENT: 00013701
 LATEST: 000138a1

I've installed sys-boot/raspberrypi-firmware-9999. I thought this would download the latest available version automatically. An update stops with the following error:

Code: Select all

# rpi-eeprom-update -a
BCM2711 detected
Dedicated VL805 EEPROM detected
*** INSTALLING EEPROM UPDATES ***
BOOTLOADER: update available
CURRENT: Mo 15. Jul 12:59:55 UTC 2019 (1563195595)
 LATEST: Do 3. Sep 12:11:43 UTC 2020 (1599135103)
 FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: update available
CURRENT: 00013701
 LATEST: 000138a1
grep: /var/lib/dpkg/info//rpi-eeprom.md5sums: Datei oder Verzeichnis nicht gefunden
cat: /var/lib/dpkg/info//rpi-eeprom-images.md5sums: Datei oder Verzeichnis nicht gefunden
md5sum: /tmp/tmp.e0pprUdhgg: keine korrekt formatierte MD5‐Prüfsummenzeile gefunden
rpi-eeprom checksums failed - try reinstalling this package
Unable to validate EEPROM image package checksums

The fix should bei available soon.

BR

[NeddySeagoon]

samo,

A little history is in order.

Since the original Pi was launched the Pi has had has a collection of files that live in /boot referred to as 'firmware'.
These files are run on the GPU before the kernel starts.
They are not really firmware as they are in /boot

With the Pi4 real firmware was added, in an SPI EEPROM, much like a PC BIOS.

raspberrypi-firmware gets you the fake firmware that lives in /boot.
You need dev-embedded/rpi4-eeprom-images which gets you both the boot loader and VL805 firmware.

[samo]

NeddySeagoon,

after downloading the latest version of rpi-eeprom-update manually the script runs:

Code: Select all

# rpi-eeprom-update -a
BCM2711 detected
Dedicated VL805 EEPROM detected
*** INSTALLING EEPROM UPDATES ***
BOOTLOADER: update available
CURRENT: Mo 15. Jul 12:59:55 UTC 2019 (1563195595)
 LATEST: Do 3. Sep 12:11:43 UTC 2020 (1599135103)
 FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: update available
CURRENT: 00013701
 LATEST: 000138a1
BOOTFS /boot
EEPROM updates pending. Please reboot to apply the update.

But now the rpi4 does not boot anymore. The boot screen flashes briefly and then I only see the colorful test image. The EEPROM seems to be corrupted and needs to be recovered

BR