Offline install snapshots corrupted for (at least) weeks

In the OpenSUSE Tumbleweed offline install ISO files, I get multiple (i.e. hundreds) corrupted .rpm files for every recent snapshot, last tested with openSUSE-Tumbleweed-DVD-x86_64-Snapshot20220819-Media.iso. These corruptions have appeared in several snapshots since at least August 1st (oldest file I could get); they are reported by the installer and also 7Zip on Windows when run on the mounted image file. The SHA-256 checksums are correct in several cases that I have checked, meaning that the cause lies at or before ISO creation. All systems that I use for this have ECC RAM. Several (probably all) architectures/platforms are affected, not just x86_64.

See also https://www.reddit.com/r/openSUSE/comments/wplc4l/tumbleweed_offline_install_image_corruptions/

Hi and welcome to the Forum :slight_smile:
Can you describe the process your using to create the images, is this to to dvd or USB?

7zip does not even support zstd compression used by Tumbleweed RPM. And you did not show any other evidence.

The installer, that I run from DVD (I have burnt and tried many DVDs of several snapshots), reports multiple rpm files as corrupted (when I continue after the first error, that is). The affected files are different from snapshot to snapshot.

7Zip approves of every rpm file on the current Leap images, so I assume it can handle at least some rpm files. The errors I get are from 7Zip are often about.cpio files (edit: but the error would be from an encapsulating format, but does it need to decompress to check the CRC?):

ERROR: Data Error : akregator-lang-22.08.0-1.1.noarch.cpio
ERROR: Data Error : ark-lang-22.08.0-1.1.noarch.cpio
ERROR: CRC Failed : autoconf-2.71-1.5.noarch.cpio

automake-1.16.5-3.1.noarch.cpio.zstd
ERRORS:
There are data after the end of archive

ERROR: There are some data after the end of the payload data : automake-1.16.5-3.1.noarch.cpio
ERROR: Data Error : blinken-lang-22.08.0-1.1.noarch.cpio
ERROR: Data Error : cervisia-lang-22.08.0-1.1.noarch.cpio
ERROR: Data Error : container-selinux-2.188.0-1.1.noarch.cpio
ERROR: Data Error : docbook-xsl-stylesheets-1.79.2-2.12.noarch.cpio
ERROR: CRC Failed : emacs-el-28.1-2.1.noarch.cpio
…]
ERRORS:
Headers Error
Unconfirmed start of archive

ERROR: CRC Failed : chrome\browser\content\pocket\panels\img\pocketsignup_hero@2x.png
ERROR: Data Error : akonadi-calendar-tools-22.08.0-1.1.x86_64.cpio
ERROR: Data Error : akonadi-import-wizard-22.08.0-1.1.x86_64.cpio
ERROR: Data Error : akregator-22.08.0-1.1.x86_64.cpio
ERROR: CRC Failed : aria2-1.36.0-1.6.x86_64.cpio
ERROR: Data Error : ark-22.08.0-1.1.x86_64.cpio
ERROR: CRC Failed : bash-5.1.16-8.2.x86_64.cpio
ERROR: CRC Failed : binutils-2.39-1.1.x86_64.cpio
ERROR: Data Error : blinken-22.08.0-1.1.x86_64.cpio
ERROR: Data Error : bovo-22.08.0-1.1.x86_64.cpio
ERROR: Data Error : breeze5-style-5.25.4-1.1.x86_64.cpio
ERROR: Data Error : cervisia-22.08.0-1.1.x86_64.cpio
ERROR: CRC Failed : csmash-0.6.6-274.2.x86_64.cpio
ERROR: Data Error : cups-2.4.2-2.1.x86_64.cpio
ERROR: Data Error : dolphin-22.08.0-1.1.x86_64.cpio

Have you tried using a USB stick instead of a DVD?

If there were “corrupted .rpm files for every recent snapshot,” I would expect to see multiple reports of it on mailing lists/forums etc.

It looks like I have to have Linux to write the image to USB, and this is my first install in years, so: no.

The net install image (that most people use) is not affected, because it is so small.

What is the reason for using 7zip on an installation media at all? This is a useless/unnecessary/wrong usage at all. It seems that you alter the iso’s with 7zip and thats also the reason why you get so many complaints whilst installation later on…
Can you explain why you use 7zip for what reason and what are you doing?

Here is the howto for creating USB installation media under Windows: https://en.opensuse.org/SDB:Create_a_Live_USB_stick_using_Windows

No, you do not. You just need a program that writes image as image (effectively in dd mode) to the correct location on USB. There is dd for Windows, there is rawwrite with GUI and other programs that support raw image mode.

I ran into the errors when installing from DVD, then I investigated, and 7Zip appears to be useful. “7z.exe t” does not change the image.

It is the Tumbleweed INSTALLER that CANNOT READ the install files. And it HAS to work from DVD, or it is broken. I should have made screenshots, but I was not sure whether the DVD drive or some drivers damage the data.

  • did you try an other DVD-Writer? Your DVD-writer may be broken…
  • did you try another DVD drive (external one as example) as your reader may be broken
  • Did you verify the install image after burning it to the DVD?
  • are you using an old DVD-RW which was used several times?
  • …as pointed out by other users: there is no report of broken/damaged Tumbleweed images except yours…

Hi
In addition to above, you also need to ensure you burn the DVD at the slowest possible speed.

To be clear you do not need 7zip for anything just do a direct binary copy (https://www.osforensics.com/tools/write-usb-images.html can be used) to the install media. for DVD do an ISO copy. The download ISO is ready without modification.

I use ImageUSB v1.3 to write TW images to USB on Windows.