Difference between revisions of "Installation Troubleshooting/9.2"

From PC-BSD Wiki
Jump to: navigation, search
m
(46 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<noinclude>{{NavHeader|back=Post Installation|forward=Advanced Installation Topics}}</noinclude><noinclude>[[category:troubleshooting]]</noinclude> <!-- This category tag causes this page to be included -for referencing this topic -->
+
<noinclude><translate>
Installing PC-BSD is usually an easy process that "just works". However, sometimes you will run into a problem. This section will look at solutions to the most common installation problems.
+
  
===Network Installation Fails===
+
<!--T:1-->
 +
{{NavHeader|back=Logging In|forward=Advanced Installation Topics}}</noinclude>
  
When installing over the network, the PC-BSD installer will try to configure any Ethernet interfaces using DHCP. Occasionally it will fail to get an IP address and will be unable to connect to the FTP mirror to get the files needed by the installer. You will know this is the case when the mirror list shown in Figure 4.2b remains greyed out.
+
<!--T:2-->
 +
Installing PC-BSD® is usually an easy process that "just works". Sometimes, however, you will run into a problem. This section will look at solutions to the most common installation problems.
  
You can manually retry getting an IP address from the terminal. To access a terminal, right-click an area on the desktop outside of the installation window and select xterm from the menu. Type '''ifconfig''' in the terminal to find out the FreeBSD names for your interfaces. You are looking for an Ethernet entry that shows a status of active. In the example shown in Figure 3.13a, the interface ''em0'' is active but does not have an IP address.
+
=== Installation Starts But Fails === <!--T:3-->
  
'''Figure 3.13a: Using ifconfig to Determine IP Address'''
+
<!--T:4-->
 +
The PC-BSD® installer creates a log which keeps a record of all the steps that are completed as well as any errors. When an installation error occurs, the PC-BSD® installer will ask if you would like to generate an error report. If you click "Yes", a pop-up message will ask if you would like to save the error log to a USB stick. Type '''y''' and insert a FAT formatted USB thumb drive to copy the log.
  
[[File:ifconfig.png]]
+
<!--T:5-->
 +
While in the installer, you can read this log to see what went wrong. Right-click an area on the desktop outside of the installation window and select "xterm" from the menu. You can read the log with this command:
  
Once you know the name of the interface, use it with the '''dhclient''' command as seen in Example 3.13a.
+
<!--T:6-->
 +
{{txtbox|box='''more /tmp/pc-sysinstall.log'''}}
  
'''Example 3.13a: Using dhclient to Obtain an IP Address'''
+
<!--T:7-->
 +
If you can not figure out how to fix the error or believe that you have discovered an installation bug, send the log that was saved on the USB stick to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/support|txt=Support}} mailing list.
  
'''dhclient em0'''
+
=== System Does not Boot Into the Installer=== <!--T:8-->
DHCPREQUEST on em0 to 255.255.255.255 port 67
+
DHCPACK from 192.168.2.1
+
bound to 192.168.2.10 -- renewal in 43200 seconds.
+
  
If you can obtain an IP address, you should be able to select a mirror to install from and continue with the installation.
+
<!--T:9-->
 +
If the installer does not make it to the initial GUI installer screen, try unplugging as many devices as possible, such as webcams, scanners, printers, USB mice and keyboards. If this solves the problem, plug in one piece of hardware at a time, then reboot. This will help you pinpoint which device is causing the problem.
  
===Installation Fails===
+
<!--T:10-->
 +
