You will find another log called crash-log in the share.
I tried to reset the NK Storage to factory settings. It worked and showed the success dialog box. Then the message of disconnecting the NKStorage was shown.
While the App was still writing logs I tried to get the App opened from the tray (in macOS it is the Menu bar) I only have seen the beach ball and then the critical dialog box .... and gone
So you also might find that log useful ...
[Update: ] Ah, after that I get the ask to do the device initialization ( so the generic init and not the random fill ) - so stay tuned for the next log
[Update: ] Ok, I did the AES key init, the dialog box for the keys showed and disappeared after a while. Then I clicked on the menu bar, have seen the beach ball and a couple of seconds later "SD-Karte konnte nicht gelöscht werden. Status Code : -1 " as a dialog box. (While it looks like the deletion of the SD Card is still ongoing (( bright red LED)) )
So you will find a log called "AES Key Init" for this action on the above share.
[Final Update] I used a new SD Card (also 16GB, but a bit faster) , did a factory reset and the random number writing. This time it worked well: the dialog was upcoming , creating new AES keys, the dialog with the progress bar was showing during the full runtime of around 1 hour the progress, the log was written with good data until the end of the bright red LED of the NK Storage . You will find another log "newsdlog.txt/zip" for that test on the same share.
So I think the original SD card is now defect due to too many writes. And the defect is after the first 2 gb partition. That could be the reason that the procedure started well and then crashed in the middle. Anyhow, I think SD Card errors capturing could be improved.