The metaroot command edits the /etc/vfstab and /etc/system files so that the system may be booted with the root file system (/) on an appropriate metadevice. The only metadevices that support the root file system are a stripe with only a single disk or a mirror on a single-disk stripe.

If necessary, the metaroot command can reset a system that has been configured to boot the root file system (/) on a metadevice so that it uses a physical slice.

Root privileges are required for all of the following options except -h.

The following options are supported:

-c mddb.cf-name

Uses mddb.cf-name instead of the default /etc/lvm/mddb.cf file as a source of metadevice database locations.

-h

Displays a usage message.

-k system-name

Edits a user-supplied system-name instead of the default /etc/system system configuration information file.

-n

Print what would be done without actually doing it.

-v vfstab-name

Edits vfstab-name instead of the default /etc/vfstab table of file system defaults.

The following operands are supported:

device

Specifies either the metadevice or the conventional disk device (slice) used for the root file system (/).

/etc/system

System configuration information file. See system(4).

/etc/vfstab

File system defaults.

/etc/lvm/mddb.cf

Metadevice state database locations.

The following exit values are returned:

0

Successful completion.

>0

An error occurred.

See attributes(5) for descriptions of the following attributes:

metadb(1M), metainit(1M), metastat(1M), mddb.cf(4), system(4), vfstab(4), attributes(5)

Solaris Volume Manager Administration Guide

Soft partitions cannot be boot devices.

You can safely ignore the following messages. Their display is an artifact of the way drivers are loaded during the boot process.

WARNING: forceload of misc/md_hotspares failed might appear during boot if root is on a metadevice and no hot spares are specified. This can be eliminated by defining an empty hot spare pool.

WARNING: forceload of misc/md_trans failed might appear if no trans devices have been configured.

WARNING: forceload of misc/md_raid failed might appear if no RAID5 devices have been configured.