Corrupted kernels for Tumbleweed?

English Install/Boot/Login
1

Hi all,

Hi all, I am seeing issues trying to update my AArch64 Tumbleweed installation, after multiple attempts I am seeing still two corrupted kernel packages:

warning: rpmpkg: detected non-zero blob, trying auto repair
error: kernel-default-7.2.6-1.1.aarch64: install failed
( 13/1047) Installing: kernel-default-7.2.6-1.1.aarch64 …[error]

Installation of kernel-default-7.2.6-1.1.aarch64 failed:

warning: rpmpkg: detected non-zero blob, trying auto repair
error: kernel-source-7.2.6-1.1.noarch: install failed
( 14/1047) Installing: kernel-source-7.2.6-1.1.noarch …[error]
Installation of kernel-source-7.2.6-1.1.noarch failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.

Not sure who to notify about this, so posting here.

2

This is http://opensuse.mirror.liteserver.nl btw

3

Try

sudo zypper clean -a
sudo zypper ref -f
sudo zypper -vvv dup
4

I actually do both of those every sync. The packages remain broken.

The only thing I have yet o try is forcing another mirror.

1 Like
5

This would have been the obvious thing to do from the very start.

Also check your free disk space.

6

Diskspace is fine, that’s not the issue here.

I know I could make this go away, but I was also hoping to get the packages fixed. I’m not the only AArch64 user on this side of the planet.

7

Having tried other mirrors, I am seeing exactly the same problem

Checking the files downloaded from two different mirrors, they appear to be binary the same. I would need to check on another machine if the other rpm is also corrupted, to be sure but it certainly looks that way.

Also the problem is spreading, the following packages are now showing as corrupted:

kernel-64kb-devel 7.2.7-1.1 aarch64 Main Repository (OSS) openSUSE
kernel-default 7.2.7-1.1 aarch64 Main Repository (OSS) openSUSE
kernel-default-devel 7.2.7-1.1 aarch64 Main Repository (OSS) openSUSE
kernel-devel 7.2.7-1.1 noarch Main Repository (OSS) openSUSE
kernel-source 7.2.7-1.1 noarch Main Repository (OSS) openSUSE
kernel-syms 7.2.7-1.1 aarch64 Main Repository (OSS) openSUSE

I strongly suspect there is a bigger problem here than just me.

8

Btw, this problem still exists, across multiple mirrors and even with the new kernel - all of the following packages are marked as corrupted in the same manner:


Retrieving: kernel-default-7.2.9-1.1.aarch64 (Main Repository (OSS))                                                                                             (1/7), 210.0 MiB
Retrieving: kernel-macros-7.2.9-1.1.noarch (Main Repository (OSS))                                                                                               (2/7),   5.0 MiB
Retrieving: kernel-devel-7.2.9-1.1.noarch (Main Repository (OSS))                                                                                                (3/7),  21.6 MiB
Retrieving: kernel-source-7.2.9-1.1.noarch (Main Repository (OSS))                                                                                               (4/7), 186.0 MiB
Retrieving: kernel-default-devel-7.2.9-1.1.aarch64 (Main Repository (OSS))                                                                                       (5/7),  12.7 MiB
Retrieving: kernel-64kb-devel-7.2.9-1.1.aarch64 (Main Repository (OSS))                                                                                          (6/7),  12.7 MiB
Retrieving: kernel-syms-7.2.9-1.1.aarch64 (Main Repository (OSS))                                                                                                (7/7),   5.0 MiB

Checking for file conflicts: ..................................................................................................................................................[done]
warning: rpmpkg: detected non-zero blob, trying auto repair
error: kernel-default-7.2.9-1.1.aarch64: install failed

Is this something I should take the mailing list? I kinda nievely presumed this would be the place to raise such a thing, clearly not.

9

Can you try:

sudo rpm --verifydb

10

That returns nothing, and doesn’t seem to solve the issue.

11

… however, combing the above and this in particular come with something that did help

Note that sudo rpm --verifydb returned no output but success, which would make one assume that the database is fine…

However sudo rpm --rebuilddb actually fixed the issue, as per here: Zypper error "rpmpkg: detected non-zero blob, trying auto repair" - #6

Things I don’t entirely understand:

  • Why this disease fixated on the kernel packages in particular, and followed those packages through two versions - other packages installed just fine, throughout this entire time. I am presuming this is something to do with dependencies.
  • Why rpm --verifydb did not show up the issue even though the database was quite obviously corrupted.
  • Why the error message here is so deliberately vague…

This is clearly a recurring issue, however rare it may actually be. Unless there is anyone here who has deep understanding of rpm, I suspect this might be worth at least raising issues on rpm for.

12

Maybe, but (s)he will probably not become triggered by the title of this topic.

13

The man page of rpmdb explains it:

Diagnostics
–verifydb
Perform a low-level integrity check on the database. Rarely
useful, for system health rpm --verify -a is a far more
meaningful operation.

–rebuilddb
Rebuild the database from the installed package headers.
Discards any unreadable (corrupt) headers and compacts the
database in case it has grown large over time.
Can also be used to convert between different rpmdb formats.