Fedora Installation fails consistently at 95%

Ask Fedora
, ,
1

Hey,
I’m trying to install Fedora gnome on my laptop (MSI vector16hxai). After checking and booting to the live usb and going through the installer the process fails at the “installing” stage at 95% every time. (On versions 42 & 43 with the error code 23) . I have two M2 SSDs, one with windows on it and another I’m trying to install Linux on. I have had to turn on SATA AHCI mode for the installer to see the disks before running into this issue.
Troubleshooting steps I tried:

  • turning off BitLocker encryption on all drives
  • disabling secure boot
  • using different versions of fedora gnome, using fedora KDE and also using bazzite gnome
  • using basic graphics mode

I would prefer not to take out either of the drives to install fedora since the laptop disassembly is quiet a pain. Also I would like to keep the windows drive like it is (without reinstalling it all).

Any help is appreciated!
Thanks.

2

Try the Everything Netinstaller, or a ReSpin

With the Netinstaller, you can either install a minimal custom install and then install Gnome after, or you can select Gnome to be installed at install time.

The ReSpins are the latest up to date version of Fedora made within the last week.

3

I found an issue as yours.

Fixed in kiwi 10.3, a new iso in the 43.1 release.

I downloaded F44-WORK-x86_64-LIVE-20260513.iso . How do I find out if it is F43.1 alias done with kiwi 10.3?

8

Can you tell us why you try F42 / F43 and not directly F44?

I ask because of the respins, they are just created on the newest Iso’s F44, as it looks like ?!

9

I phrased it poorly, but I tried all three, all had the same issue.

10

Hello there, may I ask have you been able to solve this yet? I have also encountered this problem when trying to install F44. I have also tried every steps you mentioned and also tried removing my drives but to no avail.

11

During the installation the logs are stored in the /tmp directory:

Log files

/tmp/anaconda.log the general installation information, particularly the step changes.

/tmp/storage.log storage devices scan and manipulation (hard drives, partitions, LVM, RAID), partitioning

/tmp/program.log calls to external programs, their output

/tmp/packaging.log DNF package installation messages

/tmp/syslog hardware-related system messages

After a successful installation most of those logs are copied into /var/log/anaconda/

When the installation fails, what errors are reported in any of those log files?

12

Did you try the Everything ISO and a respin?

Do you have Nvidia?

Does F43 work?

13

No I haven’t tried Everything ISO and a respin. Which version should I try?
Yes my laptop has Nvidia card.
No I haven’t had the time to tried F43 yet.

14

Try the latest KDE respin.

If that does not work, try the F43 Everything Netinstall ISO.

15

It looks like they are just made from the stable version:

means last resping is F44 if that serves.

16

For those of you seeing this failure, have you bothered to read back the installation ISO to verify that it matches the hash of the one that you downloaded? (If the network install works but the local ISO install doesn’t, that would be particularly interesting.)

I ask because crashing near the end of the install process is at least consistent with this:

and in particular the data corruption which, at least on my system, usually happens, and concentrates at the tail end of the written ISO image:

Not very likely, but just maybe these problems are related.