Difference between revisions of "Install troubleshooting"
From Amahi Wiki
Line 1: | Line 1: | ||
+ | = /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: | Some have reported an error similar to the following while attempting to install Fedora on a machine that was previously used for Windows 10: | ||
<pre>[ OK ]Started Show Plymouth Boot Screen. | <pre>[ OK ]Started Show Plymouth Boot Screen. | ||
Line 15: | 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. | 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 = | ||
+ | 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: | ||
+ | ipconfig /all | ||
+ | :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. |
Revision as of 02:08, 17 February 2017
/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 via http://hda
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:
ipconfig /all
- 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.