From owner-freebsd-questions@freebsd.org Fri Nov 11 11:51:48 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 79420C3B5C8 for ; Fri, 11 Nov 2016 11:51:48 +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 3D0481013 for ; Fri, 11 Nov 2016 11:51:47 +0000 (UTC) (envelope-from kuku@kukulies.org) Received: from localhost (localhost [127.0.0.1]) by kukulies.org (Postfix) with ESMTP id 33BB84DA409 for ; Fri, 11 Nov 2016 12:51:47 +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 22iKNI3HqBLf for ; Fri, 11 Nov 2016 12:51:46 +0100 (CET) Received: from [172.27.4.215] (unknown [87.79.34.228]) by kukulies.org (Postfix) with ESMTPSA id 402EE4DA408 for ; Fri, 11 Nov 2016 12:51:46 +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> From: "Christoph P.U. Kukulies" Message-ID: <0ca25b5a-1b97-e2b4-2966-79e7087db3ef@kukulies.org> Date: Fri, 11 Nov 2016 12:51:47 +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: 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 11:51:48 -0000 Am 11.11.2016 um 12:35 schrieb Matthew Seaman: > On 11/11/16 11:19, Christoph P.U. Kukulies wrote: >> It doesn't work. I enable console.info and *.* to go to >> /var/log/console.log resp. all.log >> bute the fiels weren't there. Also touching them in the first place >> didn't help. >> Maybe because the root FS isn't writeable at this point in time. >> >> Here is a screenshot: >> >> http://imgur.com/fEGCWhh > So, what disk devices show up in /dev after reboot? Note that /dev/ad? > style is old and /dev/ada? is the new standard. In fact the /dev/adXpY > device entries should be symlinks to the appropriate /dev/adaNpY > devices. Also note that device numbering is not particularly constant > over reboots -- if you boot with or without eg. a USB memstick plugged > in, it can cause everything to get renumbered. This is why the advice > nowadays is to use gpart(8) to set a label on your filesystems and use > /dev/gpt/labelname in /etc/fstab ada0 ada0s1 ada0s1a ada0s1b ada0s1d ada0s1e ada1 ada1p1 ada1p2 ada1p3 OK, so should I fireup gpart and label the volumes not listed? There is a directory /dev/gptid containing a UUID. Might this be the missing ad6? -- Christoph > Cheers, > > Matthew > >