Are you choosing the correct USB device (the USB stick) and not something else?
I usually find it a good idea to look at what USB devices exist before I plug in the USB stick and then look again after I plug in the USB stick, to see what changed i.e. new devices - so that I am sure that I am going to write to the correct device.
The assumption is that the USB stick is going to have its contents obliterated by this operation, in which case … does it already have stuff on it? and if so has it previously worked normally on this computer?
Maybe posting a screenshot from Gnome Disks would help.
Your computer thinks that it’s a 31 GB USB stick. Can you clarify? A photo of the USB stick? Many (but not all) USB sticks will be marked with their capacity.
Also, did your download of the .iso file work correctly??? Your computer is saying that the .iso file is only 84 KB (which is surprisingly tiny - please confirm the size) but when I checked yesterday I thought it was more like 200+ MB. And that’s kind of what Gnome Disks is trying to warn you about, albeit that you are still going to get a warning anyway.
Also I am wondering what “Generic STORAGE DEVICE” (of unknown size) is. Hopefully it is not relevant here.
Purism ought to publish securely a cryptographically-secure hash of the file so that one can verify the integrity of the file after download and before doing anything with it. However the difference between 84 KB and 277 MiB ought to be clue enough not to bother with checking the hash.
@chucker8 I just read this in the README, one level up in the repo
The files in this repo are not intended for end users.
They are intended to be used by official Purism update
mechanisms (eg, coreboot utility script), or downloaded
and applied manually when directed by Purism support staff.
Direct flashing or other use by end users without specific
instruction to do so is highly discouraged.
@irvinewade It would be trivial as-is to provide a checksum as a text file in the repo. If these files are later generated as CI build artifacts, it would be easy to modify the yml to include the checksum as part of a release without any human involvement.