CIFS VFS: Server has not responded in 120 seconds

[Roberto]

Hi everybody,

I'm a new MX Linux user and I'm new here in the forum.

I have a Raspberry Pi as a NAS server with Openmediavault as NAS software. I have mounted the NAS via smb / cifs and the following entry in the fstab:

Code: Select all

//ip-adress/Daten /media/Datenpool cifs     defaults,credentials=/home/user/.smbcredentials,rw,nounix,iocharset=utf8,vers=1.0,uid=user,gid=user 0 0

Everything works finde and I have full access to all my documents.
Unfortunately, the shutdown hangs with the following message:

Code: Select all

Stopping enhanced syslogd: rsyslogd
[ 1757.153231]CIFS VFS: Server (ip-adress) has not responded in 120 seconds. Reconnecting...

When I umount my NAS manually and shutdown my notebook afterwords, there is no delay.
When I use a different notebook with Artix Linux and OpenRc, the shutdown works smoothly.
Does anyone have an idea what I'm doing wrong or what I have to do so that my computer shut down quickly?

Thanks to all for your ideas and help.
Roberto

[timkb4cq]

It appears that your network is shutting down before your share is unmounted.
A search brought up an Ubuntu thread that indicates this will happen if the All users may connect to this network box in Network manager is unchecked.
That box is found thus: Right click on the Network icon in the panel -> Edit Connections -> Select your connection -> Edit -> General (tab)
With any luck, checking the box will solve the problem.

Update: Mounting a cifs share, and unchecking that box causes the same 120 second shutdown delay on my machine. With the box checked, shutdown is normal.

[Roberto]

Hi timkb4cq,

the checkbox "all users may connect to this network" was checked an and I tried both, checking an unchecking it, but every time I have the 120 seconds delay.
What value is important for "Connection-priority for auto-activation"? My default in the wifi connection is "0".

Roberto

[Roberto]

Has nobody an idea to solve my problem?

[fehlix]

Has nobody an idea to solve my problem?

Why not mounting/unmounting with one click manually e.g through filemanager?
Mounting smb's through fstab is kown to become potentially troublesome,
as you make boot and shutdown dependent from network-connectivity
causing timeouts during boot or shutdown.
I've seen lot's of tweaks and workaround to handle this. But why bother,
if it's just for your documents etc a simpler approach
would be by one-click manual connect/disconnect, imho.

[Roberto]

Many times, I tried to mount/umount through the filemanager, but every time I try to do it, I don't get full access to my raspberry.
I always get the message, that the owner is root and that I can't edit a file and can't create a new file.
If anybody has a solution for this problem, using the filemanager would be the way to use my raspberry.

[Roberto]

I was hoping that the update to MX-19 would solve my problem, but unfortunately this is not the case.
I have no problem to mount and unmount my Raspberry Pi via the file manager.
Unfortunately the drive is always assigned to the root and I don't have all rights as a user.
Therefore I still have to use the fstab to mount and unmount my Raspberry Pi.
How can I change the owner from root to my user via the file manager?

[cas1701]

Hi there, I'm new to MX Linux having moved over from Mint, but I'm also a relatively new user to Linux as well having come from Windows. So I'm very much learning as I go, and if anyone has an answer to this I would appreciate explanations in words of one syllable please (Numpty speak!).

I have a very similar problem to the one described here and rather than starting up a whole new thread I thought I would re-use this one.

Firstly I have installed MX21_x64 ahs onto my system and has been fully updated/upgraded. This is my system as it stands at this time:

Code: Select all

System:    Kernel: 5.16.0-5mx-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.16.0-5mx-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 dm: LightDM 1.26.0 
           Distro: MX-21_ahs_x64 Wildflower November 22  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: NOVATECH product: MBB-99K16D v: V1.0 serial: <filter> Chassis: type: 3 v: 1.0 
           serial: <filter> 
           Mobo: Gigabyte model: Z390 AORUS PRO-CF v: x.x serial: <filter> UEFI-[Legacy]: American Megatrends v: F11 
           date: 10/15/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3 serial: <filter> 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Info: 8-Core model: Intel Core i9-9900K bits: 64 type: MT MCP arch: Kaby Lake note: check family: 6 
           model-id: 9E (158) stepping: D (13) microcode: EC cache: L2: 16 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 115200 
           Speed: 800 MHz min/max: 800/5000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
           9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds mitigation: TSX disabled 
           Type: tsx_async_abort mitigation: TSX disabled 
