From owner-freebsd-questions@FreeBSD.ORG  Thu Jul 10 00:06:04 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E7CFDA40
 for <freebsd-questions@freebsd.org>; Thu, 10 Jul 2014 00:06:04 +0000 (UTC)
Received: from alogt.com (alogt.com [69.36.191.58])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8B5F929A5
 for <freebsd-questions@freebsd.org>; Thu, 10 Jul 2014 00:06:04 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com;
 s=default; 
 h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:To:From:Date;
 bh=jR6YxaaKzAikdFXq+bsdFgBJNU1XVTBiJWjKHd+t2OU=; 
 b=Cw1fzU+B3jQ0V3RchKqjaZl7aqnU9yoJg70WZjWYjcjpokAu8/NNzobjfUraCc3BVVkCCyaZzJ+4tTJMXDo2P2dg2ZvuLC19+iuytDvqZeM7uwu3nZnQj8jZxWXBLp7e8wRhpt/aiX0DmXxNQ2KSh9WEfm645qVh2UNmfCtfApg=;
Received: from [182.0.177.130] (port=54576 helo=X220.alogt.com)
 by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128)
 (Exim 4.82) (envelope-from <erich@alogt.com>) id 1X51s5-000KM7-Gq
 for freebsd-questions@freebsd.org; Wed, 09 Jul 2014 18:05:58 -0600
Date: Thu, 10 Jul 2014 08:05:51 +0800
From: Erich Dollansky <erich@alogt.com>
To: gahn via freebsd-questions <freebsd-questions@freebsd.org>
Subject: Re: boot section corruption
Message-ID: <20140710080551.0365d976@X220.alogt.com>
In-Reply-To: <1404921524.5512.YahooMailNeo@web122303.mail.ne1.yahoo.com>
References: <1404921524.5512.YahooMailNeo@web122303.mail.ne1.yahoo.com>
Organization: ALO Green Technologies
X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.0)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-AntiAbuse: This header was added to track abuse,
 please include it with any abuse report
X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net
X-AntiAbuse: Original Domain - freebsd.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - alogt.com
X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id:
 erich@alogt.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jul 2014 00:06:05 -0000

Hi,

On Wed, 9 Jul 2014 08:58:44 -0700
gahn via freebsd-questions <freebsd-questions@freebsd.org> wrote:

> i got puzzled when sometime the freebsd either failed to=A0 mount a
> slice, gets into mountroot> prompt or even worse, corrupted the whole
> boot section and gets into db> mode.besides the recovery procedures,
> i am more interested in knowing how those scenarios might happen and
> what we can do to prevent them to happen.
>=20
this happens main for two reasons. When starting from a USB device and
the device is too slow to react in time or when you have a serious
hardware problem.

What should FreeBSD do in these cases?

Erich