Editing Installation Guide

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 97: Line 97:
 
==== Other USB Flash writer tools for Windows ====
 
==== Other USB Flash writer tools for Windows ====
  
Balena Etcher  [https://etcher.io] Works for Windows, macOS, & Linux.
+
Balena Etcher  [https://etcher.io] Works for Windows, macOS, & Linux
 
Rufus  [https://rufus.ie]  Works just for Windows, needs a checkbox selected to do a pure write of .ISO image file
 
Rufus  [https://rufus.ie]  Works just for Windows, needs a checkbox selected to do a pure write of .ISO image file
  
Line 304: Line 304:
  
 
If you boot your system and you receive a ''mountroot>'' command prompt, it may be due to a change in the location of the boot device. This can occur when the installation was made on another machine and then transferring the HDD without an adjustment to the ''/etc/fstab'' file, or if a card reader is involved (including card readers on a USB dongle). The solution is to enter ''ufs:/dev/da1'' at the prompt (it will always be ufs for the installer media). Depending on the exact location of the boot media, it may be different than ''da1.'' Typing <code>?</code> at the prompt should display available devices.
 
If you boot your system and you receive a ''mountroot>'' command prompt, it may be due to a change in the location of the boot device. This can occur when the installation was made on another machine and then transferring the HDD without an adjustment to the ''/etc/fstab'' file, or if a card reader is involved (including card readers on a USB dongle). The solution is to enter ''ufs:/dev/da1'' at the prompt (it will always be ufs for the installer media). Depending on the exact location of the boot media, it may be different than ''da1.'' Typing <code>?</code> at the prompt should display available devices.
 
If you boot your system and on single user mode receive the message Solaris: NOTICE: Cannot find the pool label for 'tank' with error 5. Its generaly a problem of delay with USB HDD. After having the <mountroot>, mount the zfs root file system : type <code>zfs:tank/ROOT/initial</code>. And then, in your /boot/loader.conf, add the line <code>kern.cam.boot_delay="10000"</code>. That instructs the system to wait 10 seconds (10000 milliseconds) during boot to give time for the CAM subsystem probes to complete (USB storage devices use the CAM subsystem).
 
  
 
=== Getting Help ===
 
=== Getting Help ===

Please note that all contributions to GhostBSD Wiki are considered to be released under the Creative Commons Attribution (see GhostBSD Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)