** Changed in: sysvinit (Debian)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/275451
Title:
nfs mounts specified in fstab is not mounted on boot.
To manage
** No longer affects: null
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/275451
Title:
nfs mounts specified in fstab is not mounted on boot.
To manage notifications about this bug go to:
This bug report was originally filed in 2008. The entire handling of
boot-time mounting in Ubuntu has changed radically since then, so the
original issue that was being reported is almost certainly no longer
present. I'm therefore closing this report.
I see in the bug log that some users are
I as well have been plagued by this problem (NFS mounts failing on
bootup) ever since upstart was introduced to Ubuntu.
Not sure why it's so hard to have the network up before things like
mount are called, but apparently it is with Ubuntu.
I have a fixed IP address in /etc/network/interfaces,
Thanks MxxCon - your suggestion would have been much simpler.
Unfortunately it did not work for us.
We are not experiencing this problem so often on servers, only on
clients (about 9 out of 12 client boxes).
On servers we use static IP:s on clients we use DHCP.
Changing a client to a static IP
A FIX for the problem
=
We have also noticed that for some hosts, more often with multiple cpu
cores in our experience, NFS shares are not mounted in time during
upstart.
We have tried NFS v3 and v4 with Ubuntu 8.04 servers and Ubuntu 10.04
clients.
If /home is an NFS share this
Sorry I missed the script /sbin/ensure-nfsshares-mounted
in my last post.
Regards
** Attachment added: ensure-nfsshares-mounted
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/275451/+attachment/2041642/+files/ensure-nfsshares-mounted
--
You received this bug notification because
I also experience this problem with 10.04.2
I seem to solve it much simpler than creating custom startup scripts..
I simply added nfs to /etc/modules and now my servers don't get stuck on
mounting nfs shares.
Seems like something happened in kernel/modules config that it no longer
auto-loads nfs
The workaround from dev001 was all that worked on my Ubuntu 10.04.2 LTS
running on a ZOTAC MAG ND01. Even turning _netdev on did not help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/275451
Title:
i just installed a Ubuntu 10 LTS instance in a Xen VM Guest.
i'm still seeing the same issue as reported here ... nfs4 mounts in
/etc/fstab quietly hand the boot process, with no error messages.
manual mounts are fine.
if i change in /etc/fstab
- nfs-server:/vm/test/ /mnt/test nfs4
System: 10.04 KVM Guest
Guest: Linux 2.6.32-26-server #48-Ubuntu SMP Wed Nov 24 10:28:32 UTC 2010
x86_64 GNU/Linux
Host: Linux 2.6.32-24-server #43-Ubuntu SMP Thu Sep 16 16:05:42 UTC 2010 x86_64
GNU/Linux
I get the following errors, perhaps every 1 in 5 boots from cold:
mount.nfs: DNS
We have the same problem here - all home dirs are nfs-shares which now
don't mount on boot so one cannot login.
In the beginning (after our upgrade) some shares at least mounted, but
the last few days none mount.
Server is still running NFS v3 under Hardy, clients are newly upgraded
to Lucid.
Can confirm this bug for 10.04 server.
nfs isn't connected in 1/10 cases in the boot proces.
The rest of the times it connects within the boot proces.
But in either case the next error shows during boot:
mount.nfs: DNS resolution failed for 192.168.1.11: name or service unknown
The client is a
On a lucid machine with several NFS and NFS4 mounts specified in
/etc/fstab, no share is mounted. /var/log/boot.log does not contain any
traces of an attempt at mounting a share.
$ sudo mount -a mounts all shares, but throws errors for each filesystem
like 'mount.nfs: /backup is busy or already
** Bug watch added: Debian Bug tracker #540291
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540291
** Also affects: sysvinit (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540291
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #551821
** Changed in: sysvinit (Debian)
Status: Unknown = New
** Changed in: nfs-utils (Debian)
Status: Unknown = Incomplete
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of
And _netdev does help :-)
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Tags added: nfs
** Tags added: lucid mount networking
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
OK... NFS mounts via fstab on boot fine in Ubuntu 10.04 BUT (obviously)
not if you are mounting into a directory contained in an encrypted home.
The encrypted folders are not available on boot when the NFS share is
mounted.
Use this guide for help https://help.ubuntu.com/community/NFSv4Howto
--
I am running Ubuntu 10.04 as an NFS 4 server and 10.04 as an NFS 4
client. I am able to mount NFS shares manually on the client eg.
# mount -t nfs4 -o proto=tcp,port=2049 nfs-server:/music
/home/user/Music
I am also able to mount shares on the client using
# mount -a (When there is an entry in
I should add that in the above I am using a default Ubuntu network set
up and a wired connection
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Actually, what solves the issue is adding _netdev to the nfs mount
options in fstab. This way it is mounted after the network has come up.
Example:
10.1.1.1:/home /home nfs
rsize=32768,wsize=32768,intr,noatime,_netdev0 0
this fixed it for me.
--
nfs mounts specified in fstab is not
Upgrading to 9.10 did NOT solve this for me.
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Upgrading to 9.10 did fix this for me. Unfortunately 9.10 completely
broke suspend/resume on my laptop so I had to go back to 9.04. Issuing a
sudo mount -a before opening Rythmbox has become so 2nd nature for me
now I don't even remember doing it most of the time.
--
nfs mounts specified in
I noticed mt install no longer has a mountnfs.sh in /etc/init.d or any
other location.
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
It seems my issue was caused by network manager. Issuing the command
sudo update-rc.d -f NetworkManager remove
fixed it for me.
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
I just want to say that I upgraded an edubuntu machine from 8.04 to 8.10
and got this too. I added sleep 45 and mount -a to /etc/rc.local
rebooted and it worked.
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification
The problem went away after I upgraded from 9.04 to 9.10. You may want
to upgrade to the latest release as well. Good luck.
Thanks,
jwillar
jwil...@gmail.com
The answer to the question of life, the universe and everything is 42
On 02/18/2010 05:31 PM, nroussi wrote:
I just want to say
I'm having this problem 9.04 jaunty kubuntu install. Bonded interfaces
and static IP caused problems with network manager. I removed network
manager and then noticed the NFS mounts not auto-mounting a boot. Not
sure when the behavior actually started. I'm planning a parallel install
on this
I experienced the problem after cloning a system: With the 1st system,
everything works fine. After creating an identical clone the network mounts
were missing. The good news is that after quite some hours of searching I could
track down and resolve the problem. The basic cause is that the
I'm having the same problem in Karmic Alpha 6. It worked perfectly on
the same machine in Jaunty. DNS resolution is failing even though all my
hosts are in /etc/fstab
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug
to //mark Greewood. Try upgrading your existing install. Out of three
systems I maintain, the two upgraded one work but mine was a fresh
install fails. jwillar
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification
This is weird...
Today i cloned my install of ubuntu that was having problem into 2nd vm and it
was able to mount nfs w/o any problems...
2 identical VMs...one can mount nfs, the other can't :/
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You
On Thu, 2009-08-13 at 17:56 +, MxxCon wrote:
Scott, If this is such a significant and fundamental problem, how come
it's not affecting every single ubuntu installation out there? or are we
the only ones to report it?
Because very few people actually use NFS?
Scott
--
Scott James
I use NFS on a number of computers, all running Jaunty, but only one of
them has this problem...
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
#MxxCon - I was pretty skeptical myself after all it has not been
working for a while and I have not really changed anything much. Except
perhaps for explicitly defining the location of my credentials file (it
was in home but it may be possible it was not picking it up at boot). So
just to be
On Thu, 2009-08-13 at 06:02 +, Havard Bjastad wrote:
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
I would not say that this is a paper cut.
Working on fixing this problem has been a multi-year effort so far, with
at least a year more of development to
as per comment #38
** Changed in: hundredpapercuts
Status: New = Invalid
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Project changed: hundredpapercuts = null
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
epicurea:
Except perhaps for explicitly defining the location of my credentials file
...
//server.name/share /smb/somefolder smbfs
auto,credentials=/home/username/smbcredentials,uid=XXX,gid=XXX,umask=000 0 0
Whereas previously they looked like:
//server.name/share /smb/somefolder smbfs
Scott, If this is such a significant and fundamental problem, how come
it's not affecting every single ubuntu installation out there? or are we
the only ones to report it?
I would imagine something like this should be relatively simple to
diagnose(not necessary fix) to pinpoint why exactly nfs
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Seems to be working ok as of today - possibly some updates fixed it,
though I wouldn't know which.
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Another option I learned while researching this, add a line to crontab
to mount -a at reboot. I am using 'Scheduled Task' app to do this now
and at least I now get my NAS drive to mount whenever I boot up. Still
doesn't want to mount when logging off/on though. JohnL
--
nfs mounts specified
'mount -a' in cron on boot is not really an option but a dirty workaround for a
broken system. :(
It's supposed to be mounting on bootup...that's why there are startup scripts
for it.
epicurea(#33), i just rebooted one of my servers with all the latest
updates and it's still not mounting.
--
I concur but it beats having to run 'mount -a' from a terminal after
each sys boot. I really find it hard to believe this problem has
persisted for so long. Apparently the BUG approach has not been
successful. I wonder if a fix is included in the 100 paper cut
initiative?
--
nfs mounts
I'm experiencing the same problem with 9.04.
NFS doesn't mount on boot.
My boot sequence looks like this:
* Mounting local file systems... [OK]
* Activating swapfile swap... [OK]
* Configuring network interfaces... [OK]
* Starting portmap
I'm new to this forum, so please bear with me.
My NFS mounts broke with Jaunty Jackalope. I tried all the tips above,
but none worked.
Instead, I looked at Network Administrator and noticed that for my wired
connection, ROAMING PROFILES was enabled.
My laptop doesn't roam, so I replaced roaming
Running the current release of Ubuntu 9.04, a few weeks ago I began
having the same problem described here where my system stopped
automatically mounting my NAS drive during a system boot (manually
mounted using 'sudo mount -a). I use the following line in fstab.
//192.168.0.9/Volume_1
I am interested to know if adding 'sleep 45' before 'mount -a' in
rc.local will work for EmonkIA
At first I was under the assumption that it wasn't working with mount -a
in rc.local. As I am under the impression that the boot sequence has
changed, I was wondering if rc.local was also
I haven't tried a sleep 45 in rc.local, but I am sure it, or something within
120 seconds would work. I can ssh into the server just as the daemon comes up
and do mount -a, as it works fine by then. I'd hate to put another delay in
the boot, as it already has to time-out 2x for QLogic boards
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.04
DISTRIB_CODENAME=jaunty
DISTRIB_DESCRIPTION=Ubuntu 9.04
Linux rambc 2.6.28-14-generic #47-Ubuntu SMP x86_64 GNU/Linux
Terminal server using Ubuntu Desktop install
I have found this bug to exist on a server that was upgraded from 7.04
directly to 9.04 (in
I am having this exact problem as well. Unfortunately rudd-o's fix is
not working for me.
Interestingly enough, I have two identical machines, and one is running
an exact image of the other's install of ubuntu 9.04 that was cloned
onto another SATA flash module using dd. The initial machine works
Just to add some more information to this:
mount -a works when I run it manually, however it does not work when
added to crontab or in rc.local (even with sleep 10 preceding it)
I have three of these identical computers. The operating system
install/configure was done on one of them, and
Thank you, Rudd-O. I was going nuts about this. :)
This bug caused a hang on shutdown as well here. No fun ... but finally
solved.
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of
rud...@manuel-desktop:~$ grep nfs /etc/fstab
192.168.2.254:/var/shared/Entertainment/Music/media/music nfs
ro,bg,soft 0 0
fails to mount on boot.
the trick is to KILL networkmanager and let the default system
networking init.d script take over. if networkmanager is the one
@epicurea:
Rebooting after this does not fix the problem: you mean you don't get a DHCP
address for eth0 ? Or that you get an address but NFS still doesn't mount at
boot ?
@COD:
The problem with wireless is that the connection is usually tied up to
user-level data (AP to connect to,
@Thierry Carrez:
I do get a DHCP address, but the NFS still does not mount. sudo mount -a still
works of course.
Thanks
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm having the same problem in Jaunty - NFS not mounting on boot. It's a
wireless connection - the relevant part of /etc/network/interfaces is
auto wlan0
#iface wlan0 inet dhcp
Am I understanding correctly that if I uncomment that line the NFS mount
at boot may work properly?
--
nfs mounts
Thierry Carrez: Sorry for the disappearing act - have been very busy.
The lines in /etc/network/interfaces used to read:
auto lo
iface lo inet loopback
Following ThomasNovin's suggestion, I backed up the original file and
replaced its contents with:
auto eth0
iface eth0 inet dhcp
Rebooting
I just upgraded from intrepid to jaunty and began seeing the same
problem: NFS mounts are not performed at boot time but mount -a does
mount them without a problem.
It seems that sysvinit is not installed. The relevant part of my
/etc/network/interfaces is
auto eth0
iface eth0 inet static
I had the same issue on my daughters PC after upgrading from 8.04 to
8.10 then to 9.04. I did not test between upgrades so the fault may have
started at 8.10.
During 1 of the upgrades it gave an option to use my custom dhcp.conf or
a new one, I chose new.
On the first test after the final
** Changed in: sysvinit (Ubuntu)
Status: Incomplete = New
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Good day! I am experiencing this same issue. I am currently performing
a diskless client boot and the home directory located on a NFS
filesystem is not being mounted automatically. when FSTAB is parsed by
/etc/rcS.d/S45mountnfs.sh.
I can however, perform a mount -a, and the NFS filesystem is
How is your network configured ?
You should probably be using static system-wide network definition
(/etc/network/interfaces) if you want the network to be up in time for
the NFS mounts (and network services) to start correctly... If you're
using NetworkManager or any other session-related
Thomas: I don't think it would work (at least not in all cases) as the
network goes up only when the session is joined. At that point you
should definitely avoid using network-manager if you want to mount
filesystems at boot. The alternative would be to use gvfs network
filesystem access from
Forgive my complete ignorance, but I am not sure what you mean by
NetworkManager managed network. The NetworkManager applet has been
operational for as far back as I can remember and as I said, nothing has
changed from my end (from Feisty onwards) except the OS version. In
other words, mounting
epicurea: if your network is defined in /etc/network/interfaces, then
it's not handled by NetworkManager. In doubt, please attach your
/etc/network/interfaces file.
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification
I'm using NetworkManager (interfaces is empty).
I guess I have to disable NM and go back to using config in
/etc/network/interfaces.
If you were to run the mountnfs.sh script as the last script + mount
with a long timeout, would that also work?
** Changed in: sysvinit (Ubuntu)
Status:
@epicurea: IIRC network for wired interfaces were configured in
/etc/network/interfaces in Hardy and past versions.
If you manage your interface from there instead it will probably work.
Something like:
auto eth0
iface eth0 inet dhcp
(if you get your IP-address from a DHCP server)
--
nfs
Same problem. This problem has only emerged since Intrepid as I never
had this problem with the previous versions. Sudo mount -a works after
boot every time, so presumably the network is not available during boot.
I have tried re-installing Intrepid but this has not helped.
--
nfs mounts
The error reads something like this:
mount.nfs: DNS resolution failed for 192.168.0.113: name or service
unknown
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I noticed that you actually get an error message in the boot process.
The try to mount is clearly done before the network i started. I will
try to halt the boot and write down the error (since it's not recorded
in any file).
Also found bug #46516 which seems to have been the same problem but it
I'm on Jaunty alpha and I also have this problem.
I tried adding ASYNCMOUNTNFS=no but that had no effect.
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have this problem too. However, adding ASYNCMOUNTNFS=no to
/etc/default/rcS did not help. Running 8.10.
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have the home directory mounted over NFS by listing it in /etc/fstab. has
been working fine up until a few days ago.
I've the same problem too - still up to now (with 8.10 beta). I couldn't fix
it, so I've every time to mount the NFS dirs by shell.
--
nfs mounts specified in fstab is not
adding
ASYNCMOUNTNFS=no
to
/etc/default/rcS
makes it work again. real problem is probably in
/etc/init.d/mountnfs.sh
or even more likely it should be run as port of ifup
/etc/network/if-up.d/mountnfs
thats not being run or it's run to early or something.
--
nfs mounts specified in fstab
Please specify what version of Ubuntu you are using, and the concerned
version of the sysvinit package (if you are sure that the bug is with
this package).
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because
this is for Ubuntu intrepid
Well I noticed the problem before
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/270158
it's some type of race in the boot sequence.
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug
79 matches
Mail list logo
