Confusion with mounting NAS drive as cifs share using fstab

Support
1

Hi Folks,

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata
I have asked my cat nicely

OpenMandriva Lx version:
Lx 6.0 (Vanadium) Rock x86_64

Desktop environment (KDE, LXQT…):
KDE

Description of the issue (screenshots if relevant):
I’ve started this thread to ask for help correctly mounting my NAS drive for regular read/write access to mimic the way it works on my windows PC’s. I’ll have to apologise for a little confusion on my part here: I spent the best part of yesterday afternoon trying to get this to work with little success, but now that I’m ready to take screenshots for this thread, it seems to be just working?!

Everything I did yesterday seemed to result in repeatedly booting to a system with an unmounted drive and journalctl log errors something like “Mount process exited, code=exited, status=32/n/a”. If I would then enter the terminal command “sudo mount /media/____”, the drive would then mount and work correctly. This led me think that the issue was related to the network online status flag, hence the question I posted yesterday. When I reboot now, the NAS drive remains mounted correctly, so maybe the issue is already solved? What changed since yesterday - was it the symlinks after all? I’ll post the relevant info below, hopefully something useful can come from this discussion anyway.

Relevant informations (hardware involved, software version, logs or output…):

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=34C5-1F16                            /boot/efi      vfat    defaults,noatime 0 2
UUID=48a6f919-2da8-451f-98b5-de291ef2517c /              ext4    defaults,noatime,discard 0 1
UUID=9e10bcd2-b7e6-47c6-a46f-387b70baf7d6 /home          ext4    defaults,noatime,discard 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

#NAS drive added by me 24/8/2025:
//10.1.x.x/____-share  /media/____  cifs  cred=/root/.smbcred,dir_mode=0777,file_mode=0666,nounix,vers=3.0,nofail,_netdev,x-systemd.device  0 0


[____@____ ~]$ systemctl --type=service
  UNIT                                                                                      LOAD   ACTIVE SUB     DESCRIPTION             >
  accounts-daemon.service                                                                   loaded active running Accounts Service
  alsa-restore.service                                                                      loaded active exited  Save/Restore Sound Card >
  blk-availability.service                                                                  loaded active exited  Availability of block de>
  cups.service                                                                              loaded active running CUPS Scheduler
  dbus-broker.service                                                                       loaded active running D-Bus System Message Bus
  dracut-shutdown.service                                                                   loaded active exited  Restore /run/initramfs o>
  irqbalance.service                                                                        loaded active running irqbalance daemon
  kmod-static-nodes.service                                                                 loaded active exited  Create List of Static De>
  lvm2-monitor.service                                                                      loaded active exited  Monitoring of LVM2 mirro>
  NetworkManager-wait-online.service                                                        loaded active exited  Network Manager Wait Onl>
  NetworkManager.service                                                                    loaded active running Network Manager
  plymouth-quit-wait.service

Aug 31 19:08:31 ____ systemd[1]: Mounted home.mount - /home.
Aug 31 19:08:38 ____ systemd[1]: Mounting media-____.mount - /media/____...
Aug 31 19:08:38 ____ kernel: CIFS: Attempting to mount //10.1.x.x/____-share
Aug 31 19:08:38 ____ systemd[1]: Mounted media-____.mount - /media/____.

QNAP QTS SMB
QNAP QTS SMB1437×680 74.2 KB

QNAP QTS NFS
QNAP QTS NFS1092×577 48 KB

Browser Mount
Browser Mount704×432 32.7 KB

2

The way I understand it, is the NetworkManager.service provides the connection config and setup, while the wait-online is a list of things that should wait for a valid connection state before starting. The samba services should be on that list by default, or may have other targeting in the service that waits for a certain runlevel or condition before continuing. Naturally, the mounting proceduure probably depends on the filesystem type which may also indicate if it should mount after a specific state or trigger.

3

I’m hesitant to experiment with it any more - I don’t want to break it again now that it appears to be working. My theory is that - as per my question yesterday, I mentioned that manually starting and enabling NetworkManager.Service and NetworkManager-wait-online.service did not seem to fix my issue - maybe it could be that manually disabling and then re-enabling NetworkManager.service enacted the necessary change that created the target point / runlevel state that was previously being missed?
Once I have finished moving my remaining pc’s away from Windows 10, I can probably change the settings on my NAS to disable samba/cifs and enable NFS, and maybe then it could be easier to manage going forward. I’ve dabbled with various linux distros here and there going all the way back to Mandrake days, but this only the second time I’ve made a serious effort to transition my daily driver pc permanently. The last time I tried dual booting Linux Mint with Windows 7 I just wasn’t able to comprehend the concept of using the grub console to recover an unbootable system (for what it’s worth I had to conquer that beast in the process of installing this OMA system). Right now I don’t want to go tweaking and breaking things all over the place, I just want to establish a usable main system before setting up another system to experiment with later. I don’t think I have anything powerful enough to spin up VM’s at this point.

4

When you do get away from the Windows stuff and can drop the Samba share, you might want to try giving sshfs a try instead of NFS. I’ve had perfectly good luck and fast performance with sshfs. I’ve setup NFS shares many times in the past and they were always plagued with very significant performance problems (could well be what I did, but that was consistently my experience). Anyway, just a thought when you get there.

5

Thanks, I’ll definitely have to look into this. After persevering for years with the poor performance and lack of support from D-Link, the QTS system on my QNAP NAS still feels like a breath of fresh air. I’ve been really impressed by the responsiveness and comprehensive features of the QTS system that I almost feel like maybe they should release a general purpose OS. That being said, while it does support ssh out of the box, I’m not sure whether my current TS-233 is up to the task of using docker containers to support non-native sshfs functionality. Whenever I do get to the next upgrade, It will definitely be a higher-end QNAP unit, and once again my parents will inherit my current NAS. It’s high time they replace that natty old D-Link box they’re using now…