Performing a Boot Installed System with Network support

This document (3357364) is provided subject to the disclaimer at the end of this document.

Environment

SuSE Linux Enterprise Server 9 (SLES 9)
SuSE Linux Enterprise Server 10 (SLES 10)

Situation

It is possible to have problems with drivers or a boot loader that can keep a system from starting up. Not only is it required to get the system booted so the problem can be fixed, but network access may be required to copy files, etc. This explains how to boot the system with network support enabled.

Resolution

SLES 9 and SLES 10 have the option to 'Boot Installed System' during the install. This will use the kernel and drivers from the installation media, rather than what is on the root partition. To reach the 'Boot Installed System' option and add network support:

Boot from CD1 of the installation media
Highlight Installation and type the following on the Boot Options line before pressing enter:

insmod=

Examples of drivers are e1000, tg3, pcnet32, etc. If you are unsure which driver should be loaded, see the Additional Notes section.

The install will load. Please continue through the following options:

Accept the license
Select Language
Select Boot Installed System (other options are New Installation, Update an existing system, Repair Installed System)
*Note: On SLES 10, you must first select the 'Other' option, you can then select Boot Installed System.

Once the system boots, login as root. The driver is loaded but no IP address is bound. Bind an IP address:

ifconfig eth0 192.168.1.15 netmask 255.255.255.0

If adding a default gateway is required:

route add default gw 192.168.1.1

You should now have network access.

Additional Information

If you are unsure what network driver to use, follow the procedure for 'Boot Installed System' without adding a network driver. This assumes a custom network driver is not being used. Once the the system is up:

Locate the network startup script:

ls /etc/sysconfig/network/ifcfg-eth*

sles9:~ # ls /etc/sysconfig/network/ifcfg-eth*
/etc/sysconfig/network/ifcfg-eth-id-00:0c:29:69:b4:c9
sles9:~ #

There may be more than one if the server has multiple network adapters. Select the one to bind and cat the information from it:

cat /etc/sysconfig/network/ifcfg-eth-id-00\:0c\:29\:69\:b4\:c9

sles9:~ # cat /etc/sysconfig/network/ifcfg-eth-id-00\:0c\:29\:69\:b4\:c9
BOOTPROTO='static'
BROADCAST='192.168.1.255'
IPADDR='192.168.1.15'
MTU=''
NETMASK='255.255.255.0'
NETWORK='192.168.1.0'
REMOTE_IPADDR=''
STARTMODE='onboot'
UNIQUE='7EWs.weGuQ9ywYPF'
_nm_name='bus-pci-0000:00:11.0'
sles9:~ #

Make note of the hardware address after _nm_name=
Then type:

cat /etc/sysconfig/hardware/hwcfg-

sles9:~ # cat /etc/sysconfig/hardware/hwcfg-bus-pci-0000\:00\:11.0
MODULE='pcnet32'
MODULE_OPTIONS=''
STARTMODE='auto'
sles9:~ #

The MODULE line lists the name of the driver to insert.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.