Benches macOS

11

Unable to mount NFS volume during NetBoot…

apple Verified

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.

  1. 0

    Brian Nesse

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm almost certain that those errors are indicative of NFS not being configured/enabled correctly.

    Did you configure and start the NFS service manually? Or did you just get it when you started the NetBoot service? Sometimes it doesn't configure correctly if you don't do it manually.

    Maybe ports 67 & 68 are being blocked by a firewall... I think others have had this problem (may go back to the configuration thing above).

    The fact that you can't mount the share from the GUI is a huge red flag.

    What do you get if you to a 'showmount -e' in the terminal on the server? You ought to see the NetBoot share point(s).

  2. 0

    atm135

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Brian:

    Thanks for taking the time to follow-up. After posting on the board, I began re-evaluating my setup (again) from bottom to top. I rebuilt the box again and re-partitioned, rebuilt the box up, and hit the same problems. I began re-evaluating how I thought I was supposed to be mounting NFS shares and found that I'd simply been trying to mount shares incorrectly (my NFS knowledge comes from NAS , this is my first attempt trying to implement it in this fashion, and the filesystems apparently mount differently). I had been trying to mount nfs://ip/share point and found that when I did nfs://ip/full/path/sharepoint, I was able to mount NFS shares via the GUI.

    I'm able to mount NFS via the GUI. I try to do a NetBoot with these settings:

    IP address: ip

    NetBoot Sharepoint name: NetBootSP0

    Image set name: ImageStorage.nbi

    NetBoot image name: NetInstall-Restore.dmg

    I get the same kernel panic in the same spot.

    NetBoot is configured to host images on the system drive. Permissions on NetBootSP0 directory are:

    drwxr-xr-x 1 admin admin ImageStorage.nbi

    drwxr-xr-x 5 admin admin Resources

    I've confirmed via CLI that nfsd is running and I can appropriately mount this directory via NFS from the GUI. I'm still getting that same kernel panic, though.

    I'm running 10.5.2 (full patch rev except for the Leopard Graphics Update, I've read horror stories about it but I'm not opposed to putting it on) on a PPC 2 GHz Xserve RackMac3.1.

    The clients are Intel 2 GHz Intel Core duos.

    TFTP is confirmed running and the plist seems to be appropriately configured (I saw no changes I needed to make to it).

    I'd appreciate any thoughts anyone has... Thanks again, Brian, for taking the time to respond... I appreciate it.

    Adam @ Penn State

  3. 0

    Brian Nesse

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    For comparison purposes... On my system for NetBootSP0:

    - Automount is disabled

    - AFP is enabled (so I can copy images to it)

    - NFS is enabled (Export:World, Mapping:Root to Root, Security:Standard, Read only)

    You say you are NetBooting... are you trying do to "Diskless" NetBoot? If so, you need to have AFP configured and setup properly on NetBootClients0 as well.

  4. 0

    wstrucke

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I am having this same problem with the netboot image I created with 10.5.3 on a brand new 20" iMac running 10.5.3.

    The errors I am seeing in verbose boot are:

    nfs_boot: get
    filehandle(v3) root failed, 13

    nfs
    bootgetfh(v3,TCP) failed with 13, trying UDP...

    nfs_boot: get
    filehandle(v3) root failed, 13

    nfs
    bootgetfh(v3,UDP) failed with 13, trying v2...

    nfs_boot: get
    filehandle(v2) root failed, 13

    nfs
    bootgetfh(v2,TCP) failed with 13, trying UDP...

    nfs_boot: get
    filehandle(v2) root failed, 13

    panic(cpu 0 caller 0x002D9208): "nfs
    bootgetfh(v2,UDP) failed: NFS server refused mount - check server configuration: -v"@/SourceCache/xnu/xnu-1228.5.18/bsd/nfs/nfs_vfsops.c:893

    Debugger called: <panic>

    etc...

    reproducable on several imacs -- I have not changed my network or netboot config, the netboot image worked fine when I created it (using bombich's netrestore helper) from 10.4.11 -- only that would not netboot the new iMacs.

  5. 0

    Reem Ali

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi All,

    I am having the same issue, what I have tried is to create an HTTP Netrestore image and use HTTP for netboot and it seems to work for me. I'll have to go back now and figure out the deal with the NFS.

    I hope this helps.

  6. 0

    Stu T

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm having the same issues here... any solution found to over come this?

    I get just the following:

    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:

    followed by a ... Debugger called: <panic> ... code of 7 more lines

  7. 0

    WBG4

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Grrr I am having the same issue too. I have tried it on 2 different boxes, same issue. I guess i'll keep messing with it.

  8. 0

    WBG4

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    OK i fixed it on my box. Here's what i did (YMMV):

    I went in and I set it so that netbooting was done from my main library folder (not one that is created on another volume by enabling netboot there, this may not have been the fix, i did several things at once and I honestly kinda doubt that this fixed it).

    The thing that seemed to make a difference (I just went back through and started turning things off 1 at a time till it broke again) was I made the netboot folder a share point, then under protocol options (this part is important) under nfs, set "Allow Subdirectory Mounting" I also Turned on export this item and its contents to world.

    Here is a link to my nfs settings that seem to work
    http://homepage.mac.com/amerchant/fixnetboot.png

    I will now check to see if read only will make a difference or not

    I hope this solves it for some of you

  9. 0

    WBG4

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ok if you set things to be read only everything seems to still be happy

  10. 0

    arekdreyer

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I ran into this problem after changing the disk that contains the NetBoot images. I fixed my issues with the following steps: 1) Remove the share for existing NetBootClients0 and NetBootSP0. 2) Server Admin -> Netboot -> Settings -> General -> Select where to put images and client data: Unselect all checkboxes, then click Save. 3) Select the checkbox for the appropriate drives and click Save. 4) Start the Netboot service.

  11. 0

    matuzalem

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thank you, This fixed my issue too.

    The problem was that I had erased and installed Leopard server over a Tiger install, the netboot shares where pointing to the backup HD (SuperDuper clone), which sill has Tiger in it. I removed the shares as you suggested and recreated the netboot settings.

    Thanks again.