Date: Sun, 16 Aug 2015 19:50:39 +0000 From: John Howie <john@thehowies.com> To: Polytropon <freebsd@edvax.de> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: ada disk now da disk in upgrade to 10.2 Release? Message-ID: <C80A4ACA-CBF7-473B-ACC9-C274A49064C6@thehowies.com> In-Reply-To: <20150816203303.7f551b4b.freebsd@edvax.de> 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> <20150816203303.7f551b4b.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi there, Yes, thanks. I knew all of that. I am just providing an update to the list. I cannot believe I will be the only person to run into this. It is simply fixed, too. Just specify the fstype and (new) root disk partition manually at boot, and then modify /etc/fstab. Regards, John On 8/16/15, 11:33 AM, "Polytropon" <freebsd@edvax.de> wrote: >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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C80A4ACA-CBF7-473B-ACC9-C274A49064C6>