LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Failed to start nfs.service: Unit nfs.service not found (https://www.linuxquestions.org/questions/linux-newbie-8/failed-to-start-nfs-service-unit-nfs-service-not-found-4175679633/)

noeleo 07-29-2020 09:22 PM

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.

Thanks in advance for your help.

berndbausch 07-29-2020 10:34 PM

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 (Post 6150820)
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.

rtmistler 07-30-2020 05:13 AM

New thread created.

@noeleo,

Please do not hijack other person's threads.

ondoho 07-30-2020 07:02 AM

Quote:

Originally Posted by noeleo (Post 6150820)
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.

noeleo 07-30-2020 01:48 PM

OK, chastising aside, I thought that since the question was the same, I should ask it there. LESSON LEARNED.

Quote:

Originally Posted by ondoho (Post 6150926)
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.

[QUTOE]It isn't hard.[/QUOTE]

I'll check out your link and see what I can learn from there.

Thanks, and Ill post back when I get it fixed.


All times are GMT -5. The time now is 07:41 PM.