If your computer freezes while probing hardware, and unplugging extra devices does not fix the problem, it is possible that the installation media is corrupt. If the [[Obtaining_PC-BSD®#Data_Integrity_Check | checksum]] on the file you downloaded is correct, try burning the file again at a lower speed.
  
The PC-BSD installer creates a log which keeps a record of all the steps that completed as well as any errors. Should the installation fail, you can access this log to see what went wrong. To access a terminal, right-click an area on the desktop outside of the installation window and select xterm from the menu. You can read the log with this command:
+
<!--T:11-->
 +
If the system freezes and you suspect the video card to be the cause, review your system's BIOS settings. If there is a setting for video memory, set it to its highest value. Also check to see if the BIOS is set to prefer built-in graphics or a non-existent graphics card. On some systems this is determined by the order of the devices listed; in this case, make sure that the preferred device is listed first. If you cannot see your BIOS settings you may need to move a jumper or remove a battery to make it revert to the default of built-in graphics; check your manual or contact your manufacturer for details.
  
'''more /tmp/pc-sysinstall.log'''
+
<!--T:12-->
 +
If that change did not help, try rebooting and selecting option "''7. Escape to loader prompt''" from the boot menu shown in Figure 4.9a.
  
If you can't figure out how to fix the error or believe that you have discovered an installation bug, send this log to the [http://lists.pcbsd.org/mailman/listinfo/support Support] mailing list. When an installation error occurs, the PC-BSD installer will ask if you would like to generate an error report. If you click Yes, a pop-up message will ask if you would like to save the error log to a USB stick. Type '''y''' and insert a FAT formatted USB thumb drive to copy the log.
+
<!--T:13-->
 +
[[File:Welcome.jpeg|thumb|393px|'''Figure 4.9a: PC-BSD® Installer Boot Menu''']]
  
===System Doesn't Boot===
+
<!--T:14-->
 +
Selecting this option will open the boot loader prompt where you can type the following commands:
  
If the installer doesn't make it to the installer boot screen, seen in Figure 3.13b, try unplugging as many devices as possible, such as webcams, scanners, printers, USB mice and keyboards. If this solves the problem, plug in one piece of hardware at a time, then reboot. This will help you pinpoint which device is causing the problem.
+
<!--T:15-->
 +
{{txtbox|box='''unload'''
 +
'''disable-module vesa'''
 +
'''set module_path=/boot/kernel;/boot/modules;CONSOLE'''
 +
'''boot'''}}
 +
 +
Those commands will disable the vesa splash screen before attempting to boot the installer.
  
'''Figure 3.13b PC-BSD Welcome Screen'''
+
<!--T:16-->
 +
A not uncommon cause for problems is the LBA (Logical Block Addressing) setting in the BIOS. If your PC is not booting up before or after installation, check your BIOS and turn LBA off (do not leave it on automatic).
  
[[Image:Welcome.jpeg]]
+
<!--T:17-->
 +
If the SATA settings in your BIOS are set to "compatibility" mode, try changing this setting to "AHCI". If the system hangs with a BTX error, try turning off AHCI in the BIOS.
  
If your computer freezes after the installation boot menu (while probing hardware) and unplugging extra devices did not fix the problem, it is possible that the installation media is corrupt. If the MD5 on the file you downloaded is correct, try reburning the file at a lower speed.
+
=== USB Keyboard Does not Work in Installer === <!--T:18-->
  
If the system freezes after the PC-BSD boot screen loads and you suspect that the video card is causing the system to freeze, review your system's BIOS settings. If there is a setting for video memory, set it to its highest value. Also check to see if the BIOS is set to prefer built-in graphics or a non-existent graphics card. On some systems this is determined by the order of the devices listed; in this case, make sure that the preferred device is listed first. If you cannot see your BIOS settings you may need to move a jumper or remove a battery to make it revert to the default of built-in graphics; check your manual or contact your manufacturer for details.  
+
<!--T:19-->
 +
If the USB keyboard is non-functional, check if there is an option in your BIOS for ''legacy support'' in relation to the keyboard or to USB, or both. Enabling this feature in your BIOS may solve this issue.
  
If that change did not help, try rebooting and selecting option "7. Escape to loader prompt" from the boot menu. This will open the boot loader prompt where you can type the following commands:
+
=== mountroot prompt === <!--T:20-->
 
+
'''unload'''
+
'''disable-module vesa'''
+
'''set module_path=/boot/kernel;/boot/modules;CONSOLE'''
+
'''boot'''
+
+
That will disable the vesa splash screen and boot the system to an emergency console. From there you can try vesa mode, or drop to a shell and modify ''/etc/X11/xorg.conf'' to change your display settings.
+
  
A not uncommon cause for problems is the LBA (Logical Block Addressing) setting in the BIOS. If your PC is not booting up before or after installation, check your BIOS and turn LBA off (don't leave it on automatic).
+
<!--T:21-->
 +
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 ''?'' at the prompt should display available devices.
  
If the SATA settings in your BIOS are set to "compatibility" mode, try changing this setting to "AHCI".
+
=== Getting Help === <!--T:22-->
  
===Getting Help===
+
<!--T:23-->
 +
If none of the above has fixed your problem, search the {{citelink|url=http://forums.pcbsd.org/|txt=PC-BSD® forums}} to see if a solution exists, try a web search, or check the section on [[Finding Help]].
  
If none of the above has fixed your problem, search the [http://forums.pcbsd.org/ PC-BSD forums] to see if a solution exists, try a Google search, or check the section on [[Finding Help]].
+
<!--T:24-->
<noinclude>[[category:handbook]]</noinclude>
+
<noinclude>
 +
{{refheading}}
 +
[[category:Installation Troubleshooting]]
 +
[[category:Post Installation Configuration and Installation Troubleshooting]]
 +
[[category:handbook]]
 +
[[category:Post Installation]]
 +
[[category:troubleshooting]]
 +
</translate>
 +
<languages />
 +
</noinclude>

Revision as of 16:51, 23 April 2013

(Sorry for the inconvenience)

Contents

Installing PC-BSD® is usually an easy process that "just works". Sometimes, however, you will run into a problem. This section will look at solutions to the most common installation problems.

Installation Starts But Fails

The PC-BSD® installer creates a log which keeps a record of all the steps that are completed as well as any errors. When an installation error occurs, the PC-BSD® installer will ask if you would like to generate an error report. If you click "Yes", a pop-up message will ask if you would like to save the error log to a USB stick. Type y and insert a FAT formatted USB thumb drive to copy the log.

While in the installer, you can read this log to see what went wrong. Right-click an area on the desktop outside of the installation window and select "xterm" from the menu. You can read the log with this command:

more /tmp/pc-sysinstall.log

If you can not figure out how to fix the error or believe that you have discovered an installation bug, send the log that was saved on the USB stick to the Support[1] mailing list.

System Does not Boot Into the Installer

If the installer does not make it to the initial GUI installer screen, try unplugging as many devices as possible, such as webcams, scanners, printers, USB mice and keyboards. If this solves the problem, plug in one piece of hardware at a time, then reboot. This will help you pinpoint which device is causing the problem.

If your computer freezes while probing hardware, and unplugging extra devices does not fix the problem, it is possible that the installation media is corrupt. If the checksum on the file you downloaded is correct, try burning the file again at a lower speed.

If the system freezes and you suspect the video card to be the cause, review your system's BIOS settings. If there is a setting for video memory, set it to its highest value. Also check to see if the BIOS is set to prefer built-in graphics or a non-existent graphics card. On some systems this is determined by the order of the devices listed; in this case, make sure that the preferred device is listed first. If you cannot see your BIOS settings you may need to move a jumper or remove a battery to make it revert to the default of built-in graphics; check your manual or contact your manufacturer for details.

If that change did not help, try rebooting and selecting option "7. Escape to loader prompt" from the boot menu shown in Figure 4.9a.

Figure 4.9a: PC-BSD® Installer Boot Menu

Selecting this option will open the boot loader prompt where you can type the following commands:

unload

disable-module vesa set module_path=/boot/kernel;/boot/modules;CONSOLE

boot

Those commands will disable the vesa splash screen before attempting to boot the installer.

A not uncommon cause for problems is the LBA (Logical Block Addressing) setting in the BIOS. If your PC is not booting up before or after installation, check your BIOS and turn LBA off (do not leave it on automatic).

If the SATA settings in your BIOS are set to "compatibility" mode, try changing this setting to "AHCI". If the system hangs with a BTX error, try turning off AHCI in the BIOS.

USB Keyboard Does not Work in Installer

If the USB keyboard is non-functional, check if there is an option in your BIOS for legacy support in relation to the keyboard or to USB, or both. Enabling this feature in your BIOS may solve this issue.

mountroot prompt

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 ? at the prompt should display available devices.

Getting Help

If none of the above has fixed your problem, search the PC-BSD® forums[2] to see if a solution exists, try a web search, or check the section on Finding Help.


References


  1. http://lists.pcbsd.org/mailman/listinfo/support
  2. http://forums.pcbsd.org/
Other languages:German 12% • ‎English 100% • ‎French 8%