Bug 2056043

I personally don't use media-writer, but livecd-creator (https://github.com/livecd-tools/livecd-tools), however, I didn't test it with the Everything ISO.

Nevertheless, I believe, you chose from component in Bugzilla - isomaster - which is "an easy to use GUI CD image editor". You might want to update it to reach  people who can help you.

The ERROR RECOVERY ROUTINE (From the Server ISO) needs to be restored to the Workstation ISO.
 
I would hope it happens before RAWHIDE / Fedora36 is released to Beta.

FOR YOUR INFORMATION,  A POST FROM FEDORAFORUM.ORG

Can't Boot Fedora Workstation 35 from USB?

xxxxxxxxxxxxxxx
xxxxxxxxxxxxxxx is offline Registered User
 
    Good evening,

    I'm trying to install Fedora Workstation 35 alongside Windows 11.

    The first thing I did was disable secure boot in the BIOS of my MSI motherboard. It says it's disabled.

    Then I tried to boot from the USB created using Fedora Media Writer.

    I got a dracut-initqueue[a_number] starting timeout scripts.

    Then I did the same thing again, this time after fully disabling Windows WHQL check.

    I got dracut-iniqueue[different_number] <same message about timeout scripts>

    Then I tried to remake the live USB, both with Rufus and Fedora Media Writer. No luck, same dracut initqueue messages. I think the number is different every time, I have no idea if that is significant.

    I'm not sure where to go from here. I was looking forward to dual booting Fedora, Windows 11, and I've used live USB devices to install and dual boot other Linux distros before without these issues, although not with this computer. 

============================================================
xxxxxxxxxxxxxxx
xxxxxxxxxxxxxxx is offline Registered User
 
Okay. I have more information. The dracut error I get before going to the emergency shell says this:

Warning: /dev/disk/by-label/Fedora-WS-Live-35-1-2 does not exist
Warning: /dev/root does not exist

After this it says it’s entering emergency mode, I can press enter for maintenance mode or control D to continue. This puts me into a shell that lets me do some things

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

Leslie Satenstein
Leslie Satenstein   Fedora user since June 2005

Here is MY RESPONSE


    For some laptop bios versions, I have two 2018 or later Intel versions, I ran into similar problems. I disabled secure boot, and installed Fedora, restored secure boot, and the system refused to boot Fedora. Whats the Fear, I ask? Why the Foolishness? I have 3 laptops, and the two causing problems are the 2018 bios versions or more recent ones (Acer and ASUS) . My older Lenova laptop has a neutral bios and booting any Fedora or other version of Linux lets the Lenova boot without issues..

    Here is what I did. First, on reboot, with secure boot enabled, hold down the (undocumented) F8 key. Does that action provide you with a list of devices, including the USB with the bios? If so, the boot problem is solved.

    If it does not work, disable secure boot, visit your bios setting to change the boot order so that the USB device is recognized and make it first in the list, and then restore secure boot. On a reboot, your Fedora Flashdrive should boot.

    Oh, one more thing, if you are booting using the "Everything ISO", I would forget it, The "Everything ISO" does not have a signed bios or whatever, and it will not work. HOWEVER,
    in it's place, if you use the Server Network iso, the Intel bios will recognize it and use it. The outcome of using the latter is the same or better than using the Everything.iso.

    By the way, the workspace ISO does not have recovery software on it that works, in all cases. For that, use the recovery software that is on the Server Network install ISO. It is "signed".

    I believe that the laptop bios and hardware beginning 2018, were designed to support a TPM, (Trusted Platform Module). Some laptops come with the chip included, some do not.

    Hope the story of my struggles is useful. 

    Leslie in Montreal

Here is a situation.

The Workspace (live) ISO is what we see serving as the ISO of choice by Fedora mediawriter, and currently by all YouTube'ers.

The Workspace live ISO has no functioning error-recovery.  What it terms error recovery is to boot the system in non-propriatory graphics mode.

In further digging by me, if there is a problem with an installation of Workspace live, then one is advised to use the
Everything ISO, and on the Everything ISO, there is the true recovery routine.  

The true recovery routine puts the user into " chroot /mnt/system-image " or some similar text.  

Now, the Everything ISO (F35) is recognized and can be booted from an AMD bios, or from a Lenova bios.
For two laptops (circa 2018) the Everything ISO bios will not load with 2 IBM system bios based systems.

I would say that this is a minor blocker bug if the default advanced terminal user cannot boot the Everything.iso

And here is my other research.   I took the Server network install ISO, in place of the Everything ISO, 
and it is recognized by all my systems. The server network istall ISO seems to fully include the Everything.ISO contents.

My reason for posting this report, is to ask that the Everything bios software for initial boot, is reviewed against
the Server bios, and that tests be made

@LoraxMaintainer, could it be related to lorax?

The issue was originally reported to the isomaster component which is a tool for playing with ISO images not for creating them for Fedora. The problem is definitely not related to isomaster. I have seen #1282244 which helped me to find lorax. If you think it is not lorax related (or lorax fixable) please change the component to the one you think might be a better assignment. Thanks.

Everything netinst and Server netinst are built in exactly the same way. There's no logical reason that one but not the other would boot in any situation. Either both should work or neither should.

Hi Adam.

I downloaded the ISO twice, just in case I had a reception error.  I will retest in the AM.

Please close, 
THe Feb 18 Everything ISO did not work,
The Current (0306) version works as designed.