I’m having an odd problem with a Dell laptop, I can’t get it to install Fedora. Everytime I boot from the USB and choose the “Test media and Install Fedora” option, It gives the media check error. As in:
The media check is complete, the result is: FAIL.
These are the things I’ve tested:
- Using a second USB from another brand
- Using another USB port with either USB
- Using Fedora Workstation 40 and Fedora Silverblue 40
- Creating bootable disks with: Fedora Media Writer, Gnome Disks or Popsicle (from Pop OS)
Other Linux OS that also test their media before system setup all work with the Dell. I’ve already used that machine for some time with multiple Ubuntu spins and derivatives. The USBs also pass the media check in other laptops (HP and Acer) and can be used to install Fedora. Therefore, I can reliably say that the problem isn’t a result of faulty USBs, USB ports or ISOs (which I already verified as instructed).
Another odd thing I’ve noticed is that I can create a bootable USB in the Dell and they work as intended when they are booted in another laptop. However, when I try to boot the Fedora bootable setup USB in the Dell and reach the media check error, that error is then replicated in other laptops too.
These were on the Dell but not on other laptops:
The media check is complete, the result is: FAIL.
It is not recommended to use this media.
[FAILED] Failed to start checkisond5@dev-sdb.service — Media check on sdev/sdb.
[ 118.912749] dracut-initquene[1549]: Job for checkisomd5@dev-sdb.service failed because the control process exited with error code.
[ 118.912832] dracut-initqueue[1549]: See “systemctl status checkisomd5@dev-sdb.service” and “journalctl -xeu checkisomd5@dev-sdb.service” for details.
[ 118.931173] dracut-initqueue[1424]: Warning: Media check failed! We do not recommend using this medium. System will halt in 12 hours
Everything else including the fragment sum
and the fragment count
were the same. ACPI errors were also there but apparently don’t prevent Fedora setups.
Can you please help me troubleshoot this problem?