From owner-freebsd-arm@freebsd.org Tue Feb 21 08:02:05 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C15ACE6035 for ; Tue, 21 Feb 2017 08:02:05 +0000 (UTC) (envelope-from tony@tndh.net) Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) (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 1700EA11; Tue, 21 Feb 2017 08:02:05 +0000 (UTC) (envelope-from tony@tndh.net) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tndh.net; s=dkim; h=Subject:Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:In-Reply-To:References:Cc:To:From; bh=EgTOy1HPHe2R0SxVKmARvFE/fEurYoLdO1gmAjP1gss=; b=Aufwyye9w0rghHipCgJ1rqeZN2e0SZWESyyN8d1LUO0e5EMCnDY6hC7jq5BqWFPpGWFLs+SPoGNdhY/EW886CZNeyPfPPbaVgjgqkx0KedMZPTb/+SwFly7h1+btghvFPD0Mz7njRxy38XaYDjQmi5F1PbzF/MLUOkW81mnhPO+C3O55; Received: from express.tndh.net ([2001:470:e930:1240:20d:56ff:fe04:4c0a] helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from ) id 1cg5OM-0004sX-1q; Tue, 21 Feb 2017 00:02:03 -0800 From: "Tony Hain" To: "'Ian Lepore'" , "'Svatopluk Kraus'" Cc: References: <155401d28ba9$ccdc28c0$66947a40$@tndh.net> <157701d28bda$dd004700$9700d500$@tndh.net> <1487638318.73144.116.camel@freebsd.org> In-Reply-To: <1487638318.73144.116.camel@freebsd.org> Date: Tue, 21 Feb 2017 00:01:46 -0800 Message-ID: <159c01d28c18$bfbb90d0$3f32b270$@tndh.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQCnfVO6Je0ytic8F/R4KA9fUNGMCgJKP4/IAZlpht8CMgTsK6OYS2wA Content-Language: en-us X-SA-Exim-Connect-IP: 2001:470:e930:1240:20d:56ff:fe04:4c0a X-SA-Exim-Mail-From: tony@tndh.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on express.tndh.net X-Spam-Level: X-Spam-Status: No, score=-1.0 required=4.5 tests=ALL_TRUSTED,RP_MATCHES_RCVD autolearn=unavailable version=3.3.1 Subject: RE: Fatal kernel abort (was: r313878M builds mmcsd0s2 as read-only & /etc/fstab is missing) X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on express.tndh.net) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2017 08:02:05 -0000 Ian Lepore wrote: > Subject: Re: Fatal kernel abort (was: r313878M builds mmcsd0s2 as read-only > & /etc/fstab is missing) >=20 > On Mon, 2017-02-20 at 16:38 -0800, Tony Hain wrote: > > [...] > > Booting from disk0s2a: > > [...] > > Mounting from ufs:/dev/ufs/rootfs failed with error 19. > > Trying to mount root from ufs:mmcsd0s2 []... > > [...] >=20 > I think that's the trouble right there. =A0Loader is aware that the = rootfs is s2a, > then the kernel tries to mount the labeled rootfs (presumably fstab = told it to > do that), and that fails, and then for some reason it mounts s2, not = s2a, and > that's not the right partition. >=20 > Either add a ufs label to the rootfs, or write fstab in terms of the actual slice > and partition. >=20 > -- Ian=20 Thanks for the pointer. I don't know if it is a change between 11 and = 12, or something in 12 that crochet is failing over, but there is no fstab = when building 12. I can't find any maintainer contact info for crochet, so I = am shooting in the dark here trying to patch together a working system. I copied an fstab from a working 11 build, but didn't look to see if the partitions were labeled before I overwrote it with 12. Clearly it was because the fstab was label based. When I tried gpart modify the = partition to add a label, I got syntax error, and will need to do further research = to figure that out. I have tried both /dev/mmcsd0s2a and /dev/mmcsd0s2 in fstab, and both = are failing as read-only. They are not marked that way on the media because = I can mount and write files from the crochet system. My first thought was = that something in the boot sequence handing off the device to FreeBSD as read-only, but when I try to mount the dos partition it fails to mount = and I end up with the kernel panic. When I mounted the dos partition on the crochet system the only difference I can see between the running BBB and = the dos sector in the BBG card is that the file names are upper case on the working one and lower case on the failing one. Given that the kernel = boots, the name case is unlikely to affect the mounting of the second partition = as read-only.=20 Thanks again for pointing me in the right direction.