metaroot(1M)

NAME

     metaroot - setup system files for root (/) metadevice

SYNOPSIS

     /usr/sbin/metaroot -h

     /usr/sbin/metaroot  [-n]  [-k system-name]  [-v vfstab-name]
     [-c mddb.cf-name] [-m md.conf-name] [-R root-path] device

DESCRIPTION

     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  metadev-
     ices  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.

OPTIONS

     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 data-
           base 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.

     -m md.conf-name
           Edit the configuration file specified by  md.conf-name
           rather than the default, /kernel/drv/md.conf.

     -n    Print what would be done without actually doing it.

     -R root-path
           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.

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

OPERANDS

     The following operands are supported:

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

EXAMPLES

     Example 1: Specifying Root File System on Metadevice

     The following command edits /etc/system and  /etc/vfstab  to
     specify that the root file system is now on metadevice d0.

     # metaroot d0

     Example 2: Specifying Root File System on SCSI Disk

     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

FILES

     /etc/system
           System configuration information file. See system(4).

     /etc/vfstab
           File system defaults.

     /etc/lvm/mddb.cf
           Metadevice state database locations.

EXIT STATUS

     The following exit values are returned:

          0     Successful completion.

          >0    An error occurred.

ATTRIBUTES

     See attributes(5) for descriptions of the  following  attri-
     butes:

     ____________________________________________________________
    |       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
    |_____________________________|_____________________________|
    | Availability                | SUNWmdu                     |
    |_____________________________|_____________________________|

SEE ALSO

     metadb(1M),  metainit(1M),  metastat(1M),  mddb.cf(4),  sys-
     tem(4), vfstab(4), attributes(5)

     Solaris Volume Manager Administration Guide

NOTES

     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.