NFS mounts not happening at boot in 18.04 or 18.10 Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)NFS mount fails on Ubuntu 12.04fstab doesn't work since upgrade to 14.10Stuck booting a Ubuntu 14.04 system (not from a LiveCD but from sdb1) via PXE/NFSHow can I mount an NFS drive via fstabMounting network drive fstabHow to mount a NFS share in Ubuntu 16.04?Firewall problem using autofs with NFS-exported mounts16.04 nfs mount problems at boot timeUbuntu 18.04 - Mount NFS with FQDN not resolving addressExportfs Error: exportfs: /export/test does not support NFS export
Apollo command module space walk?
How does debian/ubuntu knows a package has a updated version
Is it true that "carbohydrates are of no use for the basal metabolic need"?
How to align text above triangle figure
Why light coming from distant stars is not discrete?
What's the purpose of writing one's academic biography in the third person?
How does the particle を relate to the verb 行く in the structure「A を + B に行く」?
What does the "x" in "x86" represent?
How do I stop a creek from eroding my steep embankment?
Why was the term "discrete" used in discrete logarithm?
Output the ŋarâþ crîþ alphabet song without using (m)any letters
When were vectors invented?
What is the logic behind the Maharil's explanation of why we don't say שעשה ניסים on Pesach?
2001: A Space Odyssey's use of the song "Daisy Bell" (Bicycle Built for Two); life imitates art or vice-versa?
Why is "Consequences inflicted." not a sentence?
First console to have temporary backward compatibility
What is Arya's weapon design?
Dating a Former Employee
Generate an RGB colour grid
Extract all GPU name, model and GPU ram
What exactly is a "Meth" in Altered Carbon?
What causes the vertical darker bands in my photo?
Why do people hide their license plates in the EU?
Why am I getting the error "non-boolean type specified in a context where a condition is expected" for this request?
NFS mounts not happening at boot in 18.04 or 18.10
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)NFS mount fails on Ubuntu 12.04fstab doesn't work since upgrade to 14.10Stuck booting a Ubuntu 14.04 system (not from a LiveCD but from sdb1) via PXE/NFSHow can I mount an NFS drive via fstabMounting network drive fstabHow to mount a NFS share in Ubuntu 16.04?Firewall problem using autofs with NFS-exported mounts16.04 nfs mount problems at boot timeUbuntu 18.04 - Mount NFS with FQDN not resolving addressExportfs Error: exportfs: /export/test does not support NFS export
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I'm trying to set up a couple of NFS mounts to automatically mount at boot. I'm not new to this; I did this on Solaris in 1985.
Here's what I have in /etc/fstab:
iomega:/nfs/Music /music nfs rw,auto,user 0 0
It doesn't mount at boot and leaves this message in syslog:
Mount process exited, code=exited status=32
It didn't work in 18.04, and I just upgraded today to 18.10 and it still doesn't work. If I do a mount -a after boot, that fs mounts normally.
I've tried several suggestions about adding systemd-specific parameters to the mount options, but none of them worked.
This is basic functionality. It should JFW. Can anybody tell me what the exit code 32 means and how to make this work?
boot mount fstab nfs
asked Oct 22 '18 at 19:55
Mike JonesMike Jones
62
add a comment |
I'm trying to set up a couple of NFS mounts to automatically mount at boot. I'm not new to this; I did this on Solaris in 1985.
Here's what I have in /etc/fstab:
iomega:/nfs/Music /music nfs rw,auto,user 0 0
It doesn't mount at boot and leaves this message in syslog:
Mount process exited, code=exited status=32
It didn't work in 18.04, and I just upgraded today to 18.10 and it still doesn't work. If I do a mount -a after boot, that fs mounts normally.
I've tried several suggestions about adding systemd-specific parameters to the mount options, but none of them worked.
This is basic functionality. It should JFW. Can anybody tell me what the exit code 32 means and how to make this work?
boot mount fstab nfs
asked Oct 22 '18 at 19:55
Mike JonesMike Jones
62
perror 32tells meOS error code 32: Broken pipe
– waltinator
Oct 22 '18 at 23:49
add a comment |
I'm trying to set up a couple of NFS mounts to automatically mount at boot. I'm not new to this; I did this on Solaris in 1985.
Here's what I have in /etc/fstab:
iomega:/nfs/Music /music nfs rw,auto,user 0 0
It doesn't mount at boot and leaves this message in syslog:
Mount process exited, code=exited status=32
It didn't work in 18.04, and I just upgraded today to 18.10 and it still doesn't work. If I do a mount -a after boot, that fs mounts normally.
I've tried several suggestions about adding systemd-specific parameters to the mount options, but none of them worked.
This is basic functionality. It should JFW. Can anybody tell me what the exit code 32 means and how to make this work?
boot mount fstab nfs
asked Oct 22 '18 at 19:55
Mike JonesMike Jones
62
I'm trying to set up a couple of NFS mounts to automatically mount at boot. I'm not new to this; I did this on Solaris in 1985.
Here's what I have in /etc/fstab:
iomega:/nfs/Music /music nfs rw,auto,user 0 0
It doesn't mount at boot and leaves this message in syslog:
Mount process exited, code=exited status=32
It didn't work in 18.04, and I just upgraded today to 18.10 and it still doesn't work. If I do a mount -a after boot, that fs mounts normally.
I've tried several suggestions about adding systemd-specific parameters to the mount options, but none of them worked.
This is basic functionality. It should JFW. Can anybody tell me what the exit code 32 means and how to make this work?
boot mount fstab nfs
boot mount fstab nfs
asked Oct 22 '18 at 19:55
Mike JonesMike Jones
62
asked Oct 22 '18 at 19:55
Mike JonesMike Jones
62
asked Oct 22 '18 at 19:55
Mike JonesMike Jones
62
asked Oct 22 '18 at 19:55
Mike JonesMike Jones
62
asked Oct 22 '18 at 19:55
Mike JonesMike Jones
62
62
perror 32tells meOS error code 32: Broken pipe
– waltinator
Oct 22 '18 at 23:49
add a comment |
perror 32tells meOS error code 32: Broken pipe
– waltinator
Oct 22 '18 at 23:49
perror 32 tells me OS error code 32: Broken pipe– waltinator
Oct 22 '18 at 23:49
perror 32 tells me OS error code 32: Broken pipe– waltinator
Oct 22 '18 at 23:49
add a comment |
2 Answers
2
active
oldest
votes
Try changing the options in your /etc/fstab on that line to read like the following:
iomega:/nfs/Music /music nfs defaults,nofail 0 0
I use NFS at home as well, and these options have never failed me.
I am not sure what the code 32 means, but this one backs up my answer:
https://ubuntuforums.org/showthread.php?t=2389242
Hope this helps!
answered Oct 22 '18 at 19:59
TerranceTerrance
20.5k34999
Tried it, didn't work. Digging a little deeper into syslog, it looks like the network isn't available when it tries to do the mount. This is on my laptop using wifi. I suspect (but haven't tried yet) that it would work if I was on a wired connection but it's not smart enough to wait for the wifi to start up. Looks like a post-boot workaround is in order.
– Mike Jones
Oct 25 '18 at 14:49
@MikeJones I guess you could try changing theiomegato the actual IP address of it. Or add a line to your/etc/hostsfor the IP then name of iomega. There could be a chance that DNS isn't quite caught up during boot yet. Thenofailoption that is added is because if the device is not available during boot the system will continue to boot regardless.
– Terrance
Oct 25 '18 at 15:21
add a comment |
Try autofs. You can give it a try like what I did.
- Install NFS Client
apt -y install nfs-common
- Configure auto-mounting
apt -y install autofs
- Edit
auto.masterfile
vi /etc/auto.master
Add /- /etc/auto.nfs at the bottom.
(You can give a different name rather than auto.nfs.)
- Write auto.nfs
vi /etc/auto.nfs
Write as /nfs/share -fstype=nfs4,rw server:remote-point.
In case your server uses nfs4.0 you would better to add an option like this./nfs/share -fstype=nfs4,rw -vers=4.0 server:remote-point
- Create a directory and run
mkdir /nfs/share
systemctl restart autofs
- Check if it works
ls /nfs/share
ref: Configure NFS Client
answered 33 mins ago
David JungDavid Jung
11
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1086217%2fnfs-mounts-not-happening-at-boot-in-18-04-or-18-10%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try changing the options in your /etc/fstab on that line to read like the following:
iomega:/nfs/Music /music nfs defaults,nofail 0 0
I use NFS at home as well, and these options have never failed me.
I am not sure what the code 32 means, but this one backs up my answer:
https://ubuntuforums.org/showthread.php?t=2389242
Hope this helps!
answered Oct 22 '18 at 19:59
TerranceTerrance
20.5k34999
Tried it, didn't work. Digging a little deeper into syslog, it looks like the network isn't available when it tries to do the mount. This is on my laptop using wifi. I suspect (but haven't tried yet) that it would work if I was on a wired connection but it's not smart enough to wait for the wifi to start up. Looks like a post-boot workaround is in order.
– Mike Jones
Oct 25 '18 at 14:49
@MikeJones I guess you could try changing theiomegato the actual IP address of it. Or add a line to your/etc/hostsfor the IP then name of iomega. There could be a chance that DNS isn't quite caught up during boot yet. Thenofailoption that is added is because if the device is not available during boot the system will continue to boot regardless.
– Terrance
Oct 25 '18 at 15:21
add a comment |
Try changing the options in your /etc/fstab on that line to read like the following:
iomega:/nfs/Music /music nfs defaults,nofail 0 0
I use NFS at home as well, and these options have never failed me.
I am not sure what the code 32 means, but this one backs up my answer:
https://ubuntuforums.org/showthread.php?t=2389242
Hope this helps!
answered Oct 22 '18 at 19:59
TerranceTerrance
20.5k34999
Tried it, didn't work. Digging a little deeper into syslog, it looks like the network isn't available when it tries to do the mount. This is on my laptop using wifi. I suspect (but haven't tried yet) that it would work if I was on a wired connection but it's not smart enough to wait for the wifi to start up. Looks like a post-boot workaround is in order.
– Mike Jones
Oct 25 '18 at 14:49
@MikeJones I guess you could try changing theiomegato the actual IP address of it. Or add a line to your/etc/hostsfor the IP then name of iomega. There could be a chance that DNS isn't quite caught up during boot yet. Thenofailoption that is added is because if the device is not available during boot the system will continue to boot regardless.
– Terrance
Oct 25 '18 at 15:21
add a comment |
Try changing the options in your /etc/fstab on that line to read like the following:
iomega:/nfs/Music /music nfs defaults,nofail 0 0
I use NFS at home as well, and these options have never failed me.
I am not sure what the code 32 means, but this one backs up my answer:
https://ubuntuforums.org/showthread.php?t=2389242
Hope this helps!
answered Oct 22 '18 at 19:59
TerranceTerrance
20.5k34999
Try changing the options in your /etc/fstab on that line to read like the following:
iomega:/nfs/Music /music nfs defaults,nofail 0 0
I use NFS at home as well, and these options have never failed me.
I am not sure what the code 32 means, but this one backs up my answer:
https://ubuntuforums.org/showthread.php?t=2389242
Hope this helps!
answered Oct 22 '18 at 19:59
TerranceTerrance
20.5k34999
edited Oct 22 '18 at 20:12
answered Oct 22 '18 at 19:59
TerranceTerrance
20.5k34999
answered Oct 22 '18 at 19:59
TerranceTerrance
20.5k34999
answered Oct 22 '18 at 19:59
TerranceTerrance
20.5k34999
20.5k34999
Tried it, didn't work. Digging a little deeper into syslog, it looks like the network isn't available when it tries to do the mount. This is on my laptop using wifi. I suspect (but haven't tried yet) that it would work if I was on a wired connection but it's not smart enough to wait for the wifi to start up. Looks like a post-boot workaround is in order.
– Mike Jones
Oct 25 '18 at 14:49
@MikeJones I guess you could try changing theiomegato the actual IP address of it. Or add a line to your/etc/hostsfor the IP then name of iomega. There could be a chance that DNS isn't quite caught up during boot yet. Thenofailoption that is added is because if the device is not available during boot the system will continue to boot regardless.
– Terrance
Oct 25 '18 at 15:21
add a comment |
Tried it, didn't work. Digging a little deeper into syslog, it looks like the network isn't available when it tries to do the mount. This is on my laptop using wifi. I suspect (but haven't tried yet) that it would work if I was on a wired connection but it's not smart enough to wait for the wifi to start up. Looks like a post-boot workaround is in order.
– Mike Jones
Oct 25 '18 at 14:49
@MikeJones I guess you could try changing theiomegato the actual IP address of it. Or add a line to your/etc/hostsfor the IP then name of iomega. There could be a chance that DNS isn't quite caught up during boot yet. Thenofailoption that is added is because if the device is not available during boot the system will continue to boot regardless.
– Terrance
Oct 25 '18 at 15:21
Tried it, didn't work. Digging a little deeper into syslog, it looks like the network isn't available when it tries to do the mount. This is on my laptop using wifi. I suspect (but haven't tried yet) that it would work if I was on a wired connection but it's not smart enough to wait for the wifi to start up. Looks like a post-boot workaround is in order.
– Mike Jones
Oct 25 '18 at 14:49
Tried it, didn't work. Digging a little deeper into syslog, it looks like the network isn't available when it tries to do the mount. This is on my laptop using wifi. I suspect (but haven't tried yet) that it would work if I was on a wired connection but it's not smart enough to wait for the wifi to start up. Looks like a post-boot workaround is in order.
– Mike Jones
Oct 25 '18 at 14:49
@MikeJones I guess you could try changing the
iomega to the actual IP address of it. Or add a line to your /etc/hosts for the IP then name of iomega. There could be a chance that DNS isn't quite caught up during boot yet. The nofail option that is added is because if the device is not available during boot the system will continue to boot regardless.– Terrance
Oct 25 '18 at 15:21
@MikeJones I guess you could try changing the
iomega to the actual IP address of it. Or add a line to your /etc/hosts for the IP then name of iomega. There could be a chance that DNS isn't quite caught up during boot yet. The nofail option that is added is because if the device is not available during boot the system will continue to boot regardless.– Terrance
Oct 25 '18 at 15:21
add a comment |
Try autofs. You can give it a try like what I did.
- Install NFS Client
apt -y install nfs-common
- Configure auto-mounting
apt -y install autofs
- Edit
auto.masterfile
vi /etc/auto.master
Add /- /etc/auto.nfs at the bottom.
(You can give a different name rather than auto.nfs.)
- Write auto.nfs
vi /etc/auto.nfs
Write as /nfs/share -fstype=nfs4,rw server:remote-point.
In case your server uses nfs4.0 you would better to add an option like this./nfs/share -fstype=nfs4,rw -vers=4.0 server:remote-point
- Create a directory and run
mkdir /nfs/share
systemctl restart autofs
- Check if it works
ls /nfs/share
ref: Configure NFS Client
answered 33 mins ago
David JungDavid Jung
11
add a comment |
Try autofs. You can give it a try like what I did.
- Install NFS Client
apt -y install nfs-common
- Configure auto-mounting
apt -y install autofs
- Edit
auto.masterfile
vi /etc/auto.master
Add /- /etc/auto.nfs at the bottom.
(You can give a different name rather than auto.nfs.)
- Write auto.nfs
vi /etc/auto.nfs
Write as /nfs/share -fstype=nfs4,rw server:remote-point.
In case your server uses nfs4.0 you would better to add an option like this./nfs/share -fstype=nfs4,rw -vers=4.0 server:remote-point
- Create a directory and run
mkdir /nfs/share
systemctl restart autofs
- Check if it works
ls /nfs/share
ref: Configure NFS Client
answered 33 mins ago
David JungDavid Jung
11
add a comment |
Try autofs. You can give it a try like what I did.
- Install NFS Client
apt -y install nfs-common
- Configure auto-mounting
apt -y install autofs
- Edit
auto.masterfile
vi /etc/auto.master
Add /- /etc/auto.nfs at the bottom.
(You can give a different name rather than auto.nfs.)
- Write auto.nfs
vi /etc/auto.nfs
Write as /nfs/share -fstype=nfs4,rw server:remote-point.
In case your server uses nfs4.0 you would better to add an option like this./nfs/share -fstype=nfs4,rw -vers=4.0 server:remote-point
- Create a directory and run
mkdir /nfs/share
systemctl restart autofs
- Check if it works
ls /nfs/share
ref: Configure NFS Client
answered 33 mins ago
David JungDavid Jung
11
Try autofs. You can give it a try like what I did.
- Install NFS Client
apt -y install nfs-common
- Configure auto-mounting
apt -y install autofs
- Edit
auto.masterfile
vi /etc/auto.master
Add /- /etc/auto.nfs at the bottom.
(You can give a different name rather than auto.nfs.)
- Write auto.nfs
vi /etc/auto.nfs
Write as /nfs/share -fstype=nfs4,rw server:remote-point.
In case your server uses nfs4.0 you would better to add an option like this./nfs/share -fstype=nfs4,rw -vers=4.0 server:remote-point
- Create a directory and run
mkdir /nfs/share
systemctl restart autofs
- Check if it works
ls /nfs/share
ref: Configure NFS Client
answered 33 mins ago
David JungDavid Jung
11
answered 33 mins ago
David JungDavid Jung
11
answered 33 mins ago
David JungDavid Jung
11
answered 33 mins ago
David JungDavid Jung
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1086217%2fnfs-mounts-not-happening-at-boot-in-18-04-or-18-10%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
perror 32tells meOS error code 32: Broken pipe– waltinator
Oct 22 '18 at 23:49