Failed to synchronize cache for repo 'xxxxxx'
If your system cannot seem to "synchronize" and get proper packages during installation, it may be that your system's date and time are way off and not current.
One way to get time/date to be up to date automatically is doing so via the network. Here is how to do it by running these commands as root (directly or via
dnf -y install chrony systemctl enable chronyd systemctl start chronyd
Shortly after these are run, the system time should be up to date and installing packages should work.
/dev/root does not exist
Some have reported an error similar to the following while attempting to install Fedora on a machine that was previously used for Windows 10:
[ OK ]Started Show Plymouth Boot Screen. [ OK ]Reached target path. [ OK ]Reached target Basic System. [23.073611] blk_update_request: I/O error. dev sr0, sector 850520 [23.240764] blk_update_request: I/O error. dev sr0, sector 850520 [23.270797] Buffer I/O error on dev sr0, logical block 106315, async page read [ OK ]Started Show Plymouth Boot Screen. [ OK ]Reached target path. [ OK ]Reached target Basic System. Starting Dracut Emergency Shell... Warning: /dev/root does not exist Generating "/run/inittramfs/rdsosreport.txt"
This appears to be related to UEFI firmware associated with the hardware. Refer to More on booting: a practical Fedora UEFI guide, and don’t use “universal” USB stick writers for the solution.
Cannot access HDA Dashboard
Some have had problems accessing the HDA Dashboard after a new install.
- If you are using a Windows client, check that it's getting the DHCP lease and DNS from the HDA. To do so, from Windows Client command line do:
- If the IP address and/or DNS is not from the HDA, then that's your issue. Probably something related to your router settings.
- Check that the web server is running on the HDA. From command line, do:
sudo systemctl status httpd
- If it's not running, try to start it:
sudo systemctl start httpd
- If there are errors, then recommend you do an OS update:
sudo dnf update
- Reboot and then check things again.
This mainly applies to those doing an upgrade, but executing the following commands has helped some users:
systemctl stop firewalld systemctl disable firewalld systemctl stop rolekit systemctl disable rolekit
Network not available after reboot
Sometimes it takes 2 or 3 reboots before the networking starts working properly. See Amahi Bug #2046 for details.
Installer crashes with non-Intel raid system (see forum post for details)
Back to the Troubleshooting.