<artheader>

    <subtitle>A Tutorial</subtitle>

<title>Formatting Media For Use With FreeBSD 2.2-RELEASE</title>

<subtitle>A Tutorial</subtitle>

    <authorgroup>

      <author>

<authorgroup>

	<firstname>Doug</firstname>

<author>

<firstname>Doug</firstname>

	<surname>White</surname>

<surname>White</surname>

<affiliation>

	<affiliation>

<address><email>dwhite@resnet.uoregon.edu</email></address>

	  <address>

</affiliation>

	    <email>dwhite@resnet.uoregon.edu</email>

</author>

	  </address>

</authorgroup>

	</affiliation>

      </author>

<pubdate>March 1997</pubdate>

    </authorgroup>

<abstract><para>This document describes how to slice, partition, and

format hard disk drives and similar media for use with FreeBSD.  The

    <pubdate>March 1997</pubdate>

examples given have been tested under FreeBSD 2.2-GAMMA and may work

for other releases. </para>

    <abstract>

</abstract>

      <para>This document describes how to slice, partition, and

</artheader>

	format hard disk drives and similar media for use with

	FreeBSD.  The examples given have been tested under FreeBSD

<sect1>

	2.2-GAMMA and may work for other releases.</para>

<title>Introduction & Definitions</title>

    </abstract>

  </artheader>

<sect2>

<title>Overview</title>

  <sect1>

<para>Successfully adding disks to an existing system is the mark of an

    <title>Introduction & Definitions</title>

experienced system administrator.  Slicing, partitioning, and adding

disks requires a careful dance of proper command and name syntax.  One

    <sect2>

slipped finger and an entire disk could disappear in seconds.  This

      <title>Overview</title>

document is written in an attempt to simplify this process and avoid

accidents.  Thankfully, enhancements to existing tools (notably

      <para>Successfully adding disks to an existing system is the

sysinstall) have greatly improved this process in recent releases of

	mark of an experienced system administrator.  Slicing,

FreeBSD.  </para>

	partitioning, and adding disks requires a careful dance of

	proper command and name syntax.  One slipped finger and an

<para>There are two possible modes of disk formatting:

	entire disk could disappear in seconds.  This document is

</para>

	written in an attempt to simplify this process and avoid

<itemizedlist> 

	accidents.  Thankfully, enhancements to existing tools

	(notably sysinstall) have greatly improved this process in

<listitem><para><firstterm>compatibility mode</firstterm>: Arranging a

	recent releases of FreeBSD.</para>

disk so that it has a slice table for use with other operating

systems.</para> </listitem>

      <para>There are two possible modes of disk formatting:</para>

<listitem><para><firstterm>dangerously dedicated mode</firstterm>:

      <itemizedlist> 

Formatting a disk with no slice table.  This makes the process of

	<listitem>

adding disks easier, however non-FreeBSD operating systems may not

	  <para><firstterm>compatibility mode</firstterm>: Arranging a

accept the disk. </para> </listitem> 

	    disk so that it has a slice table for use with other

</itemizedlist> 

	    operating systems.</para>

	</listitem>

<para>For most cases, dedicated mode is the easiest to set up and use

in existing systems, as a new disk is usually dedicated entirely to

	<listitem>

FreeBSD.  However, compatibility mode insures optimum interoperability

	  <para><firstterm>dangerously dedicated mode</firstterm>:

with future installations at a cost of increased complexity.</para>

	    Formatting a disk with no slice table.  This makes the

	    process of adding disks easier, however non-FreeBSD

<para>In addition to selecting the mode, two methods of slicing the

	    operating systems may not accept the disk.</para>

disk are available.  One is using the system installation tool

	</listitem> 

<command>/stand/sysinstall</command>.  2.1.7-RELEASE and later

      </itemizedlist> 

versions of <command>sysinstall</command> contain code to ease setup

of disks during normal system operation, mainly allowing access to the

      <para>For most cases, dedicated mode is the easiest to set up

Label and Partition editors and a Write feature which will update just

	and use in existing systems, as a new disk is usually

the selected disk and slice without affecting other disks.  The other

	dedicated entirely to FreeBSD.  However, compatibility mode

