test

Sun Management Center Change Manager 1.0 Administration Guide

Panic: unable to mount file systems Message Appears While Booting From the Network

Description:

The network boot of your managed host might fail with an error message such as:


Panic: unable to mount file systems

If such a message appears, then your managed host is probably being served by more than one network boot server.

You must first identify all network boot servers on which your managed host is registered, other than the Change Manager server.

Solution:

Use the hostconfig(1M) command to identify the network boot servers on which your managed host is a client.

Perform the following steps to determine whether your managed host is a client of more than one network boot server:

  1. Remove your managed host from the Change Manager server from which you want to boot.

    1. Use the browser interface or the command-line interface to remove your managed host from the Change Manager topology.

    2. Log in to the boot server as superuser.

    3. Change to the Tools directory of the Solaris boot image associated with the Solaris version you want to install.

    4. Run the rm_install_client command to remove the entries for your managed host from the /etc/bootparams file.


      # ./rm_install_server hostname

  2. Run the hostconfig command to determine whether your managed host is a client of another network boot server.


    $ hostconfig -p bootparams -f hostname -n -v

  3. See if the hostconfig command identifies a network boot server for your managed host.

    • If an IP address appears in square brackets on the first line of output, your managed host is a client of another boot server. The IP address represents the boot server.


      From [192.153.72.132]: hostname = host1
	ypdomain = yourCompany.COM
	router = 192.153.72.1

    • If no IP address appears, then your managed host is not a client of a boot server. Go to Step 7.

  4. Determine the name of the boot server specified by the IP address.

    If you use the NIS naming service, for example, use ypmatch(1) to associate the IP address with the host name of the boot server.


    $ ypmatch 192.153.72.132 hosts.byaddr
129.153.72.132  cmserver

  5. Repeat Step 1b to Step 4 to remove your managed host entries from the /etc/bootparams file on the boot server.

  6. Repeat Steps 2-4 to find additional boot servers.

  7. When no more boot servers are indicated by the hostconfig command, add your managed host to the Change Manager topology of the Change Manager server. Set up the files for installation. Then, restart the boot net - install from your managed host's console.