fstab that worked with FC5 !work w/ DD

[whil]

Hi folks,

Still plugging along and having fun. Next step is to hook my Kubuntu Dapper Drake box into my network.

I have a server that I'm trying to connect to. I have a directory on my Kubuntu box, /home/wh/bambi, that I'm going to map to a directory on my server, just like I did with my FC5 box.

I unhooked my Fedora Core 5 box and plugged this box in its place - same Ethernet cable, etc. I copied my fstab entries for the share:

//192.168.1.10/bambi /home/wh/bambi smbfs username=wh,password=secret,uid=wh,gid=wh

Upon reboot, two bad things happen.

1. I see an icon on the desktop for the //192 remote share, but right clicking and selecting Mount delivers an error: "mount: only root can mount //192.... on /home/... Please check to see that the device is plugged in correct.

2. Opening up Konqueror, I see 'bambi' under my Home Folder, but there's nothing under bambi. I'm expecting to see the contents of the bambi directory on the server.

This fstab is copied verbatim from my working FC5 box (except that FC5 needs cifs instead of smbfs.)

I do not understand why the remote share isn't being mounted automatically via fstab. I suspect it's something to do with how Kubuntu handles users, but... I'm a rookie in this ballpark.

Thanks,
Whil

[kubicle]

Re: fstab that worked with FC5 !work w/ DD

For some reason your samba share is not automounting at boot time.

I'm no samba expert so I can't offer you a definitive answer why it isn't...but I remember there were problems similar to yours before...and someone 'solved' it by creating a small script to mount the share later in the boot process. Search the forums for something like 'automount samba' for more details.

Check that your fstab line is functional by mounting it manually:

sudo mount //192.168.1.10/bambi

(use umount to unmount if you need to)

That should mount the share (after which the 'bambi' directory should show the contents instead of just the mount-point)

If it mounts ok, you can create a script that will mount it at boot, if it doesn't mount, there is something wrong with the way you've setup the share (connection, share, userid or fstab)

[whil]

Re: fstab that worked with FC5 !work w/ DD

No luck on a manual mount. I get an error:
wrong fs type, bad option, bad superblock on //192.168.1.10/bambi,
missing codepage or other error

Looking up details in syslog, I find
smbfs: mount_data version 1919251317 is not supported

At this point, I'm lost. Is Kubuntu not supporting the mount_data or is this a fault of the server?

Any suggestions?

Thanks,
Whil

[xekaltsotos]

Re: fstab that worked with FC5 !work w/ DD

Hi,

I am experiencing exactly the same problem, also getting the line

smbfs: mount_data version 1684370019 is not suported

along with the 1919251317 one. Whil, maybe you could switch to root

sudo -i

and then manually mount.

[whil]

Re: fstab that worked with FC5 !work w/ DD

I switched the 'smbfs' parm back to 'cifs' and now I can manually mount successfully. No 'mount_data version .... ' error.

However, changing smbfs to cifs in my fstab doesn't work. The remote Share icon shows up on the desktop but it's not mounted, and right-clicking on it and selecting 'mount' scolds me with the "only root can mount..." dialog.

So.... howsacome Kubuntu isn't reading the fstab file?

Whil

[jborsits]

Re: fstab that worked with FC5 !work w/ DD

I to started having this problem when I upgraded to ubuntu dapper and the problem persisted when I moved over to kubuntu. I read that smbfs is being phased out in favor of cifs. I finally got feed up with manually mounting the drive after I logged in and have finally got it working properly.

//192.168.1.10/Shared_Files /home/<username>/Network_Folders cifs credentials=/root/.smbcredentials,dir_mode=0777,file_mode=0664,rw,auto 0   0

I had to do 3 things other then switching to cifs.

1) Edit .smbcredentials and change username to user as it is not a valid option for mount.cifs

2) Change fmask and dmask to file_mode and dir_mode respectively. If you use these options make sure to set the permissions using a 4 digit octal. I'm pretty sure I read you don't need these or the uid and gid options with versions of samba >= 2.2.5 when configured properly (I kludged my server together really quick and have been to lazy to go back and set it up right.) Unfortuently now I can't find that artical.. go figure.

3) I had to set the auto option. I couldn't get it to mount at boot any other way.. I tried setting _netdev but that didn't work either.

hope this helps.. I know I ran in circles a bit looking for an answer.