ada disk now da disk in upgrade to 10.2 Release?

Polytropon freebsd at
Sun Aug 16 18:33:13 UTC 2015

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:

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).

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

More information about the freebsd-questions mailing list