I apologize if this is an RTFM problem, but I've looked enough that I think this is a bug. I'm PXE booting systems with an NFS root filesystem. What I would expect to be able to do is something like: append initrd=f12-x86_64-net/initrd.img root=10.0.0.10:/potatoes/f12-x86_64-net or append initrd=f12-x86_64-net/initrd.img root=/dev/nfs nfsroot=10.0.0.10:/potatoes/f12-x86_64-net For example, the wiki at http://fedoraproject.org/wiki/StatelessLinux/NFSRoot says: "You may override the NFS server name and mount (i.e. what was passed to --rootdev above) by adding root=myserver:/foo/bar to client's pxelinux configuration". When I append "root=10.0.0.10:/potatoes/f12-x86_64-net", I get the error "dracut: FATAL: Don't know how to handle 'root=10.0.0.10:/potatoes/f12-x86_64-net'". When I append "root=/dev/nfs nfsroot=10.0.0.10:/potatoes/f12-x86_64-net", I get the error: "No root device found". In the past (Fedora 10 and 11), I have worked around the problem by adding 'option root-path "10.0.0.10:/potatoes/f12-x86_64-net"' to dhcpd.conf (without appending any root option). However, in Fedora 12, I am now getting the error: "dracut: FATAL: No or empty root= argument".
By the way, the version of dracut is dracut-002-13.4.git8f397a9b.fc12. Also, I'm more confident that I read the manual well, since https://fedoraproject.org/wiki/Dracut/Options#NFS seems to describe exactly what I'm trying. Please let me know if there is any other information I can provide. Thanks.
please check, that you have "dracut-network" installed
Indeed I do not. There is no mention of "dracut-network" in the wiki documentation, and the mkinitrd-based system didn't have any such requirement. I think there definitely need to be explanations at both of the following: https://fedoraproject.org/wiki/Dracut https://fedoraproject.org/wiki/Dracut/Options (in the NFS section) Since this is new for Fedora 12, there should also be an entry about this specific issue in the release notes. I'll try installing dracut-network, rebuilding the initramfs, and see if that works. Thanks.
It looks like installing "dracut-network" indeed makes Dracut pass NFS roots on to the mount command. I guess this bug is really about fixing the documentation. Thanks again for your help.
By the way, is there any way to specify an NFS domain for idmap in the options? I'm not currently able to mount an NFSv4 root because the client doesn't know the NFS domain and can't do mapping. The Dracut options wiki page doesn't list any way to specify the idmap domain, and Wireshark revealed that Dracut isn't doing any DNS requests to determine the NFS domain (Solaris looks up the TXT record for _nfsv4idmapdomain to determine the domain). Without getting the domain right, mounting the root filesystem gives the error: rpc.idmapd: Could not find user "nobody" mount.nfs4: mounting server:/path failed, reason given by server: No such file or directory
(In reply to comment #5) > By the way, is there any way to specify an NFS domain for idmap in the options? > I'm not currently able to mount an NFSv4 root because the client doesn't know > the NFS domain and can't do mapping. The Dracut options wiki page doesn't list > any way to specify the idmap domain, and Wireshark revealed that Dracut isn't > doing any DNS requests to determine the NFS domain (Solaris looks up the TXT > record for _nfsv4idmapdomain to determine the domain). Without getting the > domain right, mounting the root filesystem gives the error: > > rpc.idmapd: Could not find user "nobody" > mount.nfs4: mounting server:/path failed, reason given by server: > No such file or directory oh right.. this is not (yet) implemented
I don't want to clutter this bug report, which I think should just be about the documentation and release notes for "dracut-network".
*** This bug has been marked as a duplicate of bug 537969 ***