metaroot (1M)
Table of Contents

NAME

metaroot - setup system files for root (/) metadevice

SYNOPSIS

metaroot -h
metaroot [ -n ] [ -k system-name ] [ -v vfstab-name ] [ -c mddb.cf-name ] device

AVAILABILITY

/usr/opt/SUNWmd/sbin

DESCRIPTION

The metaroot command edits the /etc/vfstab and /etc/system files so that the system may be booted with the root file system (/) on a metadevice.

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.

-c mddb.cf-name
Uses mddb.cf-name instead of the default /etc/opt/SUNWmd/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.

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

EXAMPLES

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

# metaroot d0

The following command edits /etc/system and /etc/vfstab to specify that the root filesystem is now on the SCSI disk device /dev/dsk/c0t3d0s0.

# metaroot /dev/dsk/c0t3d0s0

FILES

/etc/system
Kernel patch file.

/etc/vfstab
File system defaults.

/etc/opt/SUNWmd/mddb.cf
Metadevice state database locations.

NOTES

WARNING: forceload of misc/md_hotspares failed may 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 may appear if no trans devices have been configured.

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

You can safely ignore these messages. This is an artifact of the way drivers are loaded during the boot process.

SEE ALSO

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

Solstice DiskSuite User's Guide, Solstice DiskSuite Reference