9.1/9.2 Pro: smbmountnot supported by Kernel!

Riddick · 04-07-2005, 08:01 PM

I get this error:

SE:/sbin # mount.smbfs //VI/Folding /home/ed/V_Folding/
Password:
ERROR: smbfs filesystem not supported by the kernel
Please refer to the smbmnt(8) manual page
smbmnt failed: 255

or

SE:/home/ed # mount -t smbfs //VI/Folding /home/ed/V_Folding/ -o username=Guest,uid=ed
Password:
ERROR: smbfs filesystem not supported by the kernel
Please refer to the smbmnt(8) manual page
smbmnt failed: 255

What could it be that desn't let me mount SMBs?
Help would be appreciated!

SE:/home/ed # uname -r
2.6.5-7.145-default

Riddick

Thoreau · 04-07-2005, 08:09 PM

Install smbclient and use the proper nomenclature.

mount -t smbfs -o username=blah,password=blah //WINBOX/C /mnt/c

In fstab,

//winbox/share /mnt/share smbfs username=joe,password=bloggs,uid=500,gid=500 0 0

Using smbmount directly:
smbmount //winbox/share /mnt/share -o username=joe,password=bloggs

Warning about smbmount- it's a finicky POS. Use the first 2 options first.

When mounting at boot, it's good practice to use a credential file out of reach of users that are jerkweeds. Such as:

//winbox/share /mnt/share smbfs rw,credentials=/home/joe/winbox-credentials.txt 0 0

Good luck.

Riddick · 04-07-2005, 08:42 PM

SE:/home/ed # smbmount //VI/Folding /home/ed/V_Folding -o username=VI,password=
ERROR: smbfs filesystem not supported by the kernel
Please refer to the smbmnt(8) manual page
smbmnt failed: 255
SE:/home/ed #

SE:/home/ed # mount -t smbfs -o username=VI,password= //VI/Folding /home/ed/V_Folding/
ERROR: smbfs filesystem not supported by the kernel
Please refer to the smbmnt(8) manual page
smbmnt failed: 255
SE:/home/ed #

I already put it like that in fstab and I was wondering why it wasn't working...
Did mount -a and that when i found this funny kernel error.

This happens from both SuSE 9.1 Pro and 9.2 Pro

Thanks,
Riddick

Thoreau · 04-07-2005, 11:33 PM

cd /usr/src/linux
make xconfig
File Systems, Network Filesystems
Make a module or add smb_fs:

"SMB file system support (to mount Windows shares etc.) (SMB_FS)

SMB (Server Message Block) is the protocol Windows for Workgroups
(WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
files and printers over local networks. Saying Y here allows you to
mount their file systems (often called "shares" in this context) and
access them just like any other Unix directory. Currently, this
works only if the Windows machines use TCP/IP as the underlying
transport protocol, and not NetBEUI. For details, read
<file

ocumentation/filesystems/smbfs.txt> and the SMB-HOWTO,
available from <http://www.tldp.org/docs.html#howto>.

Note: if you just want your box to act as an SMB *server* and make
files and printing services available to Windows clients (which need
to have a TCP/IP stack), you don't need to say Y here; you can use
the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
for that.

General information about how to connect Linux, Windows machines and
Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.

To compile the SMB support as a module, choose M here: the module will
be called smbfs. Most people say N, however."

In short, your kernel is jacked.

Riddick · 04-08-2005, 03:28 AM

Is this the correct thing to do even if I'm not running X in any way?

Riddick · 04-08-2005, 03:29 AM

SE:/usr/src/linux # make xconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/split-include
HOSTCC scripts/basic/docproc
*
* Unable to find the QT installation. Please make sure that the
* QT development package is correctly installed and the QTDIR
* environment variable is set to the correct location.
*
make[1]: *** [scripts/kconfig/.tmp_qtcheck] Error 1
make: *** [xconfig] Error 2
SE:/usr/src/linux #

...Not nice

abisko00 · 04-08-2005, 07:08 AM

For running 'make xconfig' you will need the qt3-devel package. But it is not necessary to re-compile the kernel anyway. smbfs is included in the standard kernels of SUSE. You will find out if you type 'zcat /proc/config.gz | grep SMB_FS'.

So your problem is probably syntax-related or you did not install the package 'samba-client'. Try 'rpm -qa | grep samba' to find out.

I successfully mounted a samba-share (as root) with

Code:

mount -t smbfs //server/directory /mountpoint -o username=name

equinox · 04-08-2005, 07:14 AM

try "make menuconfig"

broch · 04-08-2005, 07:42 AM

Quote:

try "make menuconfig"

????

default install will have only pre-compiled kernel, no sources, if you install these, sources will be clean so menuconfig will show nothing. Plus you need to run it from kernel source folder.
If you want to check what is there, either run
lsmod (if smbfs is module), or check config file in /boot

Riddick · 04-08-2005, 08:38 AM

OK! results:

Code:

SE:/usr/src/linux # rpm -qa | grep samba
yast2-samba-server-2.9.15-12
samba-3.0.9-2.6
samba-winbind-3.0.9-2.6
kdebase3-samba-3.2.1-63
samba-client-3.0.9-2.6
yast2-samba-client-2.9.16-1.2
SE:/usr/src/linux #

So sambaclient is installed... I can access the share I want through smbclient.
Mounting is the Problem. I installed QT3 Devel:

Code:

SE:/usr/src/linux # make xconfig
  SHIPPED scripts/kconfig/zconf.tab.h
  HOSTCC  scripts/kconfig/conf.o
sed < scripts/kconfig/lkc_proto.h > scripts/kconfig/lkc_defs.h 's/P(\([^,]*\),.*/#define \1 (\*\1_p)/'
  HOSTCC  scripts/kconfig/kconfig_load.o
  HOSTCC  scripts/kconfig/mconf.o
/usr/lib/qt3/bin/moc -i scripts/kconfig/qconf.h -o scripts/kconfig/qconf.moc
  HOSTCXX scripts/kconfig/qconf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/lex.zconf.c
  HOSTCC  -fPIC scripts/kconfig/zconf.tab.o
  HOSTLLD -shared scripts/kconfig/libkconfig.so
  HOSTLD  scripts/kconfig/qconf
scripts/kconfig/qconf arch/i386/Kconfig
qconf: cannot connect to X server 
make[1]: *** [xconfig] Error 1
make: *** [xconfig] Error 2
SE:/usr/src/linux #

So that's still no good (I'm accessing this through a shell (no choice)).

