From owner-freebsd-stable@FreeBSD.ORG  Wed Oct 29 13:05:03 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 08E26AE3
 for <freebsd-stable@freebsd.org>; Wed, 29 Oct 2014 13:05:03 +0000 (UTC)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com
 [IPv6:2a00:1450:4010:c04::236])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 881C06E2
 for <freebsd-stable@freebsd.org>; Wed, 29 Oct 2014 13:05:02 +0000 (UTC)
Received: by mail-lb0-f182.google.com with SMTP id f15so2677313lbj.27
 for <freebsd-stable@freebsd.org>; Wed, 29 Oct 2014 06:05:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=DaT95CaYDKXzT4UuFpPxHlnweHuujNqqwbDKquX7Ueg=;
 b=JIyWKkQa0fmMMKZVAslBVii5SDYkZr84Izf47GGiVp6GqqmhhhqmIMS/YunnzyiGvh
 BK+qxuznxy1bXBV2DD6bN2TQWgNTmtFzaMBthhQ9t+xb9KnPqHYpgB264nrNnpid23P2
 rsLjLFjUIu5F142OYkkMvoR7HtWXp1ZhbXwtRNmLRuyAsCfvFotOikqwc9pn/cBZNMCb
 OQFSdbXRjRnLyS7ghfTzFrcxj10ksZAd1nwN6H5/Fd+YbOa53CrUj9llyreehphzQhMn
 cFBq5S8o+V6rN+XrDtjKAB3VhEK0zypVX7Mufd3BzyZhLtopYMuPitzk8biRB1tC/ISw
 EvEw==
MIME-Version: 1.0
X-Received: by 10.112.36.197 with SMTP id s5mr11467704lbj.30.1414587900310;
 Wed, 29 Oct 2014 06:05:00 -0700 (PDT)
Received: by 10.152.210.197 with HTTP; Wed, 29 Oct 2014 06:05:00 -0700 (PDT)
Date: Wed, 29 Oct 2014 14:05:00 +0100
Message-ID: <CAF-3MvMTXphsXpuQqGnwtHM_3WXSeJCWJfUNttxphuYXFmKeBA@mail.gmail.com>
Subject: 10.1RC1 armv6 RPI-B stuck in single user mode
From: Alban Hertroys <haramrae@gmail.com>
To: freebsd-stable <freebsd-stable@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Oct 2014 13:05:03 -0000

We have a Raspberry Pi here that was working fine, but because my
colleagues tend to reboot the thing by unplugging the power, the root
file-system got dirty.
To fsck the root file-system, I attempted to boot it into single-user
mode using nextboot -o "-s" -k kernel.

Unfortunately, it never shows the single user mode prompt. The system
gets stuck trying to mount root from ufs:/dev/mmcsd0s2a

And it does that every time I attempt to boot it, because that
nextboot flag never gets cleared!
There doesn't appear to be any method of interrupting the boot loader
on the Pi either.

How do I get out of this pickle?
-- 
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.