Fedora 41 checksum

Ask Fedora
,
1

Hi, when I download Fedora 41 and then compare the checksum, I get this message:
… Downloads]$ sha256sum -c Fedora-Workstation-41-1.4-x86_64-CHECKSUM
Fedora-Workstation-Live-x86_64-41-1.4.iso: OK
sha256sum: WARNUNG: 17 Zeilen sind nicht korrekt formatiert =
WARNING: 17 lines are not formatted correctly
What does this mean?

I then made a USB stick and ran the test before installing. I got a message that there was a problem with the checksum. Unfortunately I haven’t written down the exact text.

How can I still install Fedora?

2

These lines are the embedded pgp signature which is use when you run gpg --verify command. They look somthing like that:

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEERmzy2LYLwwV6qUU+0GIkYumdatEFAmcg/rYACgkQ0GIkYumd
atFWGA/9FwfMG/oyZSU/8SkZWzhBTf3uhQbQWLrvJtZo3VXdi93bbRIv1OSCEra5
O1S56mWe453D/fn4/V8CKfRSYKWscq4R5PVQ7K5PoxeupdVGqsk4PTzCAHH9Zx9X
PSgrylfH8jdGLKnj9lXQMjI2mJbRWOs3paWs/P2/g2sp36RVRjdYWoE+M1lRmYHl
H8C2gTN9bz6TDbUPPiRCjlIx2A2JsKo2EYVrexUick31FLUQStDrWVmSh8nDadr9
EiWuZqJZnYMyaqWXMuy0W+qYXonWXNFNMgtXdlAFr7xZxo74btnlwQGSljHtquKd
FioV9yyPvrd75OEHCqLaI+ruHZbnJpOwiT6FuIatcXZ936mt2olLmG+TEEiSPHrg
YL/YmvmZDfXoLrfVCn5f7N4eo+vn/6J7RM/TNbZf1v4arhOrvzL893jtmL6oJWC3
/NUvZLZuBlfuDyMjKq+VrfclTDsZQNoXwuYxntNMjyBkPWkyO+PxkizJdv571Ifa
hTyM0ezLnZAb+7lRV+1BljiG2N/XkkVneWVeaqsbMbv+eYc/fjXiqFnaAXTeJnjS
nREt7VpQfVbPYBHPxWQ/CdpSBaiJk9926DVxqf02zPOf6NwZBd1kMt8ocDlprlBY
CgKNMAN2Dgb0V2MPt8grC16Hvl1FyTJjwT8nIkF/Jk4sElYSu28=
=Zisu
-----END PGP SIGNATURE-----
3

Hallo @vekruse
does it mean that everything is OK? Or is the ISO not OK?

When I then try to install, I get the following message:

grafik
grafik1624×285 167 KB

Failed to start checkisomd50dev-sdc.service …

Am I the only one to whom this happens?

4

That is quite common and that happes after you used MediaWriter on Windows to create the USB bootable device. The Windows system will create some extra files on ESP file system found on the USB device. This makes the internal checksum invalid. The USB device can still be used when you skip the check.

1 Like
5

That’s what you are looking for.
The remaining 17 checksums are for different ISO Images.

You are good to go.

1 Like
6

The CHECKSUM file for Workstation only have the checksum for the Workstation iso file. The CHECKSUM for the spin versions, however, have checksum for all the spin versions. For example:

[vek@newbox fc41]$ sha256sum -c --ignore-missing Fedora-Spins-41-1.4-x86_64-CHECKSUM
Fedora-Sway-Live-x86_64-41-1.4.iso: OK
Fedora-Xfce-Live-x86_64-41-1.4.iso: OK
sha256sum: WARNING: 17 lines are improperly formatted
[vek@newbox fc41]$
7

Hallo @vekruse hallo @augenauf
my Mediabuilder was SUSE Studio Imagewriter.
Schön, dass alles ok ist, ich werde gleich installieren, freue mich schon!

8

Then I don’t know. On SUSE you can use the dd command to write the iso image directly to the the USB device, for example to /dev/sdb or /dev/sdc, etc.

Just make sure the USB device isn’t (auto)mounted.

9

Hallo @vekruse
I don’t have Suse, but Manjaro. But I use the SUSE imagewriter. Oh, and one more thing, two weeks ago I tried Fedora 40, also with SUSE Imagewriter, and the pre-install test was successful.

I have a few questions about the installation. I want to test Fedora on an old PC. Which partitions do I have to create? I know from other Linux systems that you have to create a fat32 partition for bios boot. Is that also the case here?

10

This applies to the lines that are part of the gpg signature and is entirely normal for doing the sha256 sum.
These are what are checked when the user verifies that file.
The verification process is shown on the download page by clicking on the green folder with the check.
image

and shows this

image

Following those steps does the verification step by step.

11

Any linux system have the dd command, and all unix systems as well including mac I beleive.

Just remove all partitions and then when installing select autmatic partitioning. That will create the fat32 file system if it is needed and the rest will be a btrfs file system.

12

Does anyone know what this means?

Unable to create PID file
Anaconda is unable to create /var/run/anaconda.pid because the file already exist. Anacona is already running, or a previow instance of anaconda has crashed.

14

Hello, @vekruse

I checked iso (it checks normally on vm), created bootable usb with dd on linux, checked usb using badblocks but still getting “Failed to start check checkisomd5@dev-sda.service - Media check on /dev/sda” after 100% (not 4.8%) check

15

I have now made the USB stick with the Fedora-tool, then it passed the test during installation. After the installation via the automatic in the free area, I can no longer boot Manjaro, (although the partition of / and /home are still present) only Fedora and Windows.

If I then install Manjaro again, Fedora disappears from the Grub boot selection. How do you do this correctly?

Or is Fedora not so well suited for dual boot?

16

If you can, select the OS from the UEFI boot menu. From the grub boot menu, the last entry will usually give you the UEFI boot menu. Configuring multiple linux systems in grub is at best messy and at worst impossible.

PS: it is now getting off topic.

17

Hello @vekruse
Yes, you are absolutely right,

PS: it is now getting off topic.r ein

I will look elsewhere, because I can only ever start the last Linux installed.

18

Added anaconda