Graphics:  Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: Micro-Star MSI driver: nvidia v: 510.47.03 bus-ID: 01:00.0 
           chip-ID: 10de:1e84 class-ID: 0300 
           Display: x11 server: X.Org 1.20.13 compositor: xfwm4 v: 4.16.1 driver: loaded: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") s-diag: 777mm (30.6") 
           Monitor-1: HDMI-0 res: 2560x1440 hz: 60 dpi: 109 size: 598x336mm (23.5x13.2") diag: 686mm (27") 
           OpenGL: renderer: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 510.47.03 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel v: kernel 
           alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403 
           Device-2: NVIDIA TU104 HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
           chip-ID: 10de:10f8 class-ID: 0403 
           Sound Server-1: ALSA v: k5.16.0-5mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel port: efa0 bus-ID: 00:1f.6 
           chip-ID: 8086:15bc class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-2: Realtek RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter type: USB driver: rtl88XXau bus-ID: 1-5:2 
           chip-ID: 0bda:8812 class-ID: 0000 serial: <filter> 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8 bus-ID: 1-11.1:8 
           chip-ID: 0a12:0001 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 sub-v: 22bb hci-v: 4.0 
           rev: 22bb 
           Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 9.12 TiB used: 93.55 GiB (1.0%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 1TB size: 931.51 GiB block-size: physical: 512 B 
           logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: MBR 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 QVO 4TB size: 3.64 TiB block-size: physical: 512 B 
           logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: GPT 
           ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 QVO 4TB size: 3.64 TiB block-size: physical: 512 B 
           logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: GPT 
           ID-4: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 860 PRO 1TB size: 953.87 GiB block-size: physical: 512 B 
           logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: GPT 
Partition: ID-1: / raw-size: 923 GiB size: 907.44 GiB (98.31%) used: 12.07 GiB (1.3%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 
           ID-2: /home raw-size: 3.64 TiB size: 3.58 TiB (98.40%) used: 81.48 GiB (2.2%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3 maj-min: 8:3 
Sensors:   System Temperatures: cpu: 29.0 C mobo: N/A gpu: nvidia temp: 30 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 24% 
Repos:     Packages: 2496 note: see --pkg apt: 2488 lib: 1403 flatpak: 8 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/1password.list 
           1: deb [arch=amd64 signed-by=/usr/share/keyrings/1password-archive-keyring.gpg] https://downloads.1password.com/linux/debian/amd64 stable main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
           2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye ahs
Info:      Processes: 358 Uptime: 57m wakeups: 13 Memory: 31.29 GiB used: 3.47 GiB (11.1%) Init: SysVinit v: 2.96 runlevel: 5 
           default: 5 tool: systemctl Compilers: gcc: 10.2.1 alt: 10 Shell: Bash v: 5.1.4 
           running-in: quick-system-info-mx inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

I'm using the WiFi connection (Network Device 2).

To describe my problem, I've also edited my fstab file to mount my network shares on startup. I used a thread on the Linux Mint fora to insert the lines I needed to get this to work. The thread I used was this one, https://forums.linuxmint.com/viewtopic. ... 2&t=222087, which I followed it to the letter and it worked like a charm. There were no restart or shutdown sequence issues.

Once I moved over to MX Linux, I again edited my fstab file in the same way in the belief that the same would occur, so I inserted the lines into my fstab file as you can see below:

Code: Select all

# Pluggable devices are handled by uDev, they are not in fstab
UUID=8bbb2c7c-fc62-44d0-904a-1af858e1ae7f / ext4 noatime 1 1
UUID=d430deb8-7dd2-4e70-8c2b-d73148c41101 /home ext4 noatime 1 2
UUID=c9518406-b56b-406d-a5b8-0067549ae663 swap swap noatime 1 2
//192.168.1.95/Media /media/Media cifs username=xxx,password=xxxxxxxxx,nounix,auto,user,uid=1000 0 0
//192.168.1.95/Users /media/Users cifs username=xxx,password=xxxxxxxxx,nounix,auto,user,uid=1000 0 0

So, on startup the shares are immediately available to me and I can access/alter any files on them as I wish.

However, when I either restart or shutdown then the sequence takes about three minutes to complete. During the restart/shutdown I get a screen which says

Restarting System...

This stays on screen for about 3 minutes then this appears

[ 225.818822] CIFS: VFS \\192.169.1.95 has not responded in 180 seconds. Reconnecting...
[ 228.038535] reboot: Restarting system

and then system then restarts. I had to video it to see what it said.

I tried changing the auto entry to noauto as suggested on one of the other boards on here but that didn't work. The restart took just as long.
I also tried unchecking/checking the All users may connect to this network in Advanced Network Configuration as suggested by someone else here but that didn't work either.

I've looked at and tried many and varied suggested solutions to this and so far nothing has allowed a restart/shutdown sequence to complete without the dreaded 3 minute delay unless I manually unmount both network shares beforehand, but I have to open a root Thunar window to do this as it won't let me use a normal window as it says that a superuser is required (this was also another problem someone else here had).

Am I missing something here? Or is there another entirely different way of attaching network shares to my system in the same or similar way to mapping a network drive in Windows?

Any help would be greatly appreciated.

[CharlesV]

As felix said, connecting to the share at the fstab point is a problem.

I have two NAS devices on my system and I connect using a script at login. This has resolved any issue of slow startup or hangs at shutdown.

[fehlix]

As felix said, connecting to the share at the fstab point is a problem.

I have two NAS devices on my system and I connect using a script at login. This has resolved any issue of slow startup or hangs at shutdown.

Don't understand why people still try to mount network resources through fstab.

Just one line within user'S autostart like

Code: Select all

gio mount smb://server.name/

woudl do.
You just would connect once manuaally e.g. with
Thunar to open the uri

smb://server.name/
or even with username
smb://username@server.name/path/

and make sure it is saving connection into the gnome-keyring by clicking on save and remember permanently.
and use the identical uri above, so it would find after login
the credentials from gnome-keyring to connect.