Solaris Common Messages and Troubleshooting Guide

`panic -boot: Could not mount filesystem`

The primary problem is that jumpstart gives the following error:

2ec00 RPC: Can't decode result.
whoami RPC call failed with rpc status: 2
panic - boot: Could not mount filesystem.
program terminated
ok

Normally this is a result of the bootparams not being able to get to the install image.

The second problem is that other users have had the same error message, with the additional message:

'Timeout waiting for ARP/RARP packet...'

To solve the first problem:

1. Check how the dfstab(4) (/etc/dfs/dfstab on the install image NFS server) looks:

share -F nfs -o ro,anon=o /jumpstart-dir

2. Run share(1M) command on the installed image NFS server, to make sure it is shared properly.

3. Check /etc/bootparams file on the net install server. Look for entries with incorrect boot path.

4. Make sure that /usr/sbin/rpc.bootparamd is running on the boot server. If necessary, kill and restart it.

5. Check /etc/ethers on the boot server for duplicate or conflicting entries

6. At OK prompt, run test net /test-net and/or watch net /watch-net to test the network connectivity

A workaround for the second problem is to check the nsswitch.conf(4) file. If some of the entries point to NIS such as:

rpc		nis	files
hosts		nis	files
ethers		nis	files
bootparams	files   nis

change all of these entries to files first:

rpc		files 	nis
hosts		files 	nis
ethers		files	nis
bootparams	files	nis

Note - You may have to manually update these files if they do not contain info on the client machine you are trying to jumpstart.

Then remove the client with rm_install_client(1M), remove the contents of tftpboot, and re-add the client:

add_install_client -c /jumpstart-dir/profiles  'client name'  'arch'