DietPi Drive Manager won't stay connected to CIFS share

Creating a bug report/issue

Required Information

  • DietPi version | G_DIETPI_VERSION_CORE=8

  • Distro version | bullseye 1

  • Kernel version | Linux PiHole 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux

  • Architecture | armhf

  • SBC model | RPi 4 Model B (aarch64)

  • Power supply used | 802.3at PoE+ switch with RPi PoE HAT

  • SD card used | Kingston M.2 SSD (booted through USB 3.0 port)

Additional Information (if applicable)

  • Software title | dietpi drive manager
  • Was the software title installed freshly or updated/migrated? Updated
  • Can this issue be replicated on a fresh installation of DietPi? Haven’t tried

Steps to reproduce

  1. Mount CIFS drive with dietpi drive manager
  2. Confirm drive is mounted, /etc/fstab entry looks ok
  3. Wait an hour or two for mounted network drive to disconnect spontaneously (but the samba share is otherwise available to other clients on network)
  4. Re-mount cifs share with Webmin, drive can’t be mounted with dietpi drive manager now
  5. Process repeats

Expected behaviour

CIFS share should stay connected

Actual behaviour

CIFS share disconnects after an hour or two, dietpi drive manager gives error that “host is down,” but as mentioned above, the shared folder remains active on network and other (Windows) clients can access it… Once remounted by another route like Webmin, the share stays connected temporarily again but the cycle repeats itself.

Extra details

Here is the etc/fstab entry created by dietpi drive manager:

//nucserver.xxxx/xxxshare /mnt/xxxxshare-SMB cifs uid=0,iocharset=utf8,cred=/var/lib/dietpi/dietpi-drive_manager/mnt-xxxxshare-SMB.cred,dir_mode=0770,file_mode=0770,vers=3.1.1,nofail,gid=0,x-systemd.automount,noauto 0 0

I doubt that the drive manager has any influence on this, as it does nothing other than create the /etc/fstab entry and mount it directly during execution. Even if you reboot, the drive manager is not involved.

If your system loses the connection or even the entire mount, it probably has other reasons. If a share is no longer available, it should normally remain mounted but inaccessible.

You could have a look to last entries within journalctl or kernel error messages dmesg -l 0,1,2,3

1 Like

I see you have accepted the solution. Would you like to share your findings on why your system lost the shares?

Sorry for my delayed reply. I wish I could give a more satisfying answer, but I rebooted the RPi and so far the network drive has remained connected. Appreciate the assistance nonetheless!