From owner-freebsd-questions@FreeBSD.ORG Fri Mar 14 19:29:39 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 236AE106566C for ; Fri, 14 Mar 2008 19:29:39 +0000 (UTC) (envelope-from DWassman@etgroup.net) Received: from mail3.etgroup.net (mail3.etgroup.net [66.195.99.250]) by mx1.freebsd.org (Postfix) with ESMTP id F054F8FC1F for ; Fri, 14 Mar 2008 19:29:38 +0000 (UTC) (envelope-from DWassman@etgroup.net) Received: from mail2.etgroup.net (66.195.99.231) by etg6.etg.local (66.195.99.250) with Microsoft SMTP Server id 8.1.240.5; Fri, 14 Mar 2008 14:29:38 -0500 Received: from mail.etgroup.net ([66.195.99.210]) by mail2.etgroup.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 14 Mar 2008 14:29:38 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 14 Mar 2008 14:30:39 -0500 Message-ID: <4EFE19E52F4F844D997F24D759C4A23B038755C3@etg2.etg.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: thread-topic: RE: interactive stop on boot thread-index: AciF9b6uzbUZ32ozQM+kZAFpg5MJLgAEvFPA From: David Wassman To: X-OriginalArrivalTime: 14 Mar 2008 19:29:38.0560 (UTC) FILETIME=[BE4CF000:01C88609] Cc: freebsd-questions@freebsd.org Subject: RE: interactive stop on boot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2008 19:29:39 -0000 Jason, If there isn't anything needed from the NFS mounts, you can add intr,soft options to the /etc/fstab for each NFS share. Intr allows you to interrupt the NFS process with CTRL-C. You may not be available to do this, but you could call a user to do it. Soft allows the NFS client to fail, instead of hang.=20 Or you could just delete the entries or have them noauto. Also, verify that the dump and pass# are set to zero. At least pass#, as if it is any other number, the background fschk will try to run and hang if not available (not ideal to run fschk on NFS mounts anyway) Hope this helps. David Wassman Message: 13 Date: Fri, 14 Mar 2008 08:24:57 -0700 From: "Jason Barnes" Subject: interactive stop on boot To: questions@freebsd.org Message-ID: Content-Type: text/plain; charset=3DISO-8859-1 Hi -- I'm running a "Tombstone" machine that's functioning as a server. The machine is located somewhere with a fast connection, and not somewhere that I have easy access to. As such, I want this machine to do its best to boot up and get onto the network, no matter what happens on boot, so that I have a chance to actually fix the problem. Lately when it boots it runs into an NFS mounting error, claiming that some of my NFS-mounted drives have unexpected inconsistencies. It says "unexpected error - help!" and then quits to a /bin/sh single-user-mode prompt. As I am 10 miles away, this is decidedly unhelpful. I don't care if it can't mount some irrelevant drive or not; I want it to boot up and ask me questions later. Is there a way that I can set the machine to do its best to boot no matter what it finds at boot time? Thanks in advance for any help you can provide, - Jason PS -- Boot messages not available, as the machine is down at the moment and I can't get over there to type " exit" until later this afternoon.