You are not logged in.
Hi,
I'm have already working a nfs server for some embedded devices, for which I got already the root file system and the img. Now I'm trying to get this embedded systems working with archlinux. The CPU is a normal i686 (in case someone associated embedded with ARM or sth like this). Since the devices are able to boot with the images that I got, it points out that the server is working but the boot images are not.
I have created the Root Directory following this article;
https://wiki.archlinux.org/index.php/Di … t_NFS_root
I didn't have any problem, and just in case the mkinitcpio-nfs-utils is v0.3-3.
For the kernel image I have added the nfs module, and net and udev in the hooks...
Well as I said I have the server working so I guess that this export is ok:
/etc/export
/media/scu 192.168.1.4(rw,no_root_squash,no_subtree_check)/pxelinux.cfg/default
SERIAL 0 115200 0x000
DEFAULT linux
# display boot prompt
PROMPT 1
# 1 second timeout
TIMEOUT 10
DISPLAY help.txt
LABEL linux
MENU LABEL linux ramdisk
KERNEL scu/vmlinuz-linux-archlinux
APPEND initrd=scu/initramfs-linux-archlinux.img root=/dev/nfs nfsroot=192.168.1.1:/media/scu,tcp,v3 ip=dhcpWhen I start one of the NFS clients, it gets correctly the IP from the NFS server, the images vmlinuz and initramfs load correctly, the networking is also working aparently but when the client must mount:
NFS-Mount: 192.168.1.1:/media/scu
Waiting 10 seconds for device /dev/nfs ...
ERROR: device '/dev/nfs' not found. Skipping fsck
rpc failed: 2
::running clean up hook [udev]
ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck!!If I check the kernel modules, nfs is there. And if I try to mount the nfs by hand:
#mount -t nfs 192.168.1.1:/media/scu
mount: wrong fs type, bad option, bad superblock on 192.168.1.1:/media/scu, missing
codepage or helper program...I'm already out of ideas how to fix this, I have set up other nfs with other distros and "no problem" but in this case I think that the problem is the kernel image, not the server.
Thanks in advance,
B.
Offline
Never heard of /dev/nfs - did you take a look at the nfs and nfs4-pages on the wiki? Iirc it is not enough to load the nfs-module. You should also start two daemons: nfs-common and rpcbind in a specific order.
Offline
Check to see if /dev/nfs is in the initramfs image, either through the error message or with lsinitcpio.
Also ip line should be ip=::::::dhcp, but I don't think that you are even getting that far.
The other problem is unless you change the configuration in tftpd to start from /media/xxxx, it is pulling it from under /var/tftpboot, if you have a media that you have mounted just make another directory under tftpboot and call your kernel, initramfs, and root filesystem there instead of under /media.
For example, instead of /media/scu, it would be mounted at /var/tftpboot/scu. *NIX doesn't care where you actually mount the stuff.
Be sure to export it as /var/tftpboot/scu with a * instead of a fixed address, unless it obtains that same address everytime, otherwise you wouldn't be using dhcp, you would be setting a fixed ip with the ip= parameter.
Last edited by nomorewindows (2012-08-23 13:19:40)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
The same problem here.
When i try to mount a directory over nfs on a freshly installed archlinux, then i get the same error message:
mount: wrong fs type, bad option, bad superblock on server:/dir, missing
codepage or helper program...
Since this topic is still open, i wonder, if that is already solved.
regards
Offline
Hello,
ok, i´ve found out.
After trying to install several services, i knew from Linux, e.g. portmap, statd, and so on, which the pacman even could not find, i found a answer in the internet:
install nfs-utils
It seems, that this provides all the services which are needed to do a nfs mount.
(Btw. the docu is somehow missleading, it advises sometimes things which are not explained elsewhere. But in general, i find the documentation of archlinux straightforwarded)
regards
Offline
The missing part about ip=::::::dhcp was the OPs problem, instead of ip=dhcp.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline