@ alanb128 Thanks for your reply. I devised the following new tests (hypothesis H1-H4) based on it.
- H1 Try another SD card.
- H2 Flash a different image file.
- H3 Exclude Windows interference with Linux
- H4 Try another SD card reader
H1 It’s the SanDisk card:
See test summary
Turn off Defender real time protection.
Test flashing with a Samsung EVO 32 GB card:
Wipe card quickly with SD formatter.
Write the same image with Balena Etcher via a Trust cardreader.
Result:
Failure in log:
Error: UNKNOWN: unknown error, read
code: "UNKNOWN"
description: "Generic STORAGE DEVICE USB Device"
device: "\\\\.\\PhysicalDrive4"
errno: -4094
name: "Error"
syscall: "read"
message: "UNKNOWN: unknown error, read"
stack: "Error: UNKNOWN: unknown error, read"
Result: Flashing also fails with a Samsung Evo 32GB card.
See Discussion about Windows interference
Discussion:
As soon as the microSD card is mounted a System Volume Information folder is created by Windows. When I check the timestamps of “System Volume Information” then it was created about 7 minutes after validating flashing by Balena Etcher. Inserting another USB device might have triggered it.
7 -rw-r--r-- 1 Marty None 6434 Feb 17 17:29 README
0 drwxr-xr-x 1 Marty None 0 Mar 17 09:24 'System Volume Information'
0 dr-xr-xr-x 1 Marty None 0 Mar 17 09:44 ..
H2 It’s the image.
Test: Flash another image to the same SD card
Result: It FAILS with error: Error: UNKNOWN: unknown error, read
Result: It FAILS with error:
Object
cancelled: false
results:
averageFlashingSpeed: 23578558.323751118
bytesWritten: 53477376
devices: {failed: 1, successful: 0}
errors: Array(1)
0: Error: UNKNOWN: unknown error, read
length: 1
[[Prototype]]: Array(0)
sourceMetadata: {size: 1854418944, name: 'decompressed-image-a9896fd8f75f.tmp', blocks: Array(8), blockmappedSize: 1107296256}
[[Prototype]]: Object
skip: false
[[Prototype]]: Object
H3 Windows interferes and writes in the just written FAT32 partition after flashing.
Also under Linux flashing fails.
As seen by Checksums do not match - #82 by zvin
Test: Write from another platform: Linux.
Result: flashing fails also.
H4 It’s the Trust cardreader.
Try the built in card reader hub: Multiple flash reader USB device:
USB\VID_058F&PID_6363
Result: SUCCESS!!!
Conclusion: The Trust cardreader in combination with Balena Etcher results in flashing failures.
Details about the faulty card reader:
Hardware ID:
USB\VID_05E3&PID_0751&REV_1402
Presumable contains the following chip:
Genesys Logic, Inc. GL835T
Discussion
Discussion
I’ve written many images with the card reader in the past (with Rufus and dd amongst others but also older versions of Balena Etcher). Validating the microSD card reported no failures. Somehow flashing with Balena results in errors, and flashing with RPi imager also results in an error. (BTW When I flash the utbuntu-22.04.2-preinstalled-server-armhf+raspi directly from the RPi on-line repository with the built in Card reader it also works, but it results in version 20.04 being flashed instead of 22.04. So RPi imager has the wrong Server image version in its repository under 22.04.)