F44 KDE Beta succeeded but checking the ISO failed

I just installed F44 KDE Beta on a new x86 laptop, overwriting Windows. The hardest part was getting the laptop to recognize my boot USB drive but that’s not a Fedora issue.

I created the boot drive by downloading Fedora-KDE-Desktop-Live-44_Beta-1.2.x86_64.iso from Fedora KDE Plasma Desktop | The Fedora Project and I used Fedora Media Writer to write the USB drive.

When I finally was able to boot from the USB drive, a list of three options appeared. The default was to test the USB drive and before I could read through all my choices and make a selection, the test option was chosen. The result was ‘FAIL’. Here are most of the error messages that I saw:

Supported ISO: No

ERROR conflict detected with stolen region …

[ 16.492628] dracut-initqueue[741]: Job for checkisomd50dev-sdb.service failed because the control process exited with error code.
[ 16.492779] dracut-initqueue[741]: See “systemctl status checkisomd50dev-sdb.service” and “journalctl -xeu checkisomd50dev-sdb.service” for details.
[ 16.493467] dracut-initqueue[684]: Warning: Media check failed! We do not recommend using this media. System will halt in 12 hours

I tried to type the systemctl and journalctl commands above but I did not have a shell prompt nor was it clear how to get such a prompt.

I also saw “Press [ESC] to abort check.” but pressing Esc did nothing. Neither did pressing any of the function keys. Finally, I tried ctrl-alt-delete and the system rebooted. This time I opted for the first choice which was to boot from the USB drive. That worked and the rest of the installation went smoothly.

Despite the issues, I’m a happy camper. I’m posting this to give the Anaconda team some feedback. If you have questions for me, and I can answer them easily, I will do so. But I am not redoing the installation.

1 Like

The same happened with my F43 install and its a known error. As you have already worked out, just bypass the check.

1 Like

Indeed. See:

From that thread you can get a flavour of where the issue sits. Feels like we more or less understand the problem, but choosing and implementing a strategy to fix it isn’t
straightforward.

1 Like