problems with smbfs mount-point in /etc/fstab - "mount -a" works, but not at boottime
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Running "mount -a" as root mounts the share just fine, but when I reboot the machine that mount-point is just an empty dir, and the //192.168.0.105/MP3 share doesn't show up in the list displayed by "mount". I've grepped through the logfiles in /var/log for anything matching the case-insensitive text "mp3" without showing up anything - the only reference I can find to that share is in the /var/log/samba/log.smbmount file, and that's just for the times when I've manually mounted the share.
Anyone have any ideas as to what might be going on, or where I could look for more hints as to what's happening here??
Not sure - how would I check for this? I'm afraid my Linux skills are a bit rusty at the moment...
The (apparently) relevant portion of my boot-time syslog looks like the following:
Code:
...
Oct 25 20:52:50 bobafett kernel: cobd0 size: 2097152 kb
Oct 25 20:52:50 bobafett kernel: cobd1 size: 65536 kb
Oct 25 20:52:50 bobafett kernel: cobd: loaded (max 32 devices)
Oct 25 20:52:50 bobafett kernel: cobd1 size: 65536 kb
Oct 25 20:52:50 bobafett kernel: cobd: loaded (max 32 devices)
Oct 25 20:52:50 bobafett kernel: conet: loaded (max 16 devices)
Oct 25 20:52:50 bobafett kernel: conet0: initialized
Oct 25 20:52:50 bobafett kernel: Initializing Cryptographic API
Oct 25 20:52:50 bobafett kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Oct 25 20:52:50 bobafett kernel: IP Protocols: ICMP, UDP, TCP
Oct 25 20:52:50 bobafett kernel: IP: routing cache hash table of 512 buckets, 4$
Oct 25 20:52:50 bobafett kernel: TCP: Hash tables configured (established 4096 $
Oct 25 20:52:50 bobafett kernel: NET4: Unix domain sockets 1.0/SMP for Linux NE$
Oct 25 20:52:50 bobafett kernel: kjournald starting. Commit interval 5 seconds
Oct 25 20:52:50 bobafett kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on cobd(117$
Oct 25 20:52:50 bobafett kernel: EXT3-fs: mounted filesystem with ordered data $
Oct 25 20:52:50 bobafett kernel: VFS: Mounted root (ext3 filesystem).
Oct 25 20:52:50 bobafett kernel: Freeing unused kernel memory: 52k freed
Oct 25 20:52:50 bobafett kernel: Adding Swap: 65528k swap-space (priority -1)
Oct 25 20:52:50 bobafett kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on cobd(117$
Oct 25 20:52:50 bobafett mysqld_safe[426]: started
...
From the above, since the "conet" and "NET4" messages are showing up prior to the "EXT3 FS" / "Adding Swap" messages (by some fraction of a second), would it be safe to assume that, yes, my network stuff is coming up prior to the /etc/fstab file being processed? ...or is there any easier way to figure this out?
Now, my understanding is that the /etc/fstab file is being processed by the running of the command "mount -a" during boot. Is there any way to get this command to log any output as to the results of its execution?
Okay, your post prompted me to figure out how the linux boot-process works. After looking through all the inet.d scripts, I tried manually-invoking all the mount-oriented ones; none of mountall.sh, mountnfs.sh, or mountvirtfs.sh mounted my type=smbfs shares. I started trying to figure out why this was the case, but then got really lazy and since I knew that a post-boot execution of "mount -a" worked just fine, I simply created a new init-script that runs at the end of runlevel-S and just executes the command "mount -a".
May not be the most elegant solution to my problem, but it seems to have done the trick.
make sure that the line you have added in /etc/fstab is AFTER the line which mounts /var. Hmm... I mean, put your entry at the end of the fstab file. Hope this helps.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.