[SOLVED] NFS share not mounting at boot

Hi All,
I have an NFS share listed in fstab and it doesn't mount at boot; however, when i mount -a, it mounts fine. Any thoughts?
Thanks.
Shawn
Last edited by shawn.abdushakur (2011-05-06 12:21:27)

@damnshock: Good point . Here it is:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda1 swap swap defaults 0 0
LABEL=arch / ext4 defaults 0 1
UUID=c1a8b2e0-bf9e-4382-ac4e-15c2aec65090 /srv/nfs ext3 defaults 0 0
/srv/nfs/shawn/Documents /home/shawn/Documents none bind
/srv/nfs/shawn/Downloads /home/shawn/Downloads none bind
/srv/nfs/shawn/Music /home/shawn/Music none bind
/srv/nfs/shawn/Pictures /home/shawn/Pictures none bind
/srv/nfs/shawn/Videos /home/shawn/Videos none bind
xbmc:/srv/nfs/watch /home/shawn/Downloads/torrents/watch nfs rsize=8192,wsize=8192,timeo=14,intr

Similar Messages

[Solved]NFS Client Not Mounting Shares

Here is my setup:
I have two Arch boxes that I am attempting to setup NFS shares on. The box that is going to be the server is headless FYI. So far, I have installed nfs-utils, started `rpc-idmapd` and `rpc-mountd` successfully on the server, and started `rpc-gssd` successfully on the client.
The folder I am trying to share is the /exports folder.
ls -l /exports
produces
total 8
drwxrwxrw-+ 110 daniel 1004 4096 Dec 6 17:26 Movies
drwxrwxrwx+ 13 daniel users 4096 Jan 8 19:12 TV-Shows
On the server:
/etc/exports
# /etc/exports
# List of directories exported to NFS clients. See exports(5).
# Use exportfs -arv to reread.
# Example for NFSv2 and NFSv3:
# /srv/home hostname1(rw,sync) hostname2(ro,sync)
# Example for NFSv4:
# /srv/nfs4 hostname1(rw,sync,fsid=0)
# /srv/nfs4/home hostname1(rw,sync,nohide)
# Using Kerberos and integrity checking:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/home gss/krb5i(rw,sync,nohide)
/exports 192.168.1.10(rw,fsid=0)
On the client:
showmount -e 192.168.1.91
Export list for 192.168.1.91:
/exports 192.168.1.10
Everything is looking hunky-dory. However, I go to mount using
sudo mount -t nfs4 192.168.1.91:/exports /mnt/Media
and the mount never takes place. It sits there and does nothing. I CAN, however, kill the process with Ctrl-c.
So does anybody have ANY idea why my shares aren't working.
EDIT: Just thought I should mention that all of the data in the /exports folder is a mount --bind from /mnt/media. All of the /mnt/media is contained on a USB external hard drive. I did notice that there is an ACL.
getfacl /exports
getfacl: Removing leading '/' from absolute path names
# file: exports/
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
Last edited by DaBungalow (2014-01-10 03:18:05)

I found what the problem was. Apparently rpc_gssd was causing a problem. Stopping it fixed everything.

[SOLVED] External HDD not mounting at boot

So, I've got this USB external HDD which won't mount at boot time. I set it in /etc/fstab using its UUID and it works immediately after boot if I do
sudo mount -a
I had it before on a different machine, running Arch too, and never had this problem. How can I see what's going on at boot time? I usualy just start the computer remotely (wake on lan).
Last edited by RaisedFist (2010-10-21 11:22:46)

Couldn't it be caused by the external HDD not being ready yet when the system boot? Nowadays I rarely encounter these issues, but some years ago even certain internally connected drive would need a delay to get ready for boot. If so settings in BIOS has to be adjusted.
Just a quick guess.

Solaris 10/08 w/ ZFS rpool NFS doesn't mount at boot time?

