KDE Linux: Editing fstab not possible

I work with a NAS where I store all my work documents. To ensure that I always have access to the three important folders, I have entered them in fstab. Example:
//ds-xxx/music /media/music cifs users,credentials=/home/xxxxx/.smbcredentials,uid=1000,gid=1000,vers=2.0,auto,rw 0 0
Since fstab cannot be edited in KDE Linux, I am now stuck. What other option works in KDE Linux?

fstab definately can be edited. I changed mine many times.

1 Like

Are you sure? Have you tested this in KDE Linux? I’ve done this in various distributions without any problems. I haven’t been able to do it in KDE Linux.

I”m in KDE Linux right now. Yes it can be edited. I just tested it to be certain. Just don’t use Kate. Use sudo nano.

1 Like

Thanks, l will check it.

Hi Jay,
You were right, thanks for the tip. Editing fstab worked.
But now I’m facing the next obstacle. Could it be that “cifs-utils” is not available in kde-linux or that cifs still needs to be specially configured (I was able to use the example I posted in various distros)? The following error is displayed when mounting:
sudo mount -a
[sudo] Password for marcel:
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Do you have any ideas?

cifs is obsolete. Can’t you use smb?

https://www.google.com/search?q=replace+cifs+with+smb&oq=replace+cifs+with+smb&gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIHCAEQIRigATIHCAIQIRigATIHCAMQIRigATIHCAQQIRifBTIHCAUQIRifBTIHCAYQIRifBTIHCAcQIRifBTIHCAgQIRifBTIHCAkQIRifBdIBCDg4MzhqMGo3qAIIsAIB8QXz7Juzwk7Z7Q&sourceid=chrome&ie=UTF-8#fpstate=ive&vld=cid:6858c75f,vid:xFl1gEVZZnM,st:23

1 Like

Thanks, that helps

Apropo: I entered the parameter vers=2 in the call. This forces SMB version 2. This means that the connection to the NAS already runs with SMB2. SMB is also enabled on the NAS. What else can I do?

In Windows

Locate SMB 1.0/CIFS File Sharing Support and ensure it is disabled to force usage of modern, secure SMBv2/v3, or enable it if specifically required for legacy device compatibility.

Use PowerShell Set-SmbServerConfiguration to configure supported protocols.

In Linux

When mounting a share, update the command to specify the SMB version to avoid falling back to CIFS/SMB1.
Example: mount -t cifs //server/share /mnt/folder -o vers=3.0,username=user.

If the NAS supports NFS (as Synology do) wouldn’t it be more natural to use that with a Linux client rather than SMB?

My use case is that I want all the apps I use to have access to the NAS (I always test use cases that make sense in everyday life). This includes the file explorer. That’s why I use the fstab entry described above on my work computer. This generates an error in kde-linux. I have reported this and it should be fixed.