From owner-freebsd-questions@FreeBSD.ORG Wed Aug 17 18:22:21 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 230DF16A41F for ; Wed, 17 Aug 2005 18:22:21 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBC7D43D48 for ; Wed, 17 Aug 2005 18:22:20 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 6901 invoked from network); 17 Aug 2005 18:22:20 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail23.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 17 Aug 2005 18:22:19 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id F1BFE36; Wed, 17 Aug 2005 14:22:18 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Brian Clark References: <20050817012145.7e1fcb5a@bc.oamnet.com> From: Lowell Gilbert Date: 17 Aug 2005 14:22:18 -0400 In-Reply-To: <20050817012145.7e1fcb5a@bc.oamnet.com> Message-ID: <44k6ikpgo5.fsf@be-well.ilk.org> Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: fstab and bad hard drives 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: Wed, 17 Aug 2005 18:22:21 -0000 Brian Clark writes: > I searched and looked through the man pages and was unable to find > any information on this. My question is, is there a way to make > freebsd boot if it has problems mounting a hard drive listed in > fstab? With NFS drives I use 'bg' so the system will continue to > boot if the NFS drive is down or unavailable. I would prefer if a > hard drive on the system was to stop working that the system would > still boot and not hang in single user mode. This is for remote > servers that are about 2 hours away and have had several instances > where an extra drive on the system failed which caused the system to > not reboot correctly... so then i have to drive down manually edit > the fstab, (remove the entry) reboot and all is fine. In an ideal > world, if the system reboots and an extra drive fails to mount then > the system skips it and continues to load without the bad drive. Any > ideas? I was considering noauto and have an rc.d script mount them > but not for sure if it would still hang the system. That last is the approach I would have suggested...