View previous topic :: View next topic |
Author |
Message |
visionlogic n00b

Joined: 04 Nov 2017 Posts: 8
|
Posted: Sat Nov 04, 2017 10:48 pm Post subject: trouble mounting nfs |
|
|
Hi Everybody,
First off, I'd like to say hello and thank you to the other Gentoo users who help on this forum. I began learning Gentoo about 6 months ago, and have to say: I am thankful for the support already received indirectly by reading posts on here. This is my first post as a forum member, so wanted to start it off with gratitude.
Now, onto my issue. After days of searching, I havn't been able to find anything which leads to a solution. There have been other posts from users who had similar symptons, but realized that they needed to reboot, add nfs support in their kernel, install nfs-utils, etc.
I have done all these things but can't seem to figure it out. Every system file that I know to check seems to indicate the proper settings.
I am unable to mount a drive found on my NAS after adding kernel support for my AMD graphics card. It was working before, and I had the drive automatically mounting at boot by adding an appropriate fstab entry.
Once I updated the kernel, however, it stopped working.
To get to the bottom of the problem, I tried reverting the change. For some reason this didn't help. I actually tried starting from a fresh kernel config with make defconfig. After reconfiguring everything to minimally support what I need (including nfs and the amd card), I recompiled and installed the kernel. Heck, I even rebuilt world for good measure (this is my second gentoo device, and the system does not have much on it yet--in fact, I was configuring the graphics drivers as part of the bringup process)
Still, I am getting the same behavior. I can ssh into the NAS and view the files, but can't mount.
Here is a series of commands and their output to illustrate the problem. The order of connands is indicative of the things I have tried, and steps I have taken towards a solution. Does anybody know what else I can do to investigate/solve this problem?
Code: | $ uname -r
4.11.12-rt-rt14
|
Code: | $ sudo mount <SERVER_IP>:/volume3/file_locker /mnt/file_locker
mount.nfs: Protocol not supported
|
Code: | $ cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev ramfs
nodev bdev
nodev proc
nodev cpuset
nodev cgroup
nodev cgroup2
nodev tmpfs
nodev devtmpfs
nodev binfmt_misc
nodev debugfs
nodev tracefs
nodev securityfs
nodev sockfs
nodev bpf
nodev pipefs
nodev hugetlbfs
nodev devpts
iso9660
nodev pstore
nodev mqueue
nodev selinuxfs
ext2
ext3
ext4
btrfs
reiserfs
jfs
nodev rpc_pipefs
nodev nfs
nodev nfs4
xfs
fuseblk
nodev fuse
nodev fusectl
|
Code: | $ cat /lib/modules/4.11.12-rt-rt14/modules.builtin | grep nfs
kernel/fs/nfs/nfs.ko
kernel/fs/nfs/nfsv2.ko
kernel/fs/nfs/nfsv3.ko
kernel/fs/nfs/nfsv4.ko
kernel/fs/nfs/blocklayout/blocklayoutdriver.ko
kernel/fs/nfs/filelayout/nfs_layout_nfsv41_files.ko
kernel/fs/nfs_common/nfs_acl.ko
kernel/fs/nfs_common/grace.ko
kernel/fs/nfsd/nfsd.ko
|
Code: | $ lsmod | grep nfs
nfs 225280 0
lockd 77824 1 nfs
sunrpc 286720 3 lockd,nfs
fscache 61440 1 nfs
|
Code: | $ grep -i nfs /usr/src/linux/.config
CONFIG_KERNFS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V2=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_SWAP=y
CONFIG_NFS_V4_1=y
CONFIG_NFS_V4_2=y
CONFIG_PNFS_FILE_LAYOUT=y
CONFIG_PNFS_BLOCK=y
CONFIG_PNFS_FLEXFILE_LAYOUT=m
CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="kernel.org"
# CONFIG_NFS_V4_1_MIGRATION is not set
CONFIG_NFS_V4_SECURITY_LABEL=y
CONFIG_ROOT_NFS=y
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_NFSD=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_PNFS=y
CONFIG_NFSD_BLOCKLAYOUT=y
CONFIG_NFSD_SCSILAYOUT=y
CONFIG_NFSD_FLEXFILELAYOUT=y
# CONFIG_NFSD_V4_SECURITY_LABEL is not set
# CONFIG_NFSD_FAULT_INJECTION is not set
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
|
Code: | $ sudo /etc/init.d/nfs restart
* Starting NFS mountd ... [ ok ]
* Starting NFS daemon ...
rpc.nfsd: Unable to access /proc/fs/nfsd errno 2 (No such file or directory).
Please try, as root, 'mount -t nfsd nfsd /proc/fs/nfsd' and then restart rpc.nfsd to correct the problem [ !! ]
* Starting NFS smnotify ... [ ok ]
* ERROR: nfs failed to start
|
Code: | $ sudo mount -t nfsd nfsd /proc/fs/nfsd
mount: unknown filesystem type 'nfsd'
|
Code: | $ ls /proc/fs/
ext4 fscache jbd2 lockd nfsd nfsfs xfs
|
Code: | $ dmesg | grep -i nfs
[ 4.643451] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 4.671958] FS-Cache: Netfs 'nfs' registered for caching
|
Code: | $ sudo showmount -e <SERVER_IP> |
shows same export list that had been working before
Code: | $ equery --quiet list net-fs/nfs-utils
net-fs/nfs-utils-1.3.4-r1 |
[Moderator edit: added [code] tags to preserve output layout. -Hu] |
|
Back to top |
|
 |
visionlogic n00b

Joined: 04 Nov 2017 Posts: 8
|
Posted: Sun Nov 05, 2017 2:13 am Post subject: |
|
|
After a bit more troubleshooting, I stumbled on the problem. Whenever I did the thing that broke nfs, it also broke vfat, which is the type of my boot partition. This meant that while I thought I was installing the newly compiled kernel, I was actually just installing to a directory called /boot within my rootfs. My kernel updates weren't actually taking place, even though everything else about the state of the system looked right.
What I did to fix it:
-chroot into the system after mounting everything properly from a systemrescuecd
-reinstall kernel after verifying that /boot was actually pointing to my boot partition
Hopefully this note can help somebody else solve a similar problem. On another note, the amd graphics drivers are still causing me trouble, but this is an issue for another thread.
Cheers |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|