I've got an issue with NFS not mounting vfstab entered mounts during boot and was wondering if the latest Sol 10/08 with ZFS had anything to do with it.
1) #vi /etc/vfstab
server:/vol/share - /share nfs - yes rw,bg,hard,nointr,rsize=32768,wsize=32768,noac,vers=3,timeo=600
server2:/vol/share2 - /share2 nfs - yes rw,bg,hard,nointr,rsize=32768,wsize=32768,noac,vers=3,timeo=600
2) reboot -- -rv
Upon rebooting, the shares do not show up, but doing a mountall mounts them finally:
#mountall
mount: /tmp is already mounted or swap is busy
3) Doing a df -k at this point shows me they mounted.
So what gives? Why are they not mounting at boot? I tried to get around it by doing removing the vfstab entries, adding them into auto_master and then using cachefs, but my employer was not satisfied with autofs and wants them at boot and persistent via the vfstab. So what can be done to get this to work?
Thank you,
--tom

It appears I didn't have all of the services set online correctly:
#svcs |grep nfs
online Jan_05 svc:/network/nfs/status:default
online Jan_05 svc:/network/nfs/nlockmgr:default
So, I enabled the following:
#svcadm enable nfs/mapid
#svcadm enable nfs/cbd
#svcadm enable nfs/client
#scvs |grep nfs
Checked again:
#svcs |grep nfs
online Jan_05 svc:/network/nfs/status:default
online Jan_05 svc:/network/nfs/nlockmgr:default
online 15:48:24 svc:/network/nfs/mapid:default
online 15:48:33 svc:/network/nfs/cbd:default
online 15:48:42 svc:/network/nfs/client:default
Tested to make sure no errors were reported:
# svcs -xv
Then rebooted again.
Voila! It worked! Sometimes reading the documents on docs.sun.com pay off. I was just being too lazy to do it and gave up when I posted this. The solution is to check the services and ensure nfs/client is running correctly and then try rebooting again.

Checking if NFS share is mounted on client

Hi
I would like to check on my nfs server if a nfs share is mounted on a client.
If I mount a share it is listed in /proc/fs/nfs/exports on the server, but it looks like it's not updated when the share is unmount; it still contains a line with the clients ip.

It looks like /var/lib/nfs/rmtab is the right file to check

[SOLVED] /home not mounted on boot after installing tp_smapi

Hi. After installing tp_smapi, my /home partition isn't mounted on boot any more.
I can log in as a normal user, but I am then left with a command line and thus need to mount /home manually and launch X/dwm with startx. The startup shell shows no error messages.
After I uninstall tp_smapi, X starts up automatically again and everything seems to work.
Here's my fstab:
/dev/sda2 / ext4 rw,noatime,data=ordered 0 1
# /dev/sda4 UUID=9d976c9a-4fe2-4cc9-a8b9-c22c713149d7
/dev/sda4 /home ext4 rw,noatime,data=ordered 0 2
# /dev/sda3 UUID=a6153a96-b9ef-412f-a670-af6775275f15
/dev/sda3 none swap defaults 0 0
I am dual-booting Arch with Windows XP on a Thinkpad X60s. A /mnt/home folder also exists. And, the error aside, tp_smapi seems to work nicely,
Thanks for any help!
Last edited by marttt (2013-06-01 20:59:55)

Okay, it works now (after creating /mnt/home anew and rebooting). However, I wonder why did tp_smapi touch my mount points in the first place?
Last edited by marttt (2013-05-31 20:46:09)

Files in NFS share not visable

I'm trying to install Solaris 10u4 from a Netra T1-200 install server. The client is a Sun Enterprise 5000, it boots fine during the network install but gives the error "The directory you specified doen not contain a valid Solaris OS image".
If I mount the same NFS share from a Linux box I can see all the files in the Boot directory but there are no files visable in the Tools or Solaris_10 directory. I've verified that they exist on the Netra but the are not visable in the share.
Any help in resolving this problem would be greatly appreciated.
Thanks,
Jack

OK, i can replicate it by doing the following on the server:
<pre>
# touch test\ file\ one.txt
# touch test\ file\ one\ two.txt
# touch test\ file\ one\ two\ three.txt
# touch test\ file\ one\ two\ three\ four.txt
# touch test\ file\ one\ two\ three\ four\ five.txt
</pre>
the last two files (ending in four and five) do not appear in finder.
It seems that if there are 5 or more spaces in a filename the file will not appear.
This seems like a bug doesn't it? how would I go about reporting it to apple?
Thanks
ed

[SOLVED] NFS protocol not supported

