From owner-freebsd-questions@freebsd.org Sun Aug 16 18:33:13 2015 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 47CED9BBD8E for ; Sun, 16 Aug 2015 18:33:13 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0DD4E8F1 for ; Sun, 16 Aug 2015 18:33:12 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-150-34.dynamic.qsc.de [92.195.150.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 1878527836; Sun, 16 Aug 2015 20:33:03 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id t7GIX3Xd002288; Sun, 16 Aug 2015 20:33:03 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 16 Aug 2015 20:33:03 +0200 From: Polytropon To: John Howie Cc: "freebsd-questions@freebsd.org" Subject: Re: ada disk now da disk in upgrade to 10.2 Release? Message-Id: <20150816203303.7f551b4b.freebsd@edvax.de> In-Reply-To: <37CD6FAB-CA35-48D2-B8B0-342DE72B70CE@thehowies.com> References: <480CDD91-7457-4E11-B614-934F5B66FBCB@thehowies.com> <20150814225109.279f0c29.freebsd@edvax.de> <978FAFAC-5DBB-4464-B7DE-81F8DFF63E84@thehowies.com> <37CD6FAB-CA35-48D2-B8B0-342DE72B70CE@thehowies.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Aug 2015 18:33:13 -0000 On Sun, 16 Aug 2015 17:51:04 +0000, John Howie wrote: > Hi all, > > Following up. > > I verified that no changes have been made to the HyperV Cluster, > and that no changes were made to /etc/fstab in the upgrade. This file has no influence to how devices are being recognized. But as you mention it: Have you thought about adding labels to the partitions? It's a convenient way to abandon device names. Use the label to refer to the file system. You can find some informatio here: http://www.wonkity.com/~wblock/docs/html/labels.html https://www.freebsd.org/doc/handbook/geom-glabel.html It's easy to add them afterwards. No need to start over. > The virtual machine (10.1-RELEASE) was installed on the HyperV > Cluster from 10.1-RELEASE media, which created the ada disks > and partitions (I do remember there being difficulty in setting > the boot partition as active, and having to mark it manually). The installer _should_ be able to do this, but of course there is no problem to go to CLI and do it manually. It's not that this is a complicated task... :-) However, if a disk has been set as active, it doesn't matter as which device _type_ it's being recognized - it will boot, given that the BIOS (or in your case, the hypervisor) will transfer boot control to it. A partition marked as bootable will fulfill that requirement. From there on, labels are a convenient way to refer to the file system in further steps of the boot process (mounting root file system, mounting other file systems). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...