Hiya,

Everything was fine until a couple of days ago, and i've had the same settings for at least a couple of years now. But now my drives don't map.

I'm using Nobara Linux (Fedora-based, doesn't use SELinux) for a while, and my drive mounts have been fine. But i think a recent update to Nobara 43, and perhaps coupled with unRAID to 7.2.2 (i only just updated to 7.x). I've been using the same fstab for a long time.

Here's a line from the fstab that has worked for years:

//192.168.1.10/Apps /mnt/NAS/Apps cifs username=derek,password=mysupersecretpassword,uid=nobody,gid=users,file_mode=0777,dir_mode=0777,nofail,noperm,vers=3.0,rw,noserverino,x-systemd.automount 0 0

I re-entered my password in unRAID 'users' tab, and then manually navigated via Dolphin > Network > SMB > NAS > Apps. I entered my username/password and it accepted it. Not only that, it accepted it for all the other visible shares (some shares are hidden). Any hidden share did not accept the credentials. Also, even though i could access "Photos" via the manual method described in this paragraph, i couldn't then navigate there via the terminal (/mnt/NAS/Photos).

In Dolphin, i get:

In Terminal, i get:

derek@Nobara-PC:/mnt/NAS$ cd Apps
bash: cd: Apps: No such device

So, i'm guessing something in the universe of Linux has changed? I did see someone mention that Nobara "now uses systemd mounting" but no more information than that. Perhaps the entry above is not properly compatible with systemd mounting methods?

I'm a confused monkey. I'd appreciate any assistance (even if it's just suggestions to improve the fstab entry regardless of fixing the issue).

Edited December 5, 2025Dec 5 by Derek_

Alrighty! So i think i might've had more than one issue. I was trying things for about 1.5 hrs before i posted, and about 1hr after - and by fluke or by brilliance, i think i've solved it.

• Updates for both Nobara and unRAID confused where the issue might lie

• I use OpenSnitch (something that blocks/allows stuff). OpenSnitch has not previously caused this issue, so at first i forgot about it. It appears it was a contributing factor.

• fstab was 'dated' and needed some tweaking.

It appears i needed a combination of:

1. Explicit OpenSnitch SMB "allow" rules; and

2. Updated fstab.

Here's my updated fstab:

//192.168.1.10/Apps /mnt/NAS/Apps cifs credentials=/home/derek/bits'n'bobs/smbcredentials,uid=1000,gid=1001,iocharset=utf8,noperm,vers=3.1.1,rw,noserverino,x-systemd.automount,x-systemd.idle-timeout=3600 0 0


The change that made the actual difference, i think, was replacing:

uid=nobody,gid=users,file_mode=0777,dir_mode=0777

With my desktop user's id numbers:

uid=1000,gid=1001

But that alone didn't work. I found that communication worked if i disabled OpenSnitch (but this didn't work before i updated fstab). So i created explicit rules to allow SMB (this wasn't needed pre-updates).

Edited December 5, 2025Dec 5 by Derek_

Update: i suspect my fstabbing had nothing at all to do with it. It's something to do with OpenSnitch's settings. I've had to disable OpenSnitch - at least temporarily to establish the connection. Whereupon i can re-enable it. I think it's time to replace my desktop, it's gotten glitchy... too much fiddling on my part.

Edited February 7Feb 7 by Derek_