This is too funny because we were experiencing the same problem. It appears to be a NetApp bug. When we set the bootparams to do rootopts=:vers=2 the jumpstart works.
Yep, including that in DHCP vendor option 1 (equivalent to bootparam rootopts) did the magic trick. Makes sense where it dies too, as it is immediately after the kernel takes over responsibility for the NFS mount (doing v3) from the bootstrap (doing v2).
I have an open case with NetApp and they say that this is fixed in 6.1.3.
Good deal.
Try that vers=2 for NFS Version 2 and see if it works for you. We are doing exactly what you are doing off a mirrored volume. The base volume in TX works great but the mirror we have in CA hangs.
I was doing some cross-country jumpstarts (nfs root filesystems 3000mi away suck) today before I sent that mail and got your response -- needless to say it was a big help, thanks.
..kg..