User avatar
billybangleballs
Posts: 148
Joined: Fri May 18, 2012 11:28 pm

What causes this?

Sun May 20, 2018 2:26 pm

I have a windows box with 2 drives, both are shared and are mounted at boot by the raspberry pi.
Both are instantly accessible all the time, never a delay or a pause when trying to read or write to either of them, but my log is full of the following.

Code: Select all

May 20 13:42:04 raspberrypi kernel: [43535.598765] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:42:04 raspberrypi kernel: [43535.599036] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:44:11 raspberrypi kernel: [43662.319927] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:44:11 raspberrypi kernel: [43662.320108] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:46:18 raspberrypi kernel: [43789.041242] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:46:18 raspberrypi kernel: [43789.041460] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:48:25 raspberrypi kernel: [43915.762373] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:48:25 raspberrypi kernel: [43915.762639] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:50:31 raspberrypi kernel: [44042.483564] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:50:44 raspberrypi kernel: [44055.283648] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:52:38 raspberrypi kernel: [44169.204718] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:52:51 raspberrypi kernel: [44182.004835] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:54:45 raspberrypi kernel: [44295.925880] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:54:57 raspberrypi kernel: [44308.726015] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:56:51 raspberrypi kernel: [44422.647122] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:58:44 raspberrypi kernel: [44535.288120] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 13:58:58 raspberrypi kernel: [44549.368240] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 14:00:51 raspberrypi kernel: [44662.009299] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 14:01:05 raspberrypi kernel: [44676.089428] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 14:04:37 raspberrypi kernel: [44888.571673] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 14:05:37 raspberrypi kernel: [44948.732219] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
May 20 14:06:44 raspberrypi kernel: [45015.292528] CIFS VFS: Server 192.168.0.1 has not responded in 120 seconds. Reconnecting...
What is the windows box not responding to? Nothing seems amiss from an operational standpoint, but it would be nice to know why my logs are filling up with these messages.

I'm running a 3B with Raspbian GNU/Linux 9 \n \l and kernel 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l GNU/Linux
Grumpy old man.
Ex-G0KAP - I'd rather be doing it than talking about it.
"When found, make a note of." - Captain Cuttle

User avatar
billybangleballs
Posts: 148
Joined: Fri May 18, 2012 11:28 pm

Re: What causes this?

Mon May 21, 2018 7:45 am

I changed the cat5 patch lead from a blue one to a red one, but it made no difference.
Grumpy old man.
Ex-G0KAP - I'd rather be doing it than talking about it.
"When found, make a note of." - Captain Cuttle

User avatar
billybangleballs
Posts: 148
Joined: Fri May 18, 2012 11:28 pm

Re: What causes this?

Sun May 19, 2019 4:52 pm

I found a cure, just add

Code: Select all

* * * * * /usr/bin/touch /mnt/win/pi
to your crontab, and no more log spamming occurs.
It creates/recreates a 0 byte file on the windows share every minute and prevents the timeout.
Grumpy old man.
Ex-G0KAP - I'd rather be doing it than talking about it.
"When found, make a note of." - Captain Cuttle

Return to “General discussion”