Client fails to boot from Jumpstart Server
I am trying to build a jump client using the command boot net -install. After running the command, the client easily find the jumpstart server and identify its ip and host name but then can not boot at all.
It exits with the error panic - boot: Could not mount the filesystem
Here is the sequence of events on the client after the boot command is issued
Ok boot net -v - install
Resetting ...
************** Banner Display **********************
Rebooting with command: boot net -v -install
Boot device:/sbus/SUNW,<a href="mailto:hme@e" target="_blank">hme@e</a>, 8c00000 File and args: -v - install Timeout waiting for ARP/RARP packet Timeout waiting for ARP/RARP packet
10e00 Retrying ... Check TFTP server and network setup
2b000 Retrying ... Check TFTP server and network setup
2b400 Using RARP/BOOTPARAMS ...
Requesting Internet Address for 8:0:20:93:42:d4
Internet address is 10.9.106.48
Hostname: jump-client1
Found 10.9.106.192 @ 0:2:55:ff:39:80
panic - boot: Could not mount the filesystem
Program terminated
ok
I've checked the server side, all necessary filesystem and directories are shared. Any ideas or suggestions ?
Thank you
[1532 byte] By [
parm] at [2007-11-25 22:35:16]
# 1
My guess is the FS' on the JS server is not shared out with UID=0. JS needs this. share -F nfs -o anon=0 .....
# 2
Thanks for replying, The install file system and jumpstart config directory are shared with a uid=0, however it is shared as ro and not as a rw. Should that really make a difference, I doubt.
Here is an output of dfshares or a share command
<a href="mailto:root@wil-apps1" target="_blank">root@wil-apps1</a> # dfshares
RESOURCE SERVER ACCESSTRANSPORT
wil-apps1:/cdrom/sol_9_sparc/s5wil-apps1 - -
wil-apps1:/cdrom/sol_9_sparc/s4wil-apps1 - -
wil-apps1:/cdrom/sol_9_sparc/s3wil-apps1 - -
wil-apps1:/cdrom/sol_9_sparc/s2wil-apps1 - -
wil-apps1:/cdrom/sol_9_sparc wil-apps1 - -
wil-apps1:/export/install wil-apps1 - -
wil-apps1:/Jumpstartwil-apps1 - -
wil-apps1:/cdrom/sol_9_sparc/s0wil-apps1 - -
wil-apps1:/cdrom/sol_9_sparc/s1wil-apps1 - -
<a href="mailto:root@wil-apps1" target="_blank">root@wil-apps1</a> # share
-/cdrom/sol_9_sparc/s5ro""
-/cdrom/sol_9_sparc/s4ro""
-/cdrom/sol_9_sparc/s3ro""
-/cdrom/sol_9_sparc/s2ro""
-/cdrom/sol_9_sparcro""
-/export/installro,anon=0""
-/Jumpstartro,anon=0""
-/cdrom/sol_9_sparc/s0ro,anon=0""
-/cdrom/sol_9_sparc/s1ro,anon=0""
parm at 2007-7-5 13:59:06 >
# 3
All the shares look ok to me. Can you post the contents of /etc/bootparams? Also, see if you can mount all the shares ok from another system.
# 4
The contents of /etc/bootparams are as follows: Looks fine to me.
<a href="mailto:root@wil-apps1" target="_blank">root@wil-apps1</a># more /etc/bootparams
jump-client1 root=wil-apps1:/export/install/Sol8-02/Solaris_8/Tools/Boot install=10.9.106
.192:/export/install/Sol8-02 boottype=:in sysid_config=10.9.106.192:/Jumpstart install_con
fig=10.9.106.192:/Jumpstart rootopts=:rsize=32768
I am able to mount the /export/install filesystem from other system without any question.
parm at 2007-7-5 13:59:06 >
# 5
Have you checked the directories shared for sufficient permissions, etc? - /export/install ro,anon=0 "" - /Jumpstart ro,anon=0 ""
# 6
I also had a doubt that directory permissions could have been a issue. But it didn't turned out to be so far.
The initial permissions on the /export/install directory was 755 when I created the filesystem and mounted it. So when the OS image files were copied to /export/install, the directory permissions were 755.
Then, I had changed permissions on /export/install as well as on /Jumpstart directory recursively to 777. It took a while to do chmod on /export/install due to the size of the directory.
I wonder if it really matters to change the install directory permissions before or after copying the OS software the the install directory.
parm at 2007-7-5 13:59:06 >
# 7
Yeah, I'm still lingering on nfs being the culprit. I just can't visualize on all that you have going there. Below is one of the thread from sunsolve, though not exact, but close enough.
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 filesnis
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'
# 8
Thanks for your research. I tried booting the client by connecting client and server via a crossover cable. That worked just fine. The client easily found the boot and install files and started jumpstart installation. This leads me to conclude that the network router (default gateway) is not able to carry the clients bootparam request to the server. Some services are probably turned off on the network side. Not sure what are they? The most surprising fact was that the initial client-server communciation took place just fine. The client easily resolved its ip address and host name from the server, but then failed to boot.
Anyways, I am sure now that there is nothing wrong with the jumpstart server configuration. Its the network settings that needed to be tuned. Thanks for all your help!!
parm at 2007-7-5 13:59:06 >
# 9
In my case it doesnt cross this. Any clues? Please advice. Thanks!
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Retrying ... Check TFTP server and network setup
Retrying ... Check TFTP server and network setup
Retrying ... Check TFTP server and network setup
Retrying ... Check TFTP server and network setup
Retrying ... Check TFTP server and network setup
Retrying ... Check TFTP server and network setup
Retrying ... Check TFTP server and network setup
Retrying ... Check TFTP server and network setup
Retrying ... Check TFTP server and network setup
kaspe at 2007-7-5 13:59:06 >
# 10
Hi,
are you still having this prblem, is it sol10 running on the jumpstart system
check the build status with snoop, if you are geeting ICMP errors in port 69, check the man page on inetdconv and inetadm.
Cheers
Tom
# 11
We had this issue here after the hostname of the jumpstart server changed but had not been rebooted. Instead of rebooting, we stop/started the rpc.bootparamd daemon and everything was happy.
# 12
All the above instructions are correct but you forgot to issue the command. #shareall The following command is not good enough. #share -F nfs /export/install