I get this error:
mount.nfs4: Protocol not supported
when trying to mount a NFS share from my server like so:
sudo mount -t nfs4 192.168.1.20:/srv/nfs4/ /media/server
I can mount it on my raspberry pi, but not on my arch laptop.
The server configuration is like this:
/srv/nfs4/ 192.168.1.1/24(rw,fsid=root,no_subtree_check)
/srv/nfs4/media 192.168.1.1/24(rw,no_subtree_check,nohide)
showmount -e gives this:
Export list for 192.168.1.20:
/srv/nfs4/media 192.168.1.1/24
/srv/nfs4 192.168.1.1/24
Any ideas?
Last edited by marius (2013-08-17 12:50:46)

I don't think you are supplying all the information that you are given by your machine. The error you mention is often preceeded by a number of other messages which give some idea of what is actually occurring. Please post error messages exactly as they are given to you, and check the journal and/or dmesg for more information.
Also as a side note, you need to use code tags for things like commands and output. Hit the quote button on this post to see how I created the boxes below (the arrows will make sense when this post is quoted):
<--These are code tags-->
<--These are quote tags-->

Drive not mounting after boot

I believe this is an epidemic problem in OS X. I have seen this problem on OS X 10.5 to 10.8.2. The fundament issue is that external drives will not mount randomly after the system is powered down and restarted. I have seen the problem with USB 2.0 and Firewire attached drives. I have seen this on many hardware platforms from PowerPC to i7 2.6GHz. I have seen the problem on different enclosures, WD, NextStar, Lacie etc. I have tried numours remedies like resetting the PRAM. The only remedy that works is unpluging the drive and pluging it back in, which if very annoying espicially since this is most prevalent in Time Machine backup drives. The many people who I help with their MACs don't often notice that Time Machine has been failing to backup for weeks since their drive has silently not mounted. Is there a real solution for this out there? It seems to me like a boot timing issue. Where the drive is not recognized by the low level driver, if it becomes powered on at a later time in the boot cycle. I can't really pin it down as it happens often but not often enough for any predictable pattern.

I believe this is an epidemic problem in OS X. I have seen this problem on OS X 10.5 to 10.8.2. The fundament issue is that external drives will not mount randomly after the system is powered down and restarted. I have seen the problem with USB 2.0 and Firewire attached drives. I have seen this on many hardware platforms from PowerPC to i7 2.6GHz. I have seen the problem on different enclosures, WD, NextStar, Lacie etc. I have tried numours remedies like resetting the PRAM. The only remedy that works is unpluging the drive and pluging it back in, which if very annoying espicially since this is most prevalent in Time Machine backup drives. The many people who I help with their MACs don't often notice that Time Machine has been failing to backup for weeks since their drive has silently not mounted. Is there a real solution for this out there? It seems to me like a boot timing issue. Where the drive is not recognized by the low level driver, if it becomes powered on at a later time in the boot cycle. I can't really pin it down as it happens often but not often enough for any predictable pattern.

Nfs /vol not mounted

nfs umount: /vol: not mounted
WARNING: forceload of misc/md_raid failed
WARNING: forceload of misc/md_hotspares failed

Solution
Remove all entries from mac os disk manager (nfs) (better copy&past the entries into a text file)
sudo automount -vc -> working
Setup absolutely the same in disk manager again -> working
however
Lion-Mac-Pro:~ me$ sudo automount -vc
automount: /net updated
automount: /home updated
automount: /Users/me/Music updated
automount: /Users/me/Pictures updated
automount: /Users/me/Downloads updated
automount: /Users/me/Documents updated
automount: /Volumes/foo updated
automount: no unmounts

External drive does not mount on boot

I have a Toshiba MK5055GSX 500GB external drive which I use for Time Machine but for some reason it does not automatically mount from a cold boot. Before I started to use it for Time Machine (it was formatted as NTFS at the time) I had not problems with it. All other external drives correctly mount on boot.
I had thought it might be a problem with the drive itself but if I disconnect it and reconnect it with my iMac running it mounts every time without fail. If I reboot after it has mounted it also mounts at boot. Only if I start the iMac using the power button with the drive already connected does it fail to mount and the results are consistently repeatable.
Does anyone have any ideas why this might be happening and how to fix it?

Does this drive have a separate power brick? If it does I suggest using it to see if that fixes the problem. If the enclosure has both USB and Firewire ports try using the drive on a Firewire port instead of a USB port.
It sounds like the drive is not spinning up early enough in the startup process to be detected.
Not knowing how you prepared the drive for the Mac, you should re-prep the drive as follows:
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.

