From owner-freebsd-questions@FreeBSD.ORG Sat Apr 25 17:55:55 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 51945274 for ; Sat, 25 Apr 2015 17:55:55 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 146D91952 for ; Sat, 25 Apr 2015 17:55:54 +0000 (UTC) Received: from r56.edvax.de (port-92-195-64-237.dynamic.qsc.de [92.195.64.237]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 090883CD1F; Sat, 25 Apr 2015 19:55:44 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id t3PHtiiq004636; Sat, 25 Apr 2015 19:55:44 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sat, 25 Apr 2015 19:55:44 +0200 From: Polytropon To: Robert Fitzpatrick Cc: FreeBSD Subject: Re: System won't boot after loss of power Message-Id: <20150425195544.c9b2cf17.freebsd@edvax.de> In-Reply-To: <553BB8BD.8060400@webtent.org> References: <553BB8BD.8060400@webtent.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Apr 2015 17:55:55 -0000 On Sat, 25 Apr 2015 11:54:37 -0400, Robert Fitzpatrick wrote: > I can use Live CD and make changes to the /etc/fstab to use the slices > of one pair of drives and chroot to the existing system without gmirror > and read all the data from all the partitions. This works for all drives > updating fstab for each pair of drives. > > No matter how I update the fstab file, I just get a blinking cursor > without reaching the FreeBSD boot manager at all. How can I diagnose > further or restore the boot process? The boot manager has nothing to do with /etc/fstab, which "happens much later". If you encounter a problem at an early booting stage, the reason is to be searched for there. Maybe... is the boot manager damaged or absent? Check the partition properties with gpart. In worst case, re-install the boot manager (with gpart or bsdlabel, depending on how you have partitioned your drives). Are you sure the system is trying to boot from the correct drive? Can you interrupt at the boot prompt or the loader prompt, or don't you even reach those? If you can, verify that the correct root device is being configured. Also, just in case, check if there's something strage regarding the boot order in your BIOS / UEFI. Everything else at this poing is just WAG... :-( -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...