Package plexmediaserver-1.43.0.10389-8be686aa6.x86_64 does not verify

Plex Media Server
1

Server Version#:Version 1.43.0.10346
Player Version#:N/A

dnf localinstall plexmediaserver-1.43.0.10389-8be686aa6.x86_64.rpm

Last metadata expiration check: 1:31:34 ago on Thu 04 Dec 2025 11:06:21 AM MST.

Dependencies resolved.

===========================================================================

Package Architecture Version Repository Size

===========================================================================

Upgrading:

plexmediaserver x86_64 1.43.0.10389-8be686aa6 @commandline 103 M

Transaction Summary

===========================================================================

Upgrade 1 Package

Total size: 103 M

Is this ok [y/N]: y

Downloading Packages:

Running transaction check

Transaction check succeeded.

Running transaction test

Error: Transaction test error:

package plexmediaserver-1.43.0.10389-8be686aa6.x86_64 does not verify: Payload SHA256 ALT digest: BAD (Expected e463f006b392af87bfea354dc43ef14799cdaa4522c6f95b527c509722039ce3

!=

28282987aa10ef6fe6e44c6230d003eb76e4fd4a541b69af7d63b477917c7ad2)

2

As its a sha256 checksum error I suspect the rpm is corrupt. My rpm sizes are below …

[plex]-[dokuro]:/data/Personal/Scripts]$ ls -lh ../Software/fedora/plexmediaserver-1.43.0.10389-8be686aa6.x86_64.rpm 
-rw-r--r-- 1 plex plex 104M Dec  3 18:00 ../Software/fedora/plexmediaserver-1.43.0.10389-8be686aa6.x86_64.rpm
[plex]-[dokuro]:/data/Personal/Scripts]$ ls -la ../Software/fedora/plexmediaserver-1.43.0.10389-8be686aa6.x86_64.rpm 
-rw-r--r-- 1 plex plex 108368751 Dec  3 18:00 ../Software/fedora/plexmediaserver-1.43.0.10389-8be686aa6.x86_64.rpm
[plex]-[dokuro]:/data/Personal/Scripts]$

Delete the file, download it again and try the install again.

3

Extremely odd.

Redownloaded, same behavior. Size matched your files. Deleted file, redownloaded. Worked.

Redownloading, without manually deleting the old file did not work. Not sure I understand what was happening. Appreciate the support.

bill.

4

I’d suggest running a disk check on the drive. This type of odd behaviour maybe a early symptom of a drive failure.