From owner-freebsd-arm@freebsd.org Tue Feb 21 16:02:17 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 CB201CE8185 for ; Tue, 21 Feb 2017 16:02:17 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 AF07E7F5 for ; Tue, 21 Feb 2017 16:02:17 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: e8867c2b-f84e-11e6-b3c2-c9f38144898e X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id e8867c2b-f84e-11e6-b3c2-c9f38144898e; Tue, 21 Feb 2017 16:00:47 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v1LG18f4005247; Tue, 21 Feb 2017 09:01:08 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1487692868.73144.118.camel@freebsd.org> Subject: Re: Fatal kernel abort (was: r313878M builds mmcsd0s2 as read-only & /etc/fstab is missing) From: Ian Lepore To: Tony Hain Cc: freebsd-arm@freebsd.org Date: Tue, 21 Feb 2017 09:01:08 -0700 In-Reply-To: <159c01d28c18$bfbb90d0$3f32b270$@tndh.net> References: <155401d28ba9$ccdc28c0$66947a40$@tndh.net> <157701d28bda$dd004700$9700d500$@tndh.net> <1487638318.73144.116.camel@freebsd.org> <159c01d28c18$bfbb90d0$3f32b270$@tndh.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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 16:02:17 -0000 On Tue, 2017-02-21 at 00:01 -0800, Tony Hain wrote: > Ian Lepore wrote: > > > > > Subject: Re: Fatal kernel abort (was: r313878M builds mmcsd0s2 as > read-only > > > > & /etc/fstab is missing) > > > > 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 []... > > > [...] > > I think that's the trouble right there.  Loader 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. > > > > Either add a ufs label to the rootfs, or write fstab in terms of > > the > actual slice > > > > and partition. > > > > -- Ian  > 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.  > > Thanks again for pointing me in the right direction. I don't use crochet, hardly know anything about it.  But I know a lot of people do use it, so it seems like if it were really creating broken unusable images, other people would have something to say about that. -- Ian