[ILUG] Dapper won't mount NFS drives at boot

[Niall O Broin]

On 5 Dec 2006, at 19:40, Conor Wynne wrote:

>> Are the mounts specified in /etc/fstab as IP addresses or DNS names?
>>
>> It's a problem I've been having with a sarge box and still
>> haven't sorted, despite the fact that named is set to come up
>> before NFS.
>
> Yes, I had that issue too. I was sure that the init scripts were  
> set in
> the correct order,
> All the services (dependencies) were started fine too, yet fstab
> wouldn't mount the nfs volumes.

OK - I've been doing some more research into this. I happened to  
notice error messages appearing at bootup from the /etc/network/if- 
up.d script which SHOULD mount nfs. I had tried to make it leave some  
traces but it turns out that it didn't because at the time it ran,  
the disk was still mounted ro.

Further investigation reveals that the scripts are run when lo is  
configured, which happens from /etc/init.d/loopback, but they fail  
because of unwritable disks. When later in /etc/init.d/networking  
ifup -a is run to configure all interfaces, the /etc/network/if-up.d  
scripts for some reason are NOT run.

> Failing that, you could use /etc/rc.local (or whatever ununtu call it)
> and \ount it automagically once all the other scripts are finished  
> loading.

Been there, done that - it offends me :-)

> I googled and rc.local is not in ubuntu (knew that) :
> http://www.debian.org/doc/FAQ/ch-customizing.en.html

Perhaps debian doesn't use rc.local, but ubuntu does - and even  
integrates it into the SysV startup with a script which calls it, / 
etc/init.d/rc.local.



Niall