method is running the tools manually from a root command line.  For

	insures optimum interoperability with future installations at

dangerously dedicated mode, only three or four commands are involved

	a cost of increased complexity.</para>

while <command>sysinstall</command> requires some manipulation.</para>

</sect2>

      <para>In addition to selecting the mode, two methods of slicing

<sect2>

	the disk are available.  One is using the system installation

<title>Definitions</title>

	tool <command>/stand/sysinstall</command>.  2.1.7-RELEASE and

	later versions of <command>sysinstall</command> contain code

<para>UNIX disk management over the centuries has invented many new

	to ease setup of disks during normal system operation, mainly

definitions for old words.  The following glossary covers the

	allowing access to the Label and Partition editors and a Write

definitions used in this document and (hopefully) for FreeBSD in

	feature which will update just the selected disk and slice

general.  </para>

	without affecting other disks.  The other method is running

	the tools manually from a root command line.  For dangerously

	dedicated mode, only three or four commands are involved while

	<command>sysinstall</command> requires some

	manipulation.</para>

    </sect2>

    <sect2>

      <title>Definitions</title>

      <para>UNIX disk management over the centuries has invented many

	new definitions for old words.  The following glossary covers

	the definitions used in this document and (hopefully) for

	FreeBSD in general.</para>

<itemizedlist>

      <itemizedlist>

<listitem><para>compatibility mode:  Arranging a disk so that it has a slice

	<listitem>

table for use with other operating systems.  Oppose dangerously

	  <para>compatibility mode:  Arranging a disk so that it has a

dedicated mode.</para></listitem>

	    slice table for use with other operating systems.  Oppose

	    dangerously dedicated mode.</para>

<listitem><para>dangerously dedicated mode:  Formatting a disk with no slice

	</listitem>

table.  This makes the process of adding disks easier, however

non-FreeBSD operating systems may not accept the disk.  Oppose

	<listitem>

compatibility mode.</para></listitem>

	  <para>dangerously dedicated mode:  Formatting a disk with no

	    slice table.  This makes the process of adding disks

<listitem><para>disk:   A circular disc,  covered with magnetic or similarly

	    easier, however non-FreeBSD operating systems may not

manipulable material, spun by a motor under a head.  Data is stored on

	    accept the disk.  Oppose compatibility mode.</para>

the disk by changing the pattern of magnetism on the disc, which can

	</listitem>

be later read.  Hard disks, CD-ROMs, Magneto-optical,and Zip/Jaz

removables are examples of disks.</para></listitem>

	<listitem>

	  <para>disk:   A circular disc,  covered with magnetic or

<listitem><para>slice: A division of a disk.  Up to four slices are permitted on one

	    similarly manipulable material, spun by a motor under a

disk in the PC standard.  Slices are composed of contiguous sectors.

	    head.  Data is stored on the disk by changing the pattern

Slices are recorded in a <quote>slice table</quote> used by the system BIOS to

	    of magnetism on the disc, which can be later read.  Hard

locate bootable partitions.  The slice table is usually called the

	    disks, CD-ROMs, Magneto-optical,and Zip/Jaz removables are

Partition Table in DOS parlance.  Maintained by the fdisk utility.</para></listitem>

	    examples of disks.</para>

	</listitem>

<listitem><para>partition: A division of a slice.  Usually used in reference

to divisions of the FreeBSD slice of a disk.  Each filesystem and swap

	<listitem>

area on a disk resides in a partition.  Maintained using the disklabel

	  <para>slice: A division of a disk.  Up to four slices are

utility.</para></listitem>

	    permitted on one disk in the PC standard.  Slices are

	    composed of contiguous sectors.  Slices are recorded in a

	    <quote>slice table</quote> used by the system BIOS to

	    locate bootable partitions.  The slice table is usually

	    called the Partition Table in DOS parlance.  Maintained by

	    the fdisk utility.</para>

	</listitem>

	<listitem>

	  <para>partition: A division of a slice.  Usually used in

	    reference to divisions of the FreeBSD slice of a disk.

	    Each filesystem and swap area on a disk resides in a

	    partition.  Maintained using the disklabel utility.</para>

	</listitem>

