Re: sporadic successfull mount of nfs with Stretch

2019-05-29 Thread Nicholas Geovanis
On Tue, May 28, 2019, 5:06 AM Stefan K wrote: > I solved this issue by installing the latest backport kernel > So my question would be, did logs indicate that Ethernet autonegotiation failed with the new-old-bad drivers, but succeed with the backport level? >

Re: sporadic successfull mount of nfs with Stretch

2019-05-29 Thread Keith Bainbridge
On 28/5/19 8:05 pm, Stefan K wrote: I solved this issue by installing the latest backport kernel Stefan Well done -- Keith Bainbridge ke1th3...@gmail.com +61 (0)447 667 468

Re: sporadic successfull mount of nfs with Stretch

2019-05-28 Thread Stefan K
I solved this issue by installing the latest backport kernel On Sunday, May 26, 2019 7:57:50 PM CEST deloptes wrote: > Stefan K wrote: > > > I also try to use _netdev as mountoptions, but it didn't work. > > Has anyone an idea how to solve this? > > I use defaults,retry=5,_netdev - never had an

Re: sporadic successfull mount of nfs with Stretch

2019-05-26 Thread Nicholas Geovanis
Following on Keith's suggestion: If replacing the hostname with the IP address doesn't help, look at the error rates on the network interfaces. Especially look for speed mismatches in the Ethernet config at the 2 ends. On Sat, May 25, 2019, 7:48 PM Keith Bainbridge wrote: > On 23/5/19 12:36 am,

Re: sporadic successfull mount of nfs with Stretch

2019-05-26 Thread deloptes
Stefan K wrote: > I also try to use _netdev as mountoptions, but it didn't work. > Has anyone an idea how to solve this? I use defaults,retry=5,_netdev - never had an issue with this. I must admin I still use init and not systemd. But when testing with systemd I do not recall having problem. I th

Re: sporadic successfull mount of nfs with Stretch

2019-05-25 Thread Keith Bainbridge
On 23/5/19 12:36 am, Stefan K wrote: Hello, we've some problems with Debian stretch which try to mount nfs4 shares at boot-time, sometimes it works and sometimes not. If its not mounting during start I can mount it after I login without problems. A successfull (re)boot look like [1] and a (re