Re: [LUG] Merry Christmas All.. automount problem with kernel 41.3 on Mint 18.3

To: list@xxxxxxxxxxxxx

Subject: Re: [LUG] Merry Christmas All.. automount problem with kernel 41.3 on Mint 18.3

From: Simon Avery <digdilem@xxxxxxxxx>

Date: Mon, 25 Dec 2017 12:39:34 +0000

Authentication-results: mx.messagelabs.com; spf=pass (server-10.tower-188.messagelabs.com: domain of dclug.org.uk designates 85.158.139.163 as permitted sender)smtp.mailfrom=dclug.org.uk

Delivered-to: dclug@xxxxxxxxxxxxxxxxxxxxx

Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dclug.org.uk; s=1507453562; h=Sender:Content-Type:Reply-To:List-Subscribe:List-Help:List-Post:List-Unsubscribe:List-Id:Subject:To:Message-ID:Date:From:References:In-Reply-To:MIME-Version; bh=YfE5hhexoqAoiXEh1Do9kjZoMeMLhX5xjdH1zTZKBAs=; b=gseue3l8UUrDRV9akY+OA37lOJEBH3ewVMshrc5sZbTmzU1eWKIgzpz+DAwPAiUg1ynlu4rA7vIV7yS6M5i2oPLqUYUKRFNHcQYf0tyk50WLXohrPtL9Y+t6iCyETXkYEtuzQ0rPVGc4ni/TKHuu4ADejrXZOtDLgUyR1g+wSoY=;

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=IuK0FxDZwtQi7AABjxgC7CoPxMHsHQB1+ihv6spSRU4=; b=cDjOrmlPT/TtC3DSAGP64KlzdqyEv50kbWOie6FzvFFQkm3PadFJFG4uthahnU+7Qh Jds53nYtYaFzGZ/K3HRHC+4iRRR8mspAqmnO0OYUBM1FXy5XQ3ORXrhGM986cqmrc/2j /tJHSQzhq6VZeWlNZL2bvoRakCAyPFNgsarCFX45zFQJkH5KY01eE/uRlb/0NNyWL39h gwQkkDKQfAY3zz4Olb1M9KaVtcv7dkYAhEIEEOMAmTOSuYYx/+14zOnaBh5mTukhKkw4 /aaK1U5nK7ptyyMd/W/1kf0dDbsue2nPEf36argnllq4S/hrw3jpyXiookF7aAe1zSK5 bFww==

On 24 December 2017 at 16:34, Julian HallÂ<linux@xxxxxxxxxxxx>Âwrote:

Thanks Simon.
This is the dmesg output before and after manually mounting the shares; as you can see there is no change. I assume I need to look in a different log? It looks as though the network isÂ up which is one issue the forums suggested; if it wasn't I wouldn't get any network activity and I do.

Nope, can't see anything relevant in that dmesg segment (apart from it not liking your TV card but that's not relevant).

What about syslog when you repeat it?

Another method is to "ls -lt |more" (Lists most recently updated files) in /var/log just after trying to mount,Âto see if any other log files are being updated with useful info. Those at the top of the list have been touched more recently.

Or "tail -f /var/log/syslog" in one terminal window whilst you perform the command in another. (Tails the log live, ctrl+c to break out of it)

mr meowski has a good suggestion about trying the older kernel too, but I'd be surprised if NFS support had changed significantly during a kernel upgrade. It is possible though, or something is conflicting, and a useful bug-tracing exercise.