Hi, there is already a bug report about a similar problem
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988120 It points to file jigdo-file-cache.db and mentions a positive one-time effect, which would match the observation that the first medium nearly always succeeds. It works if jigdo-file-cache.db is deleted before the jigdo-lite run. If you do so at the beginning of your script, then this would nicely explain why further ISOs fail and what is their connection at all. (I began to wonder how first and further ISOs are different to jigdo-lite.) The bug report mentions SHA256 as checksums in the .jigdo file, which i only see for the overall image but not for the single data files. But maybe it is about SHA256 in the jigdo-file-cache.db. This comment proposes a patch: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988120#20 and gives a code analysis. Have a nice day :) Thomas
