From owner-freebsd-current@freebsd.org Sat Oct 7 00:45:58 2017 Return-Path: Delivered-To: freebsd-current@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 581DFE246B6 for ; Sat, 7 Oct 2017 00:45:58 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 E23CC75F01 for ; Sat, 7 Oct 2017 00:45:57 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: b4e78a58-aaf8-11e7-a893-25625093991c 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 outbound1.eu.mailhop.org (Halon) with ESMTPSA id b4e78a58-aaf8-11e7-a893-25625093991c; Sat, 07 Oct 2017 00:44:43 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v970id1L006990; Fri, 6 Oct 2017 18:44:39 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1507337079.86205.282.camel@freebsd.org> Subject: Re: r324353: boot failure: failed with error 19 From: Ian Lepore To: "O. Hartmann" , Trond =?ISO-8859-1?Q?Endrest=F8l?= Cc: "O. Hartmann" , FreeBSD CURRENT , Warner Losh Date: Fri, 06 Oct 2017 18:44:39 -0600 In-Reply-To: <20171006223214.580eb09c@thor.intern.walstatt.dynvpn.de> References: <20171006151008.04af417d@thor.intern.walstatt.dynvpn.de> <20171006223214.580eb09c@thor.intern.walstatt.dynvpn.de> 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-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 00:45:58 -0000 On Fri, 2017-10-06 at 22:33 +0200, O. Hartmann wrote: > First of all, I think something has changed, since /dev/ufs doesn't get populated anymore > by usage of "gpart label" command. Second, there is a high chance that I messed up > NanoBSD a bit, a couple of days ago I tried to sync with the code base changes and I made > most changes effectively what is now "legacy.sh". Here is the crucial error...  Labels created with glabel are in /dev/label, they have never been in /dev/ufs. /dev/ufs is populated by the contents of ufs filesystem labels, which are created using "newfs -L" or "tunefs -L".  To see what label (if any) is on your root filesystem, use:   # dumpfs / | grep vol   volname roots1 swuid 0 providersize 262135 If nothing appears between "volname" and "swuid" it has no label. I'm not disputing something may have changed that is causing you problems, I'm just trying to point out that you are chasing the wrong cause based on some kind of misunderstanding of the symptoms. -- Ian