[SOLVED] Gnome does not mount ipod after system upgrade

I did a system upgrade today (2009.12.04) and now gnome does not mount my ipod video (gnome used to mount the ipod without problems before de upgrade).
Here is some information about the system messages:
Last lines of the output of dmesg before plugging the ipod:
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
After plugging it:
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
usb 1-4: new high speed USB device using ehci_hcd and address 3
usb 1-4: configuration #1 chosen from 2 choices
Initializing USB Mass Storage driver...
scsi6 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb 1-4: reset high speed USB device using ehci_hcd and address 3
usb 1-4: reset high speed USB device using ehci_hcd and address 3
usb 1-4: reset high speed USB device using ehci_hcd and address 3
usb 1-4: reset high speed USB device using ehci_hcd and address 3
usb 1-4: reset high speed USB device using ehci_hcd and address 3
scsi 6:0:0:0: Device offlined - not ready after error recovery
usb-storage: device scan complete
The output of the lsusb command:
[miguel@miguel ~]$ lsusb
Bus 002 Device 002: ID 0408:030c Quanta Computer, Inc. HP Webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 05ac:1209 Apple, Inc. iPod Video
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lsusb shows ipod is in Bus 001
Any help?
Many tks
Last edited by mmf1902 (2009-12-29 04:42:11)

Finally found the problem was the Ipod itself. After a soft reset everything worked again.

[SOLVED] pam_mount will not mount truecrypt volume on login.

Hello.
I did system upgrade yesterday and encountered some problems with mounting my Truecrypt volume with pam_mount. I use pam_mount to mount my encrypted /home partionion at login. After first reboot and loging in I was dropped to / directory, with my /home partition clearly not mounted. I acknowledged the message from udev in pacman, that in some circumstances adding 'loop' to MODULES array in /etc/mkintcpio.conf is required and for a moment I thought it was it, but I tried this and it didn't help. Suprisingly, after another reboot I was placed im my home directory afer login, but it appears to be empty - I can see only dotfiles of few programs I used after the upgrade:
$ls -A ~/
.bash_history .links .qingy .viminfo .wicd
but my /home partition is obviously still not mounted. My relevant config files:
/etc/security/pam_mount.conf.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE pam_mount SYSTEM "pam_mount.conf.xml.dtd">

<pam_mount>

<debug enable="0" />




<mntoptions allow="nosuid,nodev,loop,encryption,fsck,nonempty,allow_root,allow_other" />

<mntoptions require="nosuid,nodev" />

<logout wait="0" hup="0" term="0" kill="0" />

<cryptmount>truecrypt --text --protect-hidden=no --keyfiles="/etc/home.key" %(VOLUME) %(MNTPT)</cryptmount>
<cryptumount>truecrypt -d</cryptumount>
<volume user="schirase" fstype="crypt" path="/dev/sda7" mountpoint="/home" options="fsck,relatime" />
<mkmountpoint enable="1" remove="true" />
</pam_mount>
/etc/pam.d/login
#%PAM-1.0
auth required pam_securetty.so
auth requisite pam_nologin.so
auth required pam_unix.so nullok
auth required pam_tally.so onerr=succeed file=/var/log/faillog
auth optional pam_mount.so
# use this to lockout accounts for 10 minutes after 3 failed attempts
#auth required pam_tally.so deny=2 unlock_time=600 onerr=succeed file=/var/log/faillog
account required pam_access.so
account required pam_time.so
account required pam_unix.sof
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
password optional pam_mount.so
#password required pam_unix.so sha512 shadow use_authtok
session required pam_unix.so
session optional pam_mount.so
session required pam_env.so
session required pam_motd.so
session required pam_limits.so
session optional pam_mail.so dir=/var/spool/mail standard
session optional pam_lastlog.so
session optional pam_loginuid.so
-session optional pam_ck_connector.so nox11
-session optional pam_systemd.so
/etc/pam.d/qingy
#%PAM-1.0
auth required /lib/security/pam_securetty.so
auth required /lib/security/pam_unix.so
auth required /lib/security/pam_nologin.so
account required /lib/security/pam_unix.so
password required /lib/security/pam_unix.so
session required /lib/security/pam_unix.so
session optional /lib/security/pam_console.so
Any ideas how to make it work again?
[EDIT] OK, I've looked into it a little more and I realised that I should try loging in without qingy. I tried on agetty console and it worked as before. It looks like qingy upgrade changed my /etc/pam.d/qingy file into default one. The one above is and obviously unsuitable for use with pam_mount and I failed to see that at first. It should look similar to the example file for slim in the wiki article on pam_mount:
#%PAM-1.0
auth required /lib/security/pam_securetty.so
auth required /lib/security/pam_unix.so
auth optional /lib/security/pam_mount.so
auth required /lib/security/pam_nologin.so
account required /lib/security/pam_unix.so
password required /lib/security/pam_unix.so
password optional /lib/security/pam_mount.so
session required /lib/security/pam_unix.so
session optional /lib/security/pam_mount.so
session optional /lib/security/pam_console.so
Sorry for the trouble, maybe at least it will help someone.
Last edited by Schirase (2012-03-25 17:49:21)

