cifs filesystem not supported

English Install/Boot/Login
#1

Hi

My fstab suddenly does not work. It wount mont the samba shares. I have had this setp for a while, bt today it says that cifs is not supported.
Any idea what this can be?

I get messages as below:

Regards, Bjorn

sudo mount -a
mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

The fstab is like this

/dev/disk/by-id/ata-ST9120823AS_5NJ01WKX-part3 swap swap defaults 0 0
/dev/disk/by-id/ata-ST9120823AS_5NJ01WKX-part1 / ext4 acl,user_xattr 1 1
/dev/disk/by-id/ata-ST9120823AS_5NJ01WKX-part2 /home ext4 acl,user_xattr 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
//nas1/flac /mnt/musikk/flac cifs username=bjorn,password=xx,uid=bjorn,gid=users 0 0
//nas1/media/Music /mnt/musikk/mp3 cifs username=bjorn,password=xx,uid=bjorn,gid=users 0 0
//nas1/arkiv /mnt/arkiv cifs username=bjorn,passwd=bjorn,uid=bjorn,gid=users 0 0
//nas1/bjorn /mnt/bjorn_nas cifs username=bjorn,passwd=xx,uid=bjorn,gid=users 0 0
//nas1/media/Videos /mnt/video cifs username=bjorn,passwd=xx,uid=bjorn,gid=users 0 0
//nas1/skannet /mnt/skannet cifs username=bjorn,passwd=xx,uid=bjorn,gid=users 0 0
//nas1/familiefoto /mnt/familiefoto cifs username=guest,password=,uid=bjorn,gid=users 0 0
##/proc proc defaults 0 0

#2

On Wed, 09 Nov 2011 21:46:03 +0000, bkv1 wrote:

> I have had this setp for a while, bt today it says that cifs is not
> supported.
> Any idea what this can be?

Do you have cifs-utils installed on the client system?

What SAMBA components are installed on the client system?

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

#3

On 11/09/2011 10:46 PM, bkv1 wrote:
> Any idea what this can be?

what operating system and version you are running?

and, is it 32 or 64 bit?

and, is it fully updated?

was there an update applied just before this “suddenly does not work”?

some those questions are answered by showing us the terminal
input/output from


uname -a
cat /etc/SuSE-release
rpm -qa | tail

–
DD
openSUSE®, the “German Automobiles” of operating systems

#4

Yes, there was an update made just before. It is all right now. Sorry, I “panicked” a little.

#5

On Thu, 10 Nov 2011 18:06:02 +0000, bkv1 wrote:

> Yes, there was an update made just before. It is all right now. Sorry, I
> “panicked” a little.

For future people who may find this thread when they have a similar
issue, what was the fix?

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

#6

Yes. it is fixed. I did nothing. It worked after the first reboot.

#7

On 11/10/2011 07:36 PM, bkv1 wrote:
>
> Yes. it is fixed. I did nothing. It worked after the first reboot.

ah…i guess 64 bit, and the “recent update” was a new 64 bit
kernel…and the YaST instructions with a new kernel is always to reboot
as soon as possible after the update…

and, when the instructions were followed, the ‘fix’ just
happened…(which is why i asked the 32 v 64 question–i know 32 didn’t
have a kernel update lately)

–
DD
openSUSE®, the “German Automobiles” of operating systems

#8

On Thu, 10 Nov 2011 18:36:04 +0000, bkv1 wrote:

> Yes. it is fixed. I did nothing. It worked after the first reboot.

Thanks for the follow-up. :slight_smile:

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C