Failed to start nfs.service: Unit nfs.service not found
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Failed to start nfs.service: Unit nfs.service not found
So the title is the message I get when I run the command <showmount -e 192.168.0.248>. Doesn't change the error if I use the "sudo" format, either. I'm trying to access my NAS from a Raspberry Pi running Buster. I'd like to access pictures and such from the Pi and view them on my 7 inch touchscreen. Just cant seem to mount the NAS. I tried using the <sudo mount 192.168.0.248:LS-WTG43E/images /mnt/images> at the command prompt and the Pi thinks hard, but then returns a "mount.nfs: Connection timed out" message. Do I just have the syntax wrong? I've worked on this the past three evenings after work, and am getting disheartened. This should work, but I can't seem to get it right.
To digress, I ran <sudo apt-get install nfs-common> and the response was that I had the newest. I ran <sudo apt-get install portmap> and the response was "Note, selecting 'rpcbind' instead of 'portmap'". Its response was again that I had the newest version. This was a precursor to setting this up to work (which it didn't).
Does anyone have suggestions? Have I left out any information? I'm not a newbie, but am far from fluent in Linux. Sure could use some pointers.
Are you the original poster? If so, try to use a consistent name. If not, ask a new question instead of hijacking this one.
Quote:
Originally Posted by noeleo
So the title is the message I get when I run the command <showmount -e 192.168.0.248>.
It surprises me that showmount wants to start the nfs service.
Quote:
sudo mount 192.168.0.248:LS-WTG43E/images /mnt/images
I would expect a leading slash right after the colon.
Quote:
returns a "mount.nfs: Connection timed out" message. Do I just have the syntax wrong?
I am not sure about that slash, but the message indicates that 192.168.0.248 has no NFS server or is not reachable. Are you sure that address is correct?
EDIT: I just notice that the original question is over a month old, and that the original poster uses Ubuntu. You are not the original poster, and you should not use somebody else's question.
Last edited by berndbausch; 07-29-2020 at 10:36 PM.
So the title is the message I get when I run the command <showmount -e 192.168.0.248>. Doesn't change the error if I use the "sudo" format, either. I'm trying to access my NAS from a Raspberry Pi running Buster. I'd like to access pictures and such from the Pi and view them on my 7 inch touchscreen. Just cant seem to mount the NAS. I tried using the <sudo mount 192.168.0.248:LS-WTG43E/images /mnt/images> at the command prompt and the Pi thinks hard, but then returns a "mount.nfs: Connection timed out" message. Do I just have the syntax wrong? I've worked on this the past three evenings after work, and am getting disheartened. This should work, but I can't seem to get it right.
To digress, I ran <sudo apt-get install nfs-common> and the response was that I had the newest. I ran <sudo apt-get install portmap> and the response was "Note, selecting 'rpcbind' instead of 'portmap'". Its response was again that I had the newest version. This was a precursor to setting this up to work (which it didn't).
Does anyone have suggestions? Have I left out any information? I'm not a newbie, but am far from fluent in Linux. Sure could use some pointers.
Thanks in advance for your help.
This text suggests that you use some helper applications to achieve network filesystem functionality. Your knowledge, and thus the information you provide, is patchy.
I suggest manually building your NFS up from zero. It isn't hard.
OK, chastising aside, I thought that since the question was the same, I should ask it there. LESSON LEARNED.
Quote:
Originally Posted by ondoho
This text suggests that you use some helper applications to achieve network filesystem functionality. Your knowledge, and thus the information you provide, is patchy.
OK, so I AM a newbie. I don't know what you mean by helper applications. I was under the assumption that nfs-common was all I needed to make the nfs access.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.