Red Hat Bugzilla – Bug 855170
Dracut needs to include nfs3, nfs4 modules
Last modified: 2013-01-09 22:36:26 EST
In 3.6 kernel all the different NFS protocols were broken up into separate kernel modules, so dracut will need to include the specific nfs2, nfs3, nfs4, and plain nfs modules in order for NFS mounting from dracut to work.
This has direct effect on Anaconda installs where stage2 comes from NFS.
*** Bug 854180 has been marked as a duplicate of this bug. ***
Created attachment 610624 [details]
console output of F18-TC6 showing broken NFS
Attached find a console output of Fedora 18 TC6. It shows, that dracut and mount are unable to mount NFS from a working NFS server.
dracut:/# ping -c 1 10.2.1.1
PING 10.2.1.1 (10.2.1.1) 56(84) bytes of data.
64 bytes from 10.2.1.1: icmp_req=1 ttl=64 time=0.339 ms
--- 10.2.1.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.339/0.339/0.339/0.000 ms
dracut:/# cat /proc/cmdline
initrd=fedora/18/x86_64/initrd.img inst.repo=nfsiso:10.2.1.1:/home/tmp/fedora/18/x86_64/iso/ selinux=0 BOOT_IMAGE=fedora/18/x86_64/vmlinuz
dracut:/# mkdir /tmp/aa
dracut:/# mount -t nfs 10.2.1.1:/home/tmp/fedora/18/x86_64/iso /tmp/aa
mount.nfs: Protocol not supported
Proposing as Beta blocker:
" It must be possible to install by booting the installation kernel directly, including via PXE, and correctly specifying a remote source for the installer itself, using whichever protocols are required to work for package retrieval at the current phase (Alpha, Beta, Final). This must work if the remote source is not a complete repository but contains only the files necessary for the installer itself to run. "
Jesse, please transfer the Blocks: field if you mark some bug as a duplicate, thanks. Doing it now.
(In reply to comment #3)
> Proposing as Beta blocker:
> " It must be possible to install by booting the installation kernel
> directly, including via PXE, and correctly specifying a remote source for
> the installer itself, using whichever protocols are required to work for
> package retrieval at the current phase (Alpha, Beta, Final). This must work
> if the remote source is not a complete repository but contains only the
> files necessary for the installer itself to run. "
Nit picky, but that criteria is not broken by this bug. During the install you can still select an NFS source and have it mounted at that point. This bug just prevents use of NFS as a stage2 source, which is independent of package install location.
I discovered that currently there is no release criteria for stage2 locations. I already proposed this as a beta blocker (by blocking the F18Beta bug) on the premise that even though there is no criteria we can make a judgement call and decide that this is a blocker anyway.
(In reply to comment #5)
That criterion was created to specifically cover stage2 download. "remote source for the installer itself" means remote location of the stage2 image.
There is a different criterion for remote location of the package repository.
dracut-023-39.git20120910.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dracut-023-39.git20120910.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
May be fixed in dracut-023-39.git20120910.fc18. But Fedora 18 Alpha RC2 still does not work with inst.repo=nfs.. (probably this new dracut was not used to build the included initramfs of RC2?).
(In reply to comment #9)
This does not qualify for Alpha criteria, it's not proposed for Alpha -> will not be in Alpha.
It's true it would be nice to have this in Alpha, but the change might be considered risky. If somebody thinks it's worth it, add F18Alpha-accepted into Blocks field and we will discuss it.
dracut-023-39.git20120910.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.