OSError: CRC check failed 0x4088b1f != 0xaaf28074
See original GitHub issueCutadapt Version: 3.3 Python Version: 3.7.7
I just installed the latest version of cutadapt, and I’m getting weird error message. I’ve previously had no issues processing this file with cutadapt.
Cutadapt is installed in my home directory on a slurm based HPC cluster. I’ve tested this on both the login node and on an interactive slurm node and I get the same error. I was hoping someone might be suggest where I can start troubleshooting.
Call to cutadapt:
(base) [abf@biomix test]$ cutadapt ../fastq/WT_0_hr_1_S1_L002_R1_001.fastq.gz > test.txt
Last Passing Read (Read # 19500):
@A00547:18:HGCLFDMXX:2:1101:24795:11397 1:N:0:ATTACTCG+TATAGCCT
CGCACGCGTTAGACTCCTTGGTCCGTGTTACAAGACGGGTCGGGTGGGAAGCCGACATCGCCGCCGACCCCGTGCGCTCGGCTTCGTCGGAGACGCGTGAC
+
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
First Failed Read:
@A00547:18:HGCLFDMXX:2:1101:25807:11397 1:N:0:ATTACTCG+TATAGCCT
CGCCCTAGGACACCTGCGTTACCGTTTGACAGGTGTACCGCCCCAGTCAAACTCCCCACCTGGCACTGTCCCCGGAGCGGGTCGCGCCCGCCCGCACGCGC
+
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Error Message:
This is cutadapt 3.3 with Python 3.7.7
Command line parameters: ../fastq/WT_0_hr_1_S1_L002_R1_001.fastq.gz
Processing reads on 1 core in single-end mode ...
Traceback (most recent call last):
File "/home/abf/.local/bin/cutadapt", line 8, in <module>
sys.exit(main_cli())
File "/home/abf/.local/lib/python3.7/site-packages/cutadapt/__main__.py", line 848, in main_cli
main(sys.argv[1:])
File "/home/abf/.local/lib/python3.7/site-packages/cutadapt/__main__.py", line 913, in main
stats = r.run()
File "/home/abf/.local/lib/python3.7/site-packages/cutadapt/pipeline.py", line 866, in run
(n, total1_bp, total2_bp) = self._pipeline.process_reads(progress=self._progress)
File "/home/abf/.local/lib/python3.7/site-packages/cutadapt/pipeline.py", line 326, in process_reads
for read in self._reader:
File "src/dnaio/_core.pyx", line 173, in fastq_iter
File "/home/abf/anaconda3/lib/python3.7/gzip.py", line 287, in read
return self._buffer.read(size)
File "/home/abf/anaconda3/lib/python3.7/_compression.py", line 68, in readinto
data = self.read(len(byte_view))
File "/home/abf/anaconda3/lib/python3.7/gzip.py", line 465, in read
self._read_eof()
File "/home/abf/anaconda3/lib/python3.7/gzip.py", line 512, in _read_eof
hex(self._crc)))
OSError: CRC check failed 0x4088b1f != 0xaaf28074
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Python gzip CRC check failed - Stack Overflow
I got the exact same error on code that has been running for months. Turns out that the file source was corrupted for...
Read more >User Error - CRC check fails · Issue #170 · dereneaton/ipyrad
It looks like the error is arising when trying to read in the the fastq files with link_fastqs() . Did Yaoxin use ipyrad...
Read more >Demux summarize error: CRC check failed - QIIME 2 Forum
Hello, I imported my paired end demultiplexed data using a manifest file, and am now ready to denoise with DADA2. However, when I...
Read more >Why the CRC check failed when running python convolutional ...
Hi all: I have gone through all the instructions of installing tensor flow. But when I run the TensorFlow demo model, some errors...
Read more >Sync fails with "PLP0000: CRC check failed" error
The task is failing with: Raw. PLP0000: CRC check failed 0x971ce6a4 != 0x846637c6L. There are four other tasks in error showing the same...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The offending versions 0.7.0 and 0.8.0 have been yanked from PyPI. These cannot be installed by accident anymore.
Thanks @rhpvorderman for fixing this so quickly! I was on vacation last week, and it is nice to see this resolved on coming back.