Installing dual boot fails, likely due to previous dual boot system

Ask Fedora
1

Dear all,
I am struggling with installing a dual boot with Windows 11.

The problem is likely due to previous dual systems with ubuntu and fedora.

The whole stuff is running on an ASUS ROG-Flow.

I tried a bunch of things but I guess what I need is a real wipe of all the stuff thats on the machine.

What I tried: manually deleting parts of Linux from the UEFI. Replacing the UEFI with software directly from ASUS. Reinstalling windows of course.

Any Idea or hints of direction? I would be very greateful! I don’t want to be stuck with Windows.

Screenshot and text from that is below, hope this is sufficient.

All the best, Johannes

Fedora_error_IMG_3395
Fedora_error_IMG_33951920Ă—1044 351 KB

ACP BIOS Error (bug): Failure creating named object [_SB.PCIO.GP17.HCO._SOW], AE_ALREADY_INISTS (20240322/dswload2-326)

ACPI Error: AB_ALREADY_EXISTS, During name lookup/catalog (20240322/psob ject-220)

ACPI BIOS Error (bug): Failure creating named object [_SB.PCI0.GP17.XHC1, SOW1, AE_ALREADY_EXISTS (20240322/dswload2-326)

ACPI Error: AB ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)

1 Started plynouth-start.service - Show Plymouth Boot Screen.

L L

OK OK OK OK

1 Started systend-ask-password-plunouth.path - Forward Password Requests to Plymouth Directory Watch.

1 Reached target cryptsetup.target - Local Encrypted Volumes.

1 Reached target paths. target - Path Units.

1 Stopped systend-uconsole setup.service - Virtual Console Setup.

Stopping systend-console-setup.service - Virtual Console Setup…

Starting systend-console-setup.service - Virtual Console Setup…

OK

1 Stopped systend-console setup.service - Virtual Console Setup.

Starting systend-console-setup.service - Virtual Console Setup…

[

OK

] Finished systend-uconsole setup.service - Virtual Console Setup.

Mounting sys-kernel-config-mount - Kernel Configuration File Systen…

ITL

OK

1 Mounted sys-kernel-config.mount - Kernel Configuration File System.

OK

3 Reached target sysinit. target - System Initialization.

OK

I Reached target basic.target - Basic System. asus 0003:0B05:19B6.0002: Asus input not registered

asus 0003:005:196.0002: probe with driver asus failed with error -12 /dev/sda:

b11bdbOec8c5b2f1661492e17233adc1

Fragment sums: 32121d3bbb21a1f2144e5baBc2648617fb1d7cd6ffb7e7cda36f3487462

Fragment count: 20

Supported ISD: no

Press [Esc] to abort check.

Checking: 004.8%

The media check is complete, the result is: FAIL.

It is not recommended to use this media.

IPALLED Pailed to start checkisondsedeu-sda.service - Media check on /deu/sda.

11,103938] dracut-initqueue{1041]: Job for checkisondSedev-sda.service failed because the control process exited with error code.

11,104029] dracut-initqueuel1041]: See “systemctl status checkisond50deu-sda.service” and “journalctl -xeu checkisondSedeu-sda.service” for details.

11.104527] dracut-initqueuel982]: Warning: Media check failed We do not recommend using this medium. Systen will halt in 12 hours

2

A windoze install will often mess up a Linux install so windoze should be installed before Linux. You may need to shrink the windoze OS partition if it has ungraciously occupied an unreasonably large amount of disk space. Booting a SystemRescue USB will provide access to gparted, a tool that I find most convenient for partition management.

Two or more cooks in a kitchen can lead to frustration and disappointment. I have several Linux installations on an m.2 NVMe SSD. One method for achieving peaceful co-oexistence is to create a UEFI partition and a data partition for each Linux installation ignoring the UEFI partition created by the windoze installation before installing Linux. I find it helpful to name the partititions before an installation because it is possible to install to a partition other than the intended one if that partition does not contain a Linux OS.

Because the UEFI esp will only be used during the boot process by a single OS, it can be as small as 93 Mbs. The annaconda installer will expect you to name the esp partition mount point “boot/efi” and the OS partition mount point “/”. You can select custom and standard partition to be able to create an ext4 file system instead of the default btrfs.

Archiving, restoring and migrating a bootable Linux partition is much less complex if that partition was formatted as ext4. The efibootmgr command may be used to change the boot order to what you desire.

3

The error being seen with the failed media check will often occur if you connect the usb device containing the fedora image while windows is running. The act of mounting that device in windows writes something to it that then causes the verification to fail…

The fix is simple.

  1. download the image
  2. Verify the image that was downloaded using the checksum file that is also linked on the download page.
  3. Write the image to the usb device
  4. Do not plug it into a machine that has a running windows OS
  5. boot from the usb device directly and perform the installation.

As long as the downloaded image is valid and the checksum verifies it the media check during boot is not normally necessary.

1 Like
4

Thanks a lot this sounds very reasonable and good to implement. I will test this immediately. Just one detail question: Is it fine to create the usb boot device on windows, I just have to make sure to connect it to the laptop when windows is shut down?

5

Yes, that usually works properly.