From owner-freebsd-questions@freebsd.org Fri Nov 11 12:25:46 2016 Return-Path: Delivered-To: freebsd-questions@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 D81BFC3B0A4 for ; Fri, 11 Nov 2016 12:25:46 +0000 (UTC) (envelope-from kuku@kukulies.org) Received: from kukulies.org (mail.kukulies.org [78.47.239.221]) by mx1.freebsd.org (Postfix) with ESMTP id 9ED4A17CF for ; Fri, 11 Nov 2016 12:25:46 +0000 (UTC) (envelope-from kuku@kukulies.org) Received: from localhost (localhost [127.0.0.1]) by kukulies.org (Postfix) with ESMTP id 4F96B4DA409 for ; Fri, 11 Nov 2016 13:25:45 +0100 (CET) Received: from kukulies.org ([127.0.0.1]) by localhost (kukulies.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4QM42DO2O2zq for ; Fri, 11 Nov 2016 13:25:45 +0100 (CET) Received: from [172.27.4.215] (unknown [87.79.34.228]) by kukulies.org (Postfix) with ESMTPSA id E86C04DA408 for ; Fri, 11 Nov 2016 13:25:44 +0100 (CET) Subject: Re: unknown error during root mount on boot (fstab) in 11.0-RELEASE (after updating) To: freebsd-questions@freebsd.org References: <7f9d7051-be30-54dd-55be-0fa236c28d84@kukulies.org> <82d02692-f98e-4605-a002-a7ffcdfdf233@kukulies.org> <0ca25b5a-1b97-e2b4-2966-79e7087db3ef@kukulies.org> <090fb456-257b-f916-8e2d-a581a994d488@freebsd.org> From: "Christoph P.U. Kukulies" Message-ID: Date: Fri, 11 Nov 2016 13:25:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <090fb456-257b-f916-8e2d-a581a994d488@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2016 12:25:46 -0000 I found my "lost devices". It was indeed /dev/ada1sX which I had to put into /etc/fstab instead of the ad6sX devices. Thanks. As to the logging not working: so it's not possible to log what appears on the console before the root FS is mounted read/write, right? -- Christoph Am 11.11.2016 um 12:59 schrieb Matthew Seaman: > On 11/11/16 11:51, Christoph P.U. Kukulies wrote: >> OK, so should I fireup gpart and label the volumes not listed? >> There is a directory /dev/gptid containing a UUID. > Yes, definitely. Labelling your partitions will make your life somewhat > easier. The /dev/gptid names could be used -- it always produces the > same device name for the same physical drive -- but it's so long it is > pretty unweildy to deal with. > >> Might this be the missing ad6? > Hmm... yes. I think the /dev/adN style device names were dropped in > 11.0-RELEASE, so what used to be ad6 is now probably only showing up as ada1 > > Cheers, > > Matthew > > >