From owner-freebsd-stable@FreeBSD.ORG  Wed Oct 29 13:09:08 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@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 6F244C9C
 for <freebsd-stable@freebsd.org>; Wed, 29 Oct 2014 13:09:08 +0000 (UTC)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (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 2FAB077F
 for <freebsd-stable@freebsd.org>; Wed, 29 Oct 2014 13:09:08 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1XjSzq-000Bgt-7n; Wed, 29 Oct 2014 14:09:06 +0100
Date: Wed, 29 Oct 2014 14:09:06 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: Alban Hertroys <haramrae@gmail.com>
Subject: Re: 10.1RC1 armv6 RPI-B stuck in single user mode
Message-ID: <20141029130906.GI66862@home.opsec.eu>
References: <CAF-3MvMTXphsXpuQqGnwtHM_3WXSeJCWJfUNttxphuYXFmKeBA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAF-3MvMTXphsXpuQqGnwtHM_3WXSeJCWJfUNttxphuYXFmKeBA@mail.gmail.com>
Cc: freebsd-stable <freebsd-stable@freebsd.org>
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:09:08 -0000

Hi!

> 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?

Put the SD card into some other device, e.g. some laptop with FreeBSD,
run the fsck there ?

-- 
pi@opsec.eu            +49 171 3101372                         6 years to go !