From owner-freebsd-questions@FreeBSD.ORG Sun Feb 17 19:44:05 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 1FBCF16A41A for ; Sun, 17 Feb 2008 19:44:05 +0000 (UTC) (envelope-from jonathan+freebsd-questions@hst.org.za) Received: from hermes.hst.org.za (onix.hst.org.za [209.203.2.133]) by mx1.freebsd.org (Postfix) with ESMTP id 3CE0E13C45E for ; Sun, 17 Feb 2008 19:44:02 +0000 (UTC) (envelope-from jonathan+freebsd-questions@hst.org.za) Received: from [10.1.11.1] ([10.1.11.1]) (authenticated bits=0) by hermes.hst.org.za (8.13.8/8.13.8) with ESMTP id m1HJa931003059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 17 Feb 2008 21:36:10 +0200 (SAST) (envelope-from jonathan+freebsd-questions@hst.org.za) From: Jonathan McKeown To: freebsd-questions@freebsd.org Date: Sun, 17 Feb 2008 21:44:36 +0200 User-Agent: KMail/1.9.4 X-Face: $@VrUx^RHy/}yu]jKf/<4T%/d|F+$j-Ol2"2J$q+%OK1]&/G_S9(HkaQ*`!?YOK?Y!'M`C aP\9nVPF8Q}CilHH8l; ~!42HK6'3lg4J}az@1Dqqh:J]M^"YPn*2IWrZON$1+G?oX3@k#0 54XDRg=Yn_F-etwot4U$bdTS{i X-Spam-Score: -4.362 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.61 on 209.203.2.133 Subject: fdisk from fixit CD: geom not found 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: Sun, 17 Feb 2008 19:44:05 -0000 As part of our disaster recovery planning, I'm working up a bare-metal recovery sequence that can be followed by someone who's used Linux (easier to find here than a FreeBSD admin). My initial outline sequence was along the lines of: Boot install CD and choose Fixit fdisk -BI extract saved disklabel from tape and install with bsdlabel Initialise filesystems using stored output of dumpfs -m (from tape) Restore filesystems from tape I'm tripping up on the first step, which although it appears to create the slice, throws a ``Geom not found'' message - which is potentially worrying to someone blindly following a recovery script. Is there a way to avoid this message, or would I be better off using the Configure option of sysinstall (and the W option to write the new slice table) before switching to Fixit mode to recover the disklabel (which is the next bit I need to test ``under lab conditions'')? Jonathan