From owner-freebsd-current@FreeBSD.ORG Mon Jun 29 09:04:34 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2DBE106564A for ; Mon, 29 Jun 2009 09:04:34 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id A47488FC08 for ; Mon, 29 Jun 2009 09:04:34 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:4cb0:c97d:951c:1ed8] (unknown [IPv6:2001:7b8:3a7:0:4cb0:c97d:951c:1ed8]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id B9E0B5C42; Mon, 29 Jun 2009 11:04:33 +0200 (CEST) Message-ID: <4A4883A2.9020004@andric.com> Date: Mon, 29 Jun 2009 11:04:34 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1pre) Gecko/20090627 Shredder/3.0b3pre MIME-Version: 1.0 To: Aisaka Taiga References: <4A476C7C.3020605@withagen.nl> <4A477576.6030701@haruhiism.net> <4A4779AF.1020303@digiware.nl> <4A487AEA.7040906@haruhiism.net> In-Reply-To: <4A487AEA.7040906@haruhiism.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Willem Jan Withagen , current@freebsd.org Subject: Re: 7.2-stable upgrade changes disknames X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 29 Jun 2009 09:04:35 -0000 On 2009-06-29 10:27, Aisaka Taiga wrote: >> And I have to manually fix my /etc/fstab to what is factual correct. >> And that was what my message was about: >> It can/will(??) bite a lot more users. >> With similar remarks and/or questions. > To be honest, I'm quite amused that it actually worked for you, because > if you use a dangerously dedicated disk you, basically, don't need a > partition table at all as the slice 'table' (bsdlabel) takes care of > everything. And if there's no partition table, there can be no adXs1a > boot device - even in 7.2. It seems sysinstall creates DDD's with a strange bit of inconsistency. If you install on e.g. /dev/ad0, it forces you to create a (bogus?) slice /dev/ad0s1, the corresponding entries in /dev are also created, and the newly installed system's fstab also uses ad0s1a, ad0s1b, etc. However, the disklabel and the partition table will overlap. In some cases, I have seen *both* ad0s1a and ad0a existing at the same time in /dev... Sometime, during Marcel Moolenaars work on removing GEOM_MBR and GEOM_BSD, and replacing them with GEOM_PART_MBR and GEOM_PART_BSD, respectively, this arrangement got modified, so suddenly the 's1' part wasn't recognized anymore, and you just got ad0a, ad0b, and so on. In my case, simply doing "bsdlabel -B /dev/ad0s1", the label's boot code would be overwritten with a default version, which contains a sort of bogus partition table, having a fourth slice of 50000 sectors. Apparently this leads to FreeBSD then recognizing the disk as not having any slices anymore, so the disk will just be using ad0[a-z] from that point forward. You'll definitely need to fix your fstab and possibly /boot/loader.conf, /etc/rc.conf and so on... Note that sysinstall in -CURRENT can't even create a DDD anymore, since it tries to newfs a first slice, which doesn't exist. :)