The metaroot command edits the /etc/vfstab and /etc/system files so that the system can 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 slice or a mirror on a single-slice 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:
Uses mddb.cf-name instead of the default /etc/lvm/mddb.cf file as a source of metadevice database locations.
Displays a usage message.
Edits a user-supplied system-name instead of the default /etc/system system configuration information file.
Edit the configuration file specified by md.conf-name rather than the default, /kernel/drv/md.conf.
Print what would be done without actually doing it.
When metaroot modifies system files, it accesses them in their relative location under root-path.
The -R option cannot be used in combination with the -c, -k,-m, or -v options.
Edits vfstab-name instead of the default /etc/vfstab table of file system defaults.
The following operands are supported:
Specifies either the metadevice or the conventional disk device (slice) used for the root file system (/).
The following command edits /etc/system and /etc/vfstab to specify that the root file system is now on metadevice d0.
# metaroot d0
The following command edits /etc/system and /etc/vfstab to specify that the root file system is now on the SCSI disk device /dev/dsk/c0t3d0s0.
# metaroot /dev/dsk/c0t3d0s0
System configuration information file. See system(4).
File system defaults.
Metadevice state database locations.
See attributes(5) for descriptions of the following attributes:
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.