There is no SMBFS or anything like that at 'lsmod'.

In the config file in boot:

Code:

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_NFSD_ACL=y
CONFIG_NFS_ACL_SUPPORT=y
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_STATD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp850"
CONFIG_CIFS=m
CONFIG_CIFS_STATS=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_CODA_FS=m
# CONFIG_CODA_FS_OLD_API is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_AFS_FS=m
CONFIG_RXRPC=m


#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
CONFIG_OSF_PARTITION=y
# CONFIG_AMIGA_PARTITION is not set
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
# CONFIG_MINIX_SUBPARTITION is not set
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_NEC98_PARTITION=y
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_EFI_PARTITION=y

smbfs = m (what does that mean? module?)

broch · 04-08-2005, 08:43 AM

yes, this is module. So check if it is loaded:
#lsmod | grep smbfs

Riddick · 04-08-2005, 08:55 AM

it is not loaded. There is Subfs... no smbfs
your grep things don't work... I don't know why

Anyway, guessing the next step:
SE:~ # modprobe smbfs
FATAL: Could not load /lib/modules/2.6.5-7.145-default/modules.dep: No such file or directory

yeah?

Thanks so much this far....

abisko00 · 04-08-2005, 09:08 AM

This is weird! Let's go step by step through your problems:

1. make xconfig still doesn't work:

You cannot run xconfig as root without exporting the display first. That's why I usually make the kernel configuration/compilation as user.

2. Why is there no smbfs?

I have one idea: did you run 'Online Update' recently? And did you reboot afterwards? If not, do so, because otherwise the current kernel doesn't find its modules anymore. If 'rpm -q kernel-default' returns something else than 'uname -r', this is the case.

Riddick · 04-08-2005, 10:29 AM

Ah:

SE:~ # rpm -q kernel-default
kernel-default-2.6.5-7.151
SE:~ # uname -r
2.6.5-7.145-default
SE:~ #

Is this it then... A restart is needed

What am I going to do about the uptime that I'm so proud of?
OK here goes...
No wait, actually I'll restart the 9.2 box.

Ok:
OK

Yes!!!

Excellent! Thanks very much...

You know how it is with linux that you get used to not restarting...

ed@SE:~> uptime
5:37pm up 61 days 2:04, 1 user, load average: 1.01, 1.01, 1.00
ed@SE:~>

Thanks (and congratulations) to everyone!!!

Riddick

Thoreau · 04-08-2005, 05:38 PM

Praise the Lord. Yes, when reinstalling your entire OS(kernel), you must reboot. Glad that fixed it.