I had problems like this in an earlier knoppmyth (based on debian). When booting not all of /etc/fstab is handled by the same script in /etc/init.d. Local disks are mounted in one script and network mounts are mounted in another script. (although this may be distro dependent).
Each of the scripts greps /etc/fstab for the filesystems it want so to deal with and then runs the mount command only on the entries that it wants to mount. At one stage the debian network mount script only grepped for nfs and smbfs filesystems, but not cifs. I had to hack the script to get it to mount cifs as well. The later version of knoppmyth that I now run (no doubt containing a later version of the init scripts) has fixed this. Anyway what I am saying is that its not simply enough to place something in /etc/fstab, your init script also has to be written to mount that particular filesystem, or the line will be ignored. Whether that is your problem is unknown without looking closely to see what is going on. Anyway, your solution works. But you may be better to make the command: mount -a -t cifs which will restrict it to just mounting the cifs mounts. On Tue, January 15, 2008 2:24 pm, Roger Searle wrote: > I have resolved this issue by adding "mount -a" to /etc/rc.local. fstab > mounts are attempted before the required modules are loaded (my > interpretation of the problem following reading various forums and > trying a few things as below). > > Name resolution is coming from the ipcop box on the network. I added an > entry to /etc/hosts for jupiter, this did not help. It has been > suggested that /home might not be mounted before the attempt to mount > drives on jupiter. /home is mounted in the third line, the jupiter > drives at the end. > > The cifs module appeared to be involved in the issue. The smb4K package > (an smbfs/cifs share browser) had stopped working too. Only following > manually mounting a drive with cifs in the relevant fstab line, does > lsmod show cifs as loaded. Adding a "cifs" line to /etc/modules didn't > help the original problem. > > smb4k is still broken even after a reinstall. well, it won't mount > drives any more, it will still report mounted drives and launch a > konqueror window in one which is sometimes handy. I have a script I can > run to mount drives as needed so I'll leave it at that for now. > > Thanks for all the suggestions! > Roger > > > > > Chris Hellyar wrote: >> If the machine (jupiter) is named via a DNS service/server it's possible >> that the dns client hasn't started when the mount is attempted, so it >> times out. Try putting the IP of the server in there instead of the >> name. >> >> >> On Tue, 2008-01-15 at 09:16 +1300, Roger Searle wrote: >> >>> Hi, I can't figure out why the following 2 lines from /etc/fstab are >>> failing to mount the drives, though they will mount manually by doing >>> "sudo mount //jupiter/backup" or "sudo mount /network/jupiter/data/". >>> >>> //jupiter/data /network/jupiter/data cifs >>> credentials=/home/roger/.smbpasswd 0 0 >>> //jupiter/backup /network/jupiter/backup cifs >>> >> >> >> > > -- Nick Rout
