truncated file / EOF marker absent

The file was never finished being written

why

BGZF files (BAM, bgzipped VCF/FASTQ) end with a defined EOF block. Missing it means writing stopped early — a killed job, a full disk, an interrupted download, or a file read while still being written.

what to do

Treat the file as invalid rather than trying to repair it, and check why writing stopped — the job's own log usually shows a kill or an out-of-disk. If it was downloaded, verify the checksum; a truncated transfer is far more common than a corrupt source.

BGZF format specification
This is one entry from BioErrors, a catalogue of bioinformatics error messages that point at the wrong thing. Every entry was traced to its real cause before it was written down.
If your error is not in it, paste it there and it gets traced and added.