Urgent - Prodcution Env Issue - CRC -Failed
A free file archiver for extremely high compression
Brought to you by:
ipavlov
Menu
▾
▴
2 Attachments
#598 Urgent - Prodcution Env Issue - CRC -Failed
when extracting compressed RVT files that comressed using 7zip by command ( p.Arguments = "a -t7z \"" + targetName + "\" \"" + sourceName + "\" -mx=5";)
i am getting error with headers and CRC failed
when trying to open file we get error from Revit software as well
please advice
Describe hardware/CPU/RAM/Storage/SSD/OS specification of all computers that were used to create/store/transfer/extract that archive.
Create another similar archive with similar data, and test that new archive.
Last edit: Igor Pavlov 2024-12-15
i attached 2 files Please have a look
this is a very small zip that we do, and it is made in an aws instance wo what could be the isssue here ?
Describe hardware/CPU/RAM/Storage/SSD/OS/Software specification of all computers that were used to create/store/transfer/extract your "bad" archive.
Describe it so:
We have computer: specification of hardware/OS.
We created archive to the storage (specification) with the command ...
size of original file / size of archive.
We transfered archive to .... with the following software / command.
Archive was stored in ... (specification of storage hardware).
Archive was transfered to ... .
Archive was extracted on computer (specification of computer/OS).
At each step you could have data corruption.
So think about each step, and find exact step where data was currupted.
For example if you download file, you can try to redownload same file.
Last edit: Igor Pavlov 2024-12-15
We have computer: specification of hardware/software.
2 CPU 8Gb Ram *
We created archive to the storage (specification) with the command ...
( p.Arguments = "a -t7z \"" + targetName + "\" \"" + sourceName + "\" -mx=5";)
size of original file / size of archive.
I do not have all to correct sizes, it is on the client now
But somewhere around of 500 Mb zipped to less then a 100, most of the files are zip files that we received from Autodesk - when we extract them with our compressing them with 7zip they open ok *
We transfered archive to .... with the following software / command.
*After downloading to our server the zip file (not 7 zip ) then we zip with the command all the path with the zip file *
Archive was stored in ... (specification of storage hardware).
All is happening in the AWS instance *
Archive was transfered to ... .
Then we upload the 7Zip into s3 Bucket sign the URL of the file and sending it to the client *
Archive was extracted on computer (specification of computer/OS).
*On Client computer *
answers are inline
Last edit: omri kaufman 2024-12-15
it's too complicated description: clent / non-client, aws/ non-aws.
Write simpler:
We had AWS server (computer-1) - specification (including OS version).
We have data on that AWS server - number of files and size.
We use 7-Zip (version) with the following command on that computer-1: ...
...
describle all steps up to step with error message.
If some data was moved to another computer, describe what software/command was used to transfer that data.
Last edit: Igor Pavlov 2024-12-15
Data was corrupted.
So some data transferring/storing step corrupted the data.
Think about all steps.
You can try to reproduce each of these step again with new data.
And calculate sha-256 checksum of file after each step.
It can show the step where data could be corrupted.
Last edit: Igor Pavlov 2024-12-15
i have a question the file is download from Autodesk is a zip file, that is working for me
then we download it to a specific location in folder hierarchy and zip it
do i need to check the sha-256 checksum for the zip file or unzip and do it for the file ?
what is the best way to do the sha-256 checksum? some tool ?
and then i am uploading it to the cloud how do i check it is uploaded ok ? how do i check the sha-256 checksum there ?
these questions are not related to 7-zip.
but do i need to check the sha-256 after the zip or do i need to unzip and then check it ?
7-Zip worked correctly.
You had data corruption at another stages when you stored data or when you transferred data.
Read my messages above in this thread.
In my experience it's bad RAM. Try making a bootable MemTest86 iso from https://www.memtest86.com/download.htm and verify your RAM. Another issue I had was bad SATA cable, it corrupted 1byte per GB transfered....