PC-SYSINSTALL(8) BSD System Manager's Manual PC-SYSINSTALL(8)NAME
pc-sysinstall -- System installer backend
SYNOPSIS
pc-sysinstall [-c file] [command]
DESCRIPTION
The pc-sysinstall utility is a hybrid backend for installing FreeBSD. When run in install mode it takes a configuration file and performs an
installation according to the parameters specified in the configuration file. When called with one of the system query commands it provides
information about the system to aid a front end in building an appropriate configuration file.
The following options are available:
-c file
Perform an installation as directed by file.
COMMANDS
The command can be any one of the following:
help Display a list of all commands.
help command
Display the help data for the specified command.
disk-list
Provide a listing of the storage devices detected on this system.
disk-part disk
Queries the specified storage device and returns information about its partitions.
disk-info disk
Returns information about a storage device's size, cylinders, heads, and sectors.
detect-laptop
Tests to see if this system is a laptop or desktop.
detect-emulation
Tests to see if this system is running in an emulator
detect-nics
Returns a listing of the detected network cards on this system.
list-components
Returns a listing of the available components which can be installed.
list-rsync-backups user host port
Returns a listing of available rsync-backups on the target server in the life-preserver/ directory.
list-tzones
Returns a listing of available timezones.
query-langs
Returns a list of languages that the installer supports.
sys-mem
Returns the size of installed system RAM in MegaBytes.
test-netup
test if an internet connection is available.
update-part-list
Returns a list of PC-BSD and FreeBSD installs on this system for updates.
xkeyboard-layouts
Returns a list of keyboard layouts that xorg supports.
xkeyboard-models
Returns a list of keyboard models that xorg supports.
xkeyboard-variants
Returns a list of keyboard variants that xorg supports.
create-part disk size
Create a new MBR primary slice on the target disk using size MB.
delete-part partition
Delete the disk partition specified. If this is the last partition, the disk partition layout will also be scrubbed, leaving a clean
disk ready for MBR or GPT file system layouts.
start-autoinstall file
Start an automated installation with the specified file. Normally only used by automated install scripts.
setup-ssh-keys user host port
Setup SSH without a password for the target host, user, and port. Used to prompt the user to log into a server before doing a rsync
+ ssh restore.
HISTORY
This version of pc-sysinstall first appeared in FreeBSD 9.0.
AUTHORS
Kris Moore <kmoore@FreeBSD.org>
BUGS
This utility was written to install PC-BSD and has seen limited use as an installer for FreeBSD. It's likely that usage to install FreeBSD
will expose edge cases that PC-BSD doesn't, as well as generate feature requests based on unforeseen needs.
BSD June 24, 2010 BSD
Check Out this Related Man Page
voldiskadd(8) System Manager's Manual voldiskadd(8)NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager
SYNOPSIS
/usr/sbin/voldiskadd disk-address-list
DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for
use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility.
One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp
(for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names
in the /dev/disk directory.
For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a
The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk
to exclude (for example, dsk5).
The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified,
that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for
future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the
disk group.
If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated.
Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should
not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage
Manager. For new disks, all space on the disk becomes free space in the disk's disk group.
Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target
disks for an operation.
The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions.
Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group.
This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk
group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot
spare device. Creating new disk groups in which to import new disks.
If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist-
ing contents.
This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a
disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible.
This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no
currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes
referring the disk are restarted. This reattach action is performed by calling the volrecover script.
ERRORS
You may receive the following messages when using the voldiskadd command:
Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open.
This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be
a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device.
special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data.
Would you like to continue?? [y,n,q,?] (default: n)
This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints
this message to warn that a disk partition may have valid data which could be destroyed.
If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning
message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM.
FILES
A list of disks to exclude from use by voldiskadd.
SEE ALSO disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8)voldiskadd(8)