<listitem><para>sector:  Smallest subdivision of a disk.  One sector usually

	<listitem>

represents 512 bytes of data.</para></listitem>

	  <para>sector:  Smallest subdivision of a disk.  One sector

	    usually represents 512 bytes of data.</para>

</itemizedlist>

	</listitem>

</sect2>

      </itemizedlist>

    </sect2>

<sect2>

<title>Warnings & Pitfalls</title>

    <sect2>

      <title>Warnings & Pitfalls</title>

<para>Building disks is not something to take lightly.  It is quite possible

to destroy the contents of other disks in your system if the proper 

      <para>Building disks is not something to take lightly.  It is

precautions are not taken.</para>

	quite possible to destroy the contents of other disks in your

	system if the proper precautions are not taken.</para>

<para><emphasis>Check your work carefully.</>  It is very simple to destroy

the incorrect disk when working with these commands.  When

      <para><emphasis>Check your work carefully.</>  It is very simple

in doubt consult the kernel boot output for the proper device.</para>

	to destroy the incorrect disk when working with these

	commands.  When in doubt consult the kernel boot output for

<para>Needless to say, we are not responsible for any damage to any data 

	the proper device.</para>

or hardware that you may experience.  You work at your own risk!</para>

      <para>Needless to say, we are not responsible for any damage to

</sect2>

	any data or hardware that you may experience.  You work at

	your own risk!</para>

    </sect2>

    <sect2>

      <title>Zip, Jaz, and Other Removables</title>

      <para>Removable disks can be formatted in the same way as normal

	hard disks.  It is essential to have the disk drive connected

	to the system and a disk placed in the drive during startup,

	so the kernel can determine the drive's geometry.  Check the

	<command>dmesg</command> output and make sure your device and

	the disk's size is listed.  If the kernel reports 

<procedure>

	then the disk was not in the drive.  In this case, you will

<step><para>Start sysinstall as root by typing 

	need to restart the machine before attempting to format

	disks.</para>

    </sect2>

  </sect1>

  <sect1>

    <title>Formatting Disks in Dedicated Mode</title>

    <sect2>

      <title>Introduction</title>

      <para>This section details how to make disks that are totally

	dedicated to FreeBSD.  Remember, dedicated mode disks cannot

	be booted by the PC architecture.</para>

    </sect2>

    <sect2>

      <title>Making Dedicated Mode Disks using Sysinstall</title>

      <para><command>/stand/sysinstall</command>, the system

	installation utility, has been expanded in recent versions to

	make the process of dividing disks properly a less tiring

	affair.  The fdisk and disklabel editors built into sysinstall

	are GUI tools that remove much of the confusion from slicing

	disks.  For FreeBSD versions 2.1.7 and later, this is perhaps

	the simplest way to slice disks.</para>

      <procedure>

	<step>

	  <para>Start sysinstall as root by typing 

<screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>

<screen>

&prompt.root; <userinput>/stand/sysinstall</userinput>

</screen>

<step><para>Select <command>Index</command>.</para></step>

	    from the command prompt.</para>

<step><para>Select <command>Partition</command>.</para></step>

	</step>

<step><para>Select the disk to edit with arrow keys and

<keycap>SPACE</keycap>.</para>

	<step>

</step>

	  <para>Select <command>Index</command>.</para>

<step><para>If you are using this entire disk for FreeBSD, select

	</step>

<command>A</command>.</para></step> 

<step><para>When asked: 

	<step>

	  <para>Select <command>Partition</command>.</para>

	</step>

	<step>

	  <para>Select the disk to edit with arrow keys and

	    <keycap>SPACE</keycap>.</para>

	</step>

	<step>

	  <para>If you are using this entire disk for FreeBSD, select

	    <command>A</command>.</para>

	</step> 

	<step>

	  <para>When asked: 

</informalexample>answer <command>No</command>.</para></step>

</informalexample>

<step><para>When asked if you still want to do this, answer

<command>Yes</command>.</para></step> 

	    answer <command>No</command>.</para>

<step><para>Select <command>Write</command>.</para></step>

	</step>

<step><para>When warned about Writing on installed systems, answer

<command>Yes</command>.</para></step> 

	<step>

