the stick seems to be okay
see attached file "smart_2020-09.txt" from today after a run of smartctl -t long /dev/sdb
anyway, tried another stick (Corsair VoyagerGT on /dev/sdb with LE Release):
after the creator created the install stick:
cat SYSTEM.md5 => 52b0c54371949fe8785bd3d9eebf1b06 target/SYSTEM
md5sum SYSTEM => 52b0c54371949fe8785bd3d9eebf1b06 SYSTEM
and after the installer installed on the stick:
cat SYSTEM.md5 => 52b0c54371949fe8785bd3d9eebf1b06 target/SYSTEM
md5sum SYSTEM => f152a99128d2166c518680ed4738c235 SYSTEM
mismatch !
attached some photo's from the installer log file.
it seems the installer is running wild somehow and I guess the bug is here (esp. when installing on USB Sticks)
on an Sandisk: box boots into an debug shell.
on an corsair: box doesn't boot/see the stick (=> no boot flag set)
I wonder what the installer is doing with /dev/sdc
But I have to admit that I need to replug the stick that the installer gets aware of it.
the box is an NUC with only an Sata-SSD as /dev/sda
more confused.