Unable to mount NFS volume during NetBoot…
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi everyone:
I've searched the bombich.com forums and haven't gotten anywhere with my issue. If I missed something in an earlier thread, I apologize, but I searched as best I could (going on 4 days now) before posting. I'm currently trying, for the first time, to do restores of Macs over the network instead of just off of an external hdd using NetRestore.
Following accepted practices on bombich.com and the San Diego State University white paper, I created the NetInstall-Restore set and the asr ready image via NetRestore Helper on a client system. The NetInstall sets are appropriately placed in the NetBootSP0 share and permissions seem good the whole way down the hierarchy. The Share Points also seem to be configured appropriately for NFS on the NetBootSP0 share. Under Protocols… the Export is set up to World (I know this isn’t the most secure practice, I’m just trying to get it operational before I start worrying about security), Mapping is “All to nobody”, and Minimum security is set to Any. I've also changed the config to a client list of 1 system (my test client) and subnet-based mapping.
Server is a 2 GHz ppc G5 and client system is a 2 GHz Intel Core duo.
I fire up NetBoot Across Subnets (my test machines all live on a different subnet from the server farm my xserve lives in) and enter all the information and reboot the system. I get kernel panics almost immediately after it starts to boot off the server. Here is the slice of the info from a verbose boot where the kernel panic occurs:
nfs_boot: get
filehandle(v3) root failed, 2
nfs
bootgetfh(v3, TCP) failed with 2, trying UDP
nfs_boot: get
filehandle(v3) root failed, 2
nfs
bootgetfh(v3, UDP) failed with 2, trying v2
nfs_boot: get
filehandle(v3) root failed, 2
nfs
bootgetfh(v2, TCP) failed with 2, trying UDP
nfs_boot: get
filehandle(v2) root failed, 2
panic(cpu 0 caller 0x002d6a31): “nfs
bootgetfh(v2,UDP) failed with 2: rp=nfs:130.203.xxx.xxx/private/tftpboot/NetBoot/NetBootSP0: name.nbi/NetInstall-Restore.dmg –v”@/SourceCache/xnu/xnu-1228/bsd/nfs/nfs_vfsops.c:895
I can’t mount the NetBootSP0 export via an NFS mount even from the gui. Anytime I try to, I get this error: “Could not connect to the server because the name or password is not correct.” I never get a chance to authenticate, but based on having an NFS export set up to "World" or even trying from a client defined in the Client List when I do a mapping that way, I shouldn't have to, right?
In reading Apple’s file services for Leopard whitepaper, I began to pay attention to the Enable Automount feature under the Share Point tab of the Share Point. It seems enabling some feature under here might allow me to browse the export via gui or in the NetBoot process… but I don’t know that for sure since I can’t find a lot of info in the forums on bombich.com or Google in general about what role this does or does not play in NetBooting. Here’s the kicker, any time I check the box to Enable Automount, the associated properties box is inaccessible to me… the spinning gear (not the color wheel) appears as if it’s doing some lookup somewhere and that never goes away until I hit cancel. From the File Services for Leopard white paper, it seems like I should be able to configure this, so I think something’s going on there w/ my setup somewhere else. I’ve even done complete rebuilds of the server and still get the perpetually spinning gear at this stage.
That’s one of my big questions… are these Automount settings essential to allowing me access to the NFS sharepoints from the GUI and the NetBoot process? If so, any thoughts on why it goes into this “lookup” mode and I never get access to the settings?
Some things I think I’ve ruled out that affect NetBoot (from what I can tell):
- Network problems w/ NFS. I don’t think there’s any trouble here because I can browse NFS exports on other servers w/o issue from OS X. I also took a test system down and plugged it in and tried via the same subnet to same results.
- I’ve tried the NFS Share Point settings in various permutations (export to just subnets, change mappings around, security, etc.) and get the same error every time. I've also confiremed and re-confirmed the POSIX permissions and even added in ACL permissions for everyone. I've tried opening up full permission to all users/all groups to no success. Is there any permission level above read-only necessary for this to work?
- TFTP is confirmed running on the server
- I’ve turned NetBoot on/off multiple times and moved the locations of the NetBoot SharePoints from the the RAID to the system partition and the other hd partition to no luck.
- I've confirmed/reconfirmed that nfsd is running both from cli and gui.
- Built/Rebuilt the server hoping something was just wonky w/ NFS (as it appears can sometimes be the case).
- I’ve tried setting up mount points via Directory Utility on the client system to at least try gain access via the GUI… no success.
- I've tried to set up NFS exports from scratch with just self-created folders and still have no success.
My big questions:
1. The Automount settings… necessary for GUI/NetBoot level access to the NFS exports for Leopard? I can’t seem to get access to them as the system goes into that “lookup” spinning gear status. What might cause that spinning gear on that particular screen?
2. Based on the info above, it really seems like NFS is the culprit to me. If not the Automount, any suggestions?
This was kind of a long one… I appreciate you taking the time to read. Any suggestions would definitely be accepted and appreciated.
11 replies
Sign in or join Beachball Help to reply.
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0