Having looked again, hal fails to start. I have it in rc.conf DAEMONS. When i try to start Hal manually, it also fails to start ...
Last edited by whitetimer (2010-11-09 16:45:46)

[SOLVED] Partitions not mounted on boot / boots to (none)

I have strange problem after I ran pacman -Syu today. After reboot I can't login and it doesn't show hostname in login window, I do get kdm login screen.
If I select console login or change to tty1 then I can login as root, without any password asked.
After that I am able to mount partitions just fine, and I am also able to chroot in and update the system, didn't help. I also tried downgrading kernel to 3.5.6.1, with no change in behaviour.
I don't have /usr on different partition but decided to try adding usr and shutdown to mkinitcpio hooks anyway, again no improvement.
Recent update only brought shadow.pacnew, which I merged. I do pacnew merges after each update.
Any pointers on where to go next?
Thanks in advance.
Last edited by thepanu (2012-11-01 20:21:41)

You need to understand what you are actually doing when you overwrite old files with new ones. When there is a recommendation to "merge" your pacnew files, that doesn't mean just go ahead and use the new ones. It means you should take the time to see what is in them, see where they differ, and then make an educated decsion on what to do with them from there.
If this is how you have always been handling pacnew files, don't expect that the prolem is totally solved. I would not be suprised if this one sneaks up and bites you in the ass.

[Solved] NFS shares root filesystem

[edit] Sorry, my fault. I was using Nautilus m(
and i think it silently switiched to using sftp.... still wondering why no password was prompted.
Hi!
I set up nfs following the wiki. It works, but i can access the whole remote-root-filesystem, not just the nfs-root. Is https://wiki.archlinux.org/index.php/NFS up to date?
greetings
Server:
cat /etc/exports
/srv/nfs4/ 192.168.0.0/24(ro,fsid=0,no_subtree_check)
/srv/nfs4/a 192.168.0.0/24(ro,no_subtree_check)
/srv/nfs4/b 192.168.0.0/24(ro,no_subtree_check)
[root@alarmpi srv]#
Client:
showmount -e 192.168.0.116
Export list for 192.168.0.116:
/srv/nfs4/a 192.168.0.0/24
/srv/nfs4/b 192.168.0.0/24
/srv/nfs4 192.168.0.0/24
Last edited by matto (2015-03-22 14:50:59)

Thanks for the hints. Meanwhile, I have done some more background reading on running Arch in VMWare Player. In particular I followed the guidelines in this article. So it turns out that X requires some special configuration when run from within VMWare.
pacman -S xf86-input-vmmouse xf86-video-vmware xf86-video-vesa svga-dri
and a vmwgfx module is supposed to be loaded. I installed tha packages and tried to load vmwgfx, but when I do lsmod I just can't see it. Then it was pointed out to me that it might be a kernel mismatch problem. The linux installed on nfsroot is 3.6.2 whereas for some reason uname -a gives me version 3.5.6.
I've tried to rebuild initramfs with the new kernel using -k switch of mkinicpio, but it didn't help. It still boots into 3.5.6. It as if the initramfs from the client was taking precedence. So then I went back to the previous image of my VM, updated the system, made appropriate changes to mkinitcpio.conf and run mkinitcpio... and it no longer boots. mount: protocol not supported. I will post the details in my other topic.

[SOLVED] NFS share not mounting at boot

Similar Messages

Maybe you are looking for