<step><para><command>Quit</command>the FDISK Editor and

	  <para>When asked if you still want to do this, answer

<keycap>ESCAPE</keycap> back to the Index menu.</para></step>

	    <command>Yes</command>.</para>

<step><para>Select <command>Label</command> from the Index

	</step> 

menu.</para></step>  

<step><para>Label as desired.  For a single partition, enter

	<step>

<command>C</command> to Create a partition, accept the

	  <para>Select <command>Write</command>.</para>

default size, partition type Filesystem, and a mountpoint (which isn't

	</step>

used).</para></step> 

<step><para>Enter <command>W</command> when done and confirm to

	<step>

continue.  The filesystem will be newfs'd for you, unless you select 

	  <para>When warned about Writing on installed systems, answer

otherwise (for news partitions you'll want to do this!).  You'll get

	    <command>Yes</command>.</para>

the error: 

	</step> 

	<step>

	  <para><command>Quit</command>the FDISK Editor and

	    <keycap>ESCAPE</keycap> back to the Index menu.</para>

	</step>

	<step>

	  <para>Select <command>Label</command> from the Index

	    menu.</para>

	</step>

	<step>

	  <para>Label as desired.  For a single partition, enter

	    <command>C</command> to Create a partition, accept the

	    default size, partition type Filesystem, and a mountpoint

	    (which isn't used).</para>

	</step> 

	<step>

	  <para>Enter <command>W</command> when done and confirm to

	    continue.  The filesystem will be newfs'd for you, unless

	    you select otherwise (for news partitions you'll want to

	    do this!).  You'll get the error: 

<screen>Error mounting /mnt/dev/wd2s1e on /mnt/blah : No such file or directory </screen>

<screen>

Error mounting /mnt/dev/wd2s1e on /mnt/blah : No such file or directory </screen>

<para>	If you need to edit the disklabel to create multiple

      <para>If you need to edit the disklabel to create multiple

partitions (such as swap), use the following: </para>

	partitions (such as swap), use the following: </para>

<para>Your disk is now ready for use.</para>

      <para>Your disk is now ready for use.</para>

    </sect2>

</sect2>

  </sect1>

</sect1>

  <sect1>

<sect1>

    <title>Making Compatibility Mode Disks</title>

<title>Making Compatibility Mode Disks</title>

    <sect2>

<sect2>

      <title>Introduction</title>

<title>Introduction</title>

<para>The command line is the easiest way to make dedicated disks, and

      <para>The command line is the easiest way to make dedicated

the worst way to make compatibility disks.  The command-line fdisk

	disks, and the worst way to make compatibility disks.  The

utility requires higher math skills and an in-depth understanding of

	command-line fdisk utility requires higher math skills and an

the slice table, which is more than most people want to deal with.

	in-depth understanding of the slice table, which is more than

Use sysinstall for compatibility disks, as described below.</para>

	most people want to deal with.  Use sysinstall for

	compatibility disks, as described below.</para>

    </sect2>

    <sect2>

      <title>Making Compatibility Mode Disks Using Sysinstall</title>

      <procedure>

	<step>

	  <para>Start sysinstall as root by typing 

<step><para>Select <command>Index</command>.</para> </step>

	    from the command prompt.</para>

<step><para>Select <command>Partition</command>.</para></step>

	</step>

<step><para>Select the disk to edit with arrow keys and

<keycap>SPACE</keycap>.

	<step>

</para></step>

	  <para>Select <command>Index</command>.</para>

<step><para>If you are using this entire disk for FreeBSD, select

	</step>

<command>A</command>.</para></step> 

	<step>

	  <para>Select <command>Partition</command>.</para>

	</step>

	<step>

	  <para>Select the disk to edit with arrow keys and

	    <keycap>SPACE</keycap>.</para>

	</step>

	<step>

	  <para>If you are using this entire disk for FreeBSD, select

	    <command>A</command>.</para>

	</step> 

	<step>

	  <para>When asked: 

</informalexample> answer <command>yes</command>.</para></step>

</informalexample>

<step><para>Select <command>Write</command>.</para></step>

	    answer <command>yes</command>.</para>

<step><para>When asked to install the boot manager, select None with

	</step>

<keycap>SPACE</keycap> then hit <keycap>ENTER</keycap> for OK.</para></step>

<step><para><command>Quit</command> the FDISK Editor.</para></step>

	<step>

<step><para>You'll be asked about the boot manager, select

	  <para>Select <command>Write</command>.</para>

<command>None</command> 

	</step>

again. </para></step> 

<step><para>Select <command>Label</command> from the Index

	<step>

menu.</para></step>  

	  <para>When asked to install the boot manager, select None

<step><para>Label as desired.  For a single partition, accept the

	    with <keycap>SPACE</keycap> then hit

default size, type filesystem, and a mountpoint (which isn't

	    <keycap>ENTER</keycap> for OK.</para>

used).</para></step> 

	</step>

<step><para>The filesystem will be newfs'd for you, unless you select otherwise (for news partitions you'll want to do this!).  You'll get the error:

	<step>

	  <para><command>Quit</command> the FDISK Editor.</para>

	</step>

	<step>

	  <para>You'll be asked about the boot manager, select

	    <command>None</command> again. </para>

	</step> 

	<step>

	  <para>Select <command>Label</command> from the Index

	    menu.</para>

	</step>  

	<step>

	  <para>Label as desired.  For a single partition, accept the

	    default size, type filesystem, and a mountpoint (which

	    isn't used).</para>

	</step> 

	<step>

	  <para>The filesystem will be newfs'd for you, unless you

	    select otherwise (for news partitions you'll want to do

	    this!).  You'll get the error:

Ignore.

</para></step>

	    Ignore.</para>

<step><para>Exit out by repeatedly pressing <keycap>ESCAPE</keycap>.</para></step>

	</step>

</procedure>

	<step>

<para>Your new disk is now ready for use.</para>

	  <para>Exit out by repeatedly pressing

	    <keycap>ESCAPE</keycap>.</para>

</sect2>

	</step>

</sect1>

      </procedure>

<sect1>

      <para>Your new disk is now ready for use.</para>

<title>Other Disk Operations</title>

    </sect2>

<sect2>

  </sect1>

<title>Adding Swap Space</title>

  <sect1>

<para>As a system grows, it's need for swap space can also grow.

    <title>Other Disk Operations</title>

Although adding swap space to existing disks is very difficult, a new

disk can be partitioned with additional swap space.  </para>

    <sect2>

      <title>Adding Swap Space</title>

<para>To add swap space when adding a disk to a system:</para>

<procedure>

      <para>As a system grows, it's need for swap space can also grow.

<step><para>When partitioning the disk, edit the disklabel and

	Although adding swap space to existing disks is very

allocate the amount of swap space to add in partition `b' and the

	difficult, a new disk can be partitioned with additional swap

remainder in another partition, such as `a' or `e'.  The size is given

	space.</para>

in 512 byte blocks.  </para></step>

<step><para>When newfsing the drive, do NOT newfs the `c'

      <para>To add swap space when adding a disk to a system:</para>

partition.  Instead, newfs the partition where the non-swap space

lies.</para></step> 

      <procedure>

<step><para>Add an entry to <filename>/etc/fstab</filename> as follows:</para>

	<step>

	  <para>When partitioning the disk, edit the disklabel and

	    allocate the amount of swap space to add in partition `b'

	    and the remainder in another partition, such as `a' or

	    `e'.  The size is given in 512 byte blocks.</para>

	</step>

	<step>

	  <para>When newfsing the drive, do NOT newfs the `c'

	    partition.  Instead, newfs the partition where the

	    non-swap space lies.</para>

	</step> 

	<step>

	  <para>Add an entry to <filename>/etc/fstab</filename> as

	    follows:</para>

<para>

Change /dev/wd0b to the device of the newly added

	  <para>Change /dev/wd0b to the device of the newly added

space.</para></step>

	    space.</para>

<step><para>To make the new space immediately available, use the

	</step>

<command>swapon</command> command.

	<step>

	  <para>To make the new space immediately available, use the

	    <command>swapon</command> command.

</informalexample>

</informalexample></para>

</para></step>

	</step>

</procedure>

      </procedure>

</sect2>

    </sect2>

<sect2>

    <sect2>

<title>Copying the Contents of Disks</title>

      <title>Copying the Contents of Disks</title>

<para>Submitted By:  Renaud Waldura (<email>renaud@softway.com</email>) </para>

      <para>Submitted By:  Renaud Waldura

	(<email>renaud@softway.com</email>) </para>

      <para>To move file from your original base disk to the fresh new

	one, do:

</informalexample>

</informalexample></para>

</para>

    </sect2>

</sect2>

    <sect2>

      <title>Creating Striped Disks using CCD</title>

<sect2>

      <para>Commands Submitted By: Stan Brown

<title>Creating Striped Disks using CCD</title>

	(<email>stanb@awod.com</email>) </para>

<para>Commands Submitted By: Stan Brown (<email>stanb@awod.com</email>) </para>

      <para>The Concatenated Disk Driver, or CCD, allows you to treat

<para>

	several identical disks as a single disk.  Striping can result

The Concatenated Disk Driver, or CCD, allows you to treat several identical disks as a single disk.

	in increased disk performance by distributing reads and writes

Striping can result in increased disk performance by distributing reads and

	across the disks.  See the &man.ccd.4; and &man.ccdconfig.8;

writes across the disks.  See the &man.ccd.4; and &man.ccdconfig.8; man pages or the

	man pages or the <ulink

<ulink URL="http://stampede.cs.berkeley.edu/ccd/">CCD Homepage</ulink> for further details.</para>

	  URL="http://stampede.cs.berkeley.edu/ccd/">CCD

	  Homepage</ulink> for further details.</para>

<para>To create a new CCD, execute the following commands.  This describes

how to add three disks together; simply add or remove devices as

      <para>To create a new CCD, execute the following commands.  This

necessary.  Remember that the disks to be striped must be <emphasis>identical.</></para>

	describes how to add three disks together; simply add or

	remove devices as necessary.  Remember that the disks to be

	striped must be <emphasis>identical.</></para>

      <para>Before executing these commands, make sure you add the line

to your kernel.</para>

	to your kernel.</para>

<para>Now you can mount and use your CCD by referencing device /dev/ccd0c.

      <para>Now you can mount and use your CCD by referencing device

</para>

	/dev/ccd0c.</para>

    </sect2>

</sect2>

  </sect1>

</sect1>

  <sect1>

<sect1>

    <title>Credits</title>

<title>Credits</title>

    <para>The author would like to thank the following individuals for

      their contributions to this project:</para>

<para>The author would like to thank the following individuals for

    <itemizedlist>

their contributions to this project:</para>

      <listitem>

<itemizedlist>

	<para>Darryl Okahata

<listitem><para>Darryl Okahata

	  (<email>darrylo@hpnmhjw.sr.hp.com</email>) for his simple

(<email>darrylo@hpnmhjw.sr.hp.com</email>) for his

	  dedicated mode setup documentation which I have used

simple dedicated mode setup documentation which I have used repeatedly

	  repeatedly on freebsd-questions.</para>

on freebsd-questions.</para></listitem>

      </listitem>

<listitem><para>Jordan Hubbard

(<email>jkh@FreeBSD.org</email>) for making

      <listitem>

sysinstall useful for this type of task.</para></listitem>

	<para>Jordan Hubbard (<email>jkh@FreeBSD.org</email>) for

<listitem><para>John Fieber

	  making sysinstall useful for this type of task.</para>

(<email>jfieber@indiana.edu</email>) for making

      </listitem>

information and examples of the DocBook DTD on which this document is

based.</para></listitem>

      <listitem>

<listitem><para>Greg Lehey (<email>grog@FreeBSD.org</email>) for checking my 

	<para>John Fieber (<email>jfieber@indiana.edu</email>) for

work and pointing out inaccuracies, as well as miscellaneous support.

	  making information and examples of the DocBook DTD on which

</para></listitem>

	  this document is based.</para>

</itemizedlist>

      </listitem>

</sect1>

      <listitem>

	<para>Greg Lehey (<email>grog@FreeBSD.org</email>) for

	  checking my work and pointing out inaccuracies, as well as

	  miscellaneous support.</para>

      </listitem>

    </itemizedlist>

  </sect1>