Sun Management Center Change Manager 1.0.1 Administration Guide

- Previous: Managed Host Hangs While Booting From the Network (4656587)
- Next: Appendix C Security (Reference)

## `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

Cause:

  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` command to identify the network boot servers that manage your managed host.

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

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

     Use the browser interface or the command-line interface to remove your managed host from the Sun Management Center topology.

  2. Run the `hostconfig` command to determine whether your managed host is managed by 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 managed by 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 managed by a boot server. Go to Step 7.

     See the hostconfig(1M) man page.

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

     If you use the NIS naming service, for example, use `ypmatch` 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

     See the ypmatch(1) man page.

  5. Remove your managed host entries from the `/etc/bootparams` file on the boot server.

     1. Log in to the boot server as superuser.

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

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

            # ./rm_install_server hostname

  6. Repeat Steps 2-4 to find additional boot servers. Then, perform Step 5 for any boot servers found.

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

- Previous: Managed Host Hangs While Booting From the Network (4656587)
- Next: Appendix C Security (Reference)

- © 2010, Oracle Corporation and/or its affiliates