Kris Kasner wrote: > Hey Folks.. > > I've been hacking and slashing the install scripts in the miniroot to > try and figure this out.. I can't find anything wrong. I'm hoping that > someone might have a suggestion for me. I've turned on install_debug, > added additional debugging to the scripts, changed get-netmask to point > to something other than a netapp so the interface is configured > correctly, etc.. > > We have a jumpstart environment that I test on vmware-server. If I jump > a system and select the 606 miniroot, everything flies. I get a full > dist install in about 40 minutes. The same install using just the 1106 > miniroot fails to complete because of NFS timeouts - I let it run for > about 24 hours and it still had about 1gb remaining during the solaris > install phase. It would install a little, tell me NFS server xxxx not > responding.. nfs server xxxx OK, install a little more, etc. > > I'm using a NetAPP filer to hold the CD images, and a boot server on the > local network for pxe/tftp and bootparams. I'm pointing to the same > jumpstart install directory with the same root dir in both cases, the > only difference is the miniroot that is tftp'ing across to run the > actual install. I can install the full 11/06 dist using the 6/06 > miniroot without issues.. Once the install is done, the 11/06 system > seems stable and happy. It's just the 11/06 miniroot that gives me NFS > issues. I don't want to use the 6/06 miniroot for all installs because > of hardware support added to 11/06 (the M2 U20's, etc). > > We do not have nfsv4 enabled on the NetAPP, but I've forced all of the > mounts to do vers=3 anyways just to cover the bases.. > > Any suggestions? >
Get some snoop traces and see what the NFS community (nfs-discuss at opensolaris.org) has to say. I'm not aware of any other reports of this problem, though perhaps someone else is. Dave
