fstab not mounting shares

[knbobick]

I have a bunch of Suse 10.1 boxes authenticating through Active Directory on a Win2003 domain controller running Windows Services for Unix. There is also an Adaptec Snap Server with several nfs shares being exported. All members of 'Domain Users' group are unable to log in unless root logs in after boot and does a 'mount -a'. This is due to the user's home folders being located on the Snap Server and the nfs mounts not being mounted during boot.

The boot.msg file shows only two items that appear related:
- mount server reported tcp not available, falling back to udp.
- mount: RPC: Remote system error - no route to host

I have tried numerous things listed in other posts but to no avail.

My latest attempt is editting /etc/rc.d/rc3.d/k14nfs to include 'sleep 5 && mount -at nfs,nfs4 &' as indicated in the comments, this did not work either.

the line in fstab:
169.1.1.61:/SHARE1 /usr/snafu nfs auto,users,_netdev 0 0

Does anyone know a possible fix to this problem? I am a relative newbie so if there is other info needed, just ask.

Thanks, Keith

[blade4383]

Hi

Can mount the share when u do it manually....

meaning try the line u mentioned in fstab and mount it using command line

[knbobick]

Yes, I can manually mount the drive after the machine is booted. It just won't do it as part of the boot process.

[blade4383]

ok..

could u please write the whole command that u are using with options....also whether it uses username and password...

there is another way to get it mounted without the /etc/fstab
use /etc/rc.local file
add your entry of mount with the command in it...
it is read at bootup

[blade4383]

There is one more cause why this is happening ...

if u add the line in /etc/rc.local and then it mounts then it means that the /etc/fstab is trying to mount the share before the network is available to it...and hence the error "mount: RPC: Remote system error - no route to host"

So if that is the case then it means that _netdev is not giving the sufficient amount of delay that is required for the network to be up...

So again what u can do is ... add an entry in /etc/rc.local "mount -a" ....


Hope this helps

[knbobick]

I have tried it two ways:

mount -at nfs,nfs4
mount -t nfs 169.1.1.61:/SHARE1 /usr/snafu -o auto,users,_netdev

I have place both of these (not at the same time) in a before.local, after.local in addition to the K14nfs file described earlier. Suse's rc does not appear to call rc.local. None have worked.

[blade4383]

Ok ...

so last try from my side...

1. Try putting the script in /etc/init.d/boot.local

mount -t nfs //169.1.1.61/SHARE1 /usr/snafu -o auto,users,_netdev

try the // thing

2. create an rc.local file in /etc/rc.d/ or any rc level .....
with the above mount command.... reboot and give me the good news ..

[knbobick]

I tried your suggestion already and it didn't work either. I believe that I have fixed it. Here's what I did:

- Create a file in /etc/init.d named 'mountshares'
- Insert the mount commands within the file.
- Chmod 655 the file
- run 'insserv -v -d /etc/init.d/mountshares'
- run 'ln -s /etc/init.d/remotemount /usr/sbin/rcmountshares'
- reboot
- successfull login

I have done this on two different machines and it works well on both. I am not exactly sure what 'insserv' is at this point, but I can find that out later.

I got this idea from the Novell site at: FSTAB Mount on Boot Problems - NOVELL FORUMS.

Thanks for all your help!!!

Keith