As said I thought it was just some error when “burning” the image to the “disk” (=sd card), so I tried again… which failed, too. So far… so strange.
Questions
I just thought I’d report it here. Let me know if you think this is just some (random?) hardware failure or where I should report it, if it is something interesting…
In any case IÄm surprised as the SD card is new and thus likely has no fault.
Hmm, that’s definitely odd. It seems like the root squashfs on the ISO is corrupted. Could you double-check that it was written to the SD correctly by reading back from it and comparing to the downloaded ISO file?
Hm tried the linked question with cp --sparse=always and dd conv=sparsefrom here, but I always just got a 32Gb file.
I guess it wrote some bytes at the end of the partition or so and not only “just expand” it.
Now had an idea to just change the partition size back on the SD card, but GParted does not let me do this arg…
Uhm dd if=disk.image count=8049257792 bs=1 of=disksmall.img (for an ISO size of 804.257.792 Bytes) went bad (was horribly slow) and copied more than 1 GB…
So the resulting diff-iso-hex.diff has a size of 7 GiB, 7.021.294.902 Bytes.
After all, maybe it could be some error with the SD card or SD card reader. Would not it be a good idea to include a self-check (for first boot) in CoreOS then as some installer ISOs from some Linux distros do? (They verify checksums AFAIK.)