Install troubleshooting - Revision history

Bigfoot65 at 00:35, 25 May 2017

2017-05-25T00:35:50Z

2017-05-25T00:34:24Z

Network not available after reboot

2017-04-21T01:53:50Z

Cannot access HDA Dashboard

2017-04-21T01:51:38Z

2017-04-11T00:23:58Z

Cannot access HDA Dashboard

2017-04-11T00:23:09Z

Cannot access HDA Dashboard

2017-02-22T01:05:18Z

Failed to synchronize cache for repo 'xxxxxx'

2017-02-22T01:04:03Z

Failed to synchronize cache for repo 'xxxxxx'

2017-02-21T22:13:44Z

2017-02-17T02:08:55Z

Cannot access HDA via http://hda

← Older revision		Revision as of 00:35, 25 May 2017
Line 56:		Line 56:
	= Installer Crashes =		= Installer Crashes =
	Installer crashes with non-Intel raid system (see [https://forums.amahi.org/viewtopic.php?p=38957&sid=315004eeba97ed605d4886d6b3f2cdd9#p38957 forum post] for details)		Installer crashes with non-Intel raid system (see [https://forums.amahi.org/viewtopic.php?p=38957&sid=315004eeba97ed605d4886d6b3f2cdd9#p38957 forum post] for details)
		+
		+
		+	Back to the [[Troubleshooting]].

← Older revision		Revision as of 00:34, 25 May 2017
Line 52:		Line 52:

	= Network not available after reboot =		= Network not available after reboot =
−	See [https://bugs.amahi.org/issues/2046 Amahi Bug #2046] for details.	+	Sometimes it takes 2 or 3 reboots before the networking starts working properly. See [https://bugs.amahi.org/issues/2046 Amahi Bug #2046] for details.
		+
		+	= Installer Crashes =
		+	Installer crashes with non-Intel raid system (see [https://forums.amahi.org/viewtopic.php?p=38957&sid=315004eeba97ed605d4886d6b3f2cdd9#p38957 forum post] for details)

← Older revision		Revision as of 01:53, 21 April 2017
Line 50:		Line 50:
	systemctl stop rolekit		systemctl stop rolekit
	systemctl disable rolekit		systemctl disable rolekit
		+
		+	= Network not available after reboot =
		+	See [https://bugs.amahi.org/issues/2046 Amahi Bug #2046] for details.

← Older revision		Revision as of 01:51, 21 April 2017
Line 1:		Line 1:
		+	__TOC__
	= Failed to synchronize cache for repo 'xxxxxx' =		= Failed to synchronize cache for repo 'xxxxxx' =

@@ Line 44: / Line 44: @@
 :Reboot and then check things again.
-Executing the following commands have also helped with this issue:
+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

← Older revision		Revision as of 00:23, 11 April 2017
Line 43:		Line 43:
	sudo dnf update		sudo dnf update
	:Reboot and then check things again.		:Reboot and then check things again.
		+
		+	Executing the following commands have also helped with this issue:
		+	systemctl stop firewalld
		+	systemctl disable firewalld
		+	systemctl stop rolekit
		+	systemctl disable rolekit

@@ Line 1: / Line 1: @@
 = 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 up to date.
+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 sudo):
+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 <code>sudo</code>):
     dnf -y install chrony
@@ Line 9: / Line 9: @@
     systemctl start chronyd
-Shortly after these are run the system time should be up to date and installing packages should be working well.
+Shortly after these are run, the system time should be up to date and installing packages should work.
 = /dev/root does not exist =

@@ Line 16: / Line 16: @@
 This appears to be related to UEFI firmware associated with the hardware.  Refer to [https://www.happyassassin.net/2014/02/04/more-on-booting-a-practical-fedora-uefi-guide-and-dont-use-universal-usb-stick-writers More on booting: a practical Fedora UEFI guide, and don’t use “universal” USB stick writers] for the solution.
-= Cannot access HDA via http://hda =
+= Cannot access HDA Dashboard =
 Some have had problems accessing the HDA Dashboard after a new install.