From owner-freebsd-hackers@FreeBSD.ORG Fri May 19 00:38:09 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7A1216A4A0 for ; Fri, 19 May 2006 00:38:09 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF22D43D4C for ; Fri, 19 May 2006 00:37:58 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002573829.msg for ; Fri, 19 May 2006 01:37:04 +0100 Message-ID: <008c01c67adc$590a2a30$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: Date: Fri, 19 May 2006 01:36:54 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Processed: multiplay.co.uk, Fri, 19 May 2006 01:37:04 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org X-MDAV-Processed: multiplay.co.uk, Fri, 19 May 2006 01:37:05 +0100 Subject: NFS server not responding prevents boot X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 May 2006 00:38:10 -0000 I was doing some kernel patches the other day and rebooted a FreeBSD 5.4 machine to pick them up, unfortunately I didn't notice someone had put in a bad nfs mount in /etc/fstab i.e. to a machine that no longer existed. This prevented the server coming back onto the network enough to fix the error ( sshd never started ). With the machine being remote I ended up having to send an engineer in to press CTRL + C on the keyboard to enable the machine to boot ( didn't know it would be that simple before he got there ). Anyway the big question is how can I change all our NFS mounts so that failed mounts dont prevent the machines booting to the point where they can be fixed remotely i.e. have started sshd. Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk.