-
When trying to build with podman using build.sh, i get the following error: STEP 14/18: RUN cd /tmp && unzip DaVinci_Resolve_Linux.zip && if [ " Not sure if the "bad CRC" is causing the exit code (2) but i redownloaded the file, and also tried with latest v19 and get the bad CRC each time $ podman images $ lsb_release -a $ glxinfo | grep "OpenGL version" $ nvidia-smi +---------------------------------------------------------------------------------------+ $ lscpu Keen to hear if others had this issue. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 2 replies
-
The line:
Suggests that there is actually a corrupted .zip file. CRC is a cyclic redundancy check, used to ensure a file does not contain any errors. If a .zip fails a CRC check while uncompressing, it usually means something in the file is not what was expected. If you like, you can use I know you said you tried re-downloading the .zip, but are you 100% sure you replaced the older file with the newly downloaded one? (And did you notice any difference, say in file size in the two downloads?) You can easily find if the downloaded files are identical or not: Method 1: $ diff file1 file2
Binary files file1 and file2 differ (if they are the same, you will not get any output) Method 2: $ sha256sum file1
$ sha256sum file2 (each of the above commands will output a random-looking characters --a "hash" of the file. If the characters outputted are the same for each file, the file is the same. Otherwise, they differ.) Also, instead of 18.6.6, maybe you want to try a different file-- say the latest beta for version 19, just to be 100% sure it's not that file itself. (Maybe it is corrupted on Blackmagic's side?) Let me know if any of these ideas helped! |
Beta Was this translation helpful? Give feedback.
-
Deleted all my downloaded zip files Then Checked for potential files with same name to be sure: $ Deleted all my podman images ran build.sh again Funny thing is, when I ran it again after deleting the podman images, I got a different CRC number (without touching the zip file) checked original file to be safe, and was still ok Going to wipe my hard-drive and reinstall Ubuntu from scratch |
Beta Was this translation helpful? Give feedback.
-
sigh..... Complete! if I run it again, i am back to same error Keeping in mind this is a fresh install of ubuntu, so there is nothing installed other than the prerequisites listed |
Beta Was this translation helpful? Give feedback.
-
Yes unfortunately with the inconsistency of these errors, and the fact that they seem to be related to checksums and verifying data, it looks like you may be having SSD issues :( At the very least, it may be a good idea to back up your most important data ASAP, then maybe replace the drive. Also, you might check the |
Beta Was this translation helpful? Give feedback.
-
Yeah we are going beyond the realm of this container and i appreciate all the help you have provided @fat-tire I don't expect you to solve this, but for what it is worth $ $ the ONLY thing i found was And this doesn't appear to be a disk issue, not sure if this is perhaps firmware/driver issue |
Beta Was this translation helpful? Give feedback.
-
That's good that you're not seeing too many errors... I don't know what that SMART error means actually. SMART was popular with hdd, but I don't see it referenced so much with ssd lately. Did you keep an eye on Also, did you try a Anyway, hope you finally got the container working :) |
Beta Was this translation helpful? Give feedback.
-
Yip that was it... thanks for your help @fat-tire Complains about it not supporting CUDA 12.3, but after manually selecting openCL and my GPU it starts up $
|
Beta Was this translation helpful? Give feedback.
-
Terrific! I mean, not that you had bad RAM, but that you figured the issue! |
Beta Was this translation helpful? Give feedback.
I found the problem. One of my memory modules are bad
https://x.com/sh4rk711/status/1814226197586522269
Explains the inconsistencies
your recommendation on
dmesg
started to list segmentation faults on random commands, such asapt-get update
etc. which made me look at memory, thanks for that @fat-tire