From owner-svn-doc-all@FreeBSD.ORG Fri Jan 24 18:11:25 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3EFC89D4; Fri, 24 Jan 2014 18:11:25 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 290B11A5B; Fri, 24 Jan 2014 18:11:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0OIBPCs058999; Fri, 24 Jan 2014 18:11:25 GMT (envelope-from manolis@svn.freebsd.org) Received: (from manolis@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0OIBOuW058994; Fri, 24 Jan 2014 18:11:24 GMT (envelope-from manolis@svn.freebsd.org) Message-Id: <201401241811.s0OIBOuW058994@svn.freebsd.org> From: Manolis Kiagias Date: Fri, 24 Jan 2014 18:11:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43640 - in head/el_GR.ISO8859-7/books/handbook: . disks preface X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 18:11:25 -0000 Author: manolis Date: Fri Jan 24 18:11:24 2014 New Revision: 43640 URL: http://svnweb.freebsd.org/changeset/doc/43640 Log: Update more parts of the Greek Handbook to the latest versions Highlights: - 'vinum' chapter removed from build - Mostly untranslated 'disks' chapter replaced with the latest en_US version Note that the 'users' chapter still remains in the Greek Handbook for reference until it is updated and merged with 'basics' New revisions: preface r43126 disks r43449 book.xml r43566 chapters.ent r43126 Makefile r43126 Obtained From: The FreeBSD Greek Documentation Project Modified: head/el_GR.ISO8859-7/books/handbook/Makefile head/el_GR.ISO8859-7/books/handbook/book.xml head/el_GR.ISO8859-7/books/handbook/chapters.ent head/el_GR.ISO8859-7/books/handbook/disks/chapter.xml head/el_GR.ISO8859-7/books/handbook/preface/preface.xml Modified: head/el_GR.ISO8859-7/books/handbook/Makefile ============================================================================== --- head/el_GR.ISO8859-7/books/handbook/Makefile Fri Jan 24 17:03:57 2014 (r43639) +++ head/el_GR.ISO8859-7/books/handbook/Makefile Fri Jan 24 18:11:24 2014 (r43640) @@ -4,7 +4,7 @@ # Μορφοποίηση του Εγχειριδίου του FreeBSD # # %SOURCE% en_US.ISO8859-1/books/handbook/Makefile -# %SRCID% 1.119 +# %SRCID% 43126 # # ------------------------------------------------------------------------ @@ -50,6 +50,7 @@ IMAGES_EN = advanced-networking/isdn-bus IMAGES_EN+= advanced-networking/isdn-twisted-pair.eps IMAGES_EN+= advanced-networking/natd.eps IMAGES_EN+= advanced-networking/net-routing.pic +IMAGES_EN+= advanced-networking/pxe-nfs.png IMAGES_EN+= advanced-networking/static-routes.pic IMAGES_EN+= bsdinstall/bsdinstall-adduser1.png IMAGES_EN+= bsdinstall/bsdinstall-adduser2.png @@ -179,13 +180,6 @@ IMAGES_EN+= security/ipsec-network.pic IMAGES_EN+= security/ipsec-crypt-pkt.pic IMAGES_EN+= security/ipsec-encap-pkt.pic IMAGES_EN+= security/ipsec-out-pkt.pic -IMAGES_EN+= vinum/vinum-concat.pic -IMAGES_EN+= vinum/vinum-mirrored-vol.pic -IMAGES_EN+= vinum/vinum-raid10-vol.pic -IMAGES_EN+= vinum/vinum-raid5-org.pic -IMAGES_EN+= vinum/vinum-simple-vol.pic -IMAGES_EN+= vinum/vinum-striped-vol.pic -IMAGES_EN+= vinum/vinum-striped.pic IMAGES_EN+= virtualization/parallels-freebsd1.png IMAGES_EN+= virtualization/parallels-freebsd2.png IMAGES_EN+= virtualization/parallels-freebsd3.png @@ -283,8 +277,8 @@ SRCS+= preface/preface.xml SRCS+= printing/chapter.xml SRCS+= security/chapter.xml SRCS+= serialcomms/chapter.xml +# Users chapter stays in the Greek Build until merged with basics SRCS+= users/chapter.xml -SRCS+= vinum/chapter.xml SRCS+= virtualization/chapter.xml SRCS+= x11/chapter.xml @@ -316,12 +310,12 @@ DOC_PREFIX?= ${.CURDIR}/../../.. # rules generating lists of mirror site from XML database. # XMLDOCS= lastmod:::mirrors.lastmod.inc \ - mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-ftp-index:::mirrors.xml.ftp.index.inc \ - mirrors-cvsup:::mirrors.xml.cvsup.inc \ + mirrors-ftp:::mirrors.xml.ftp.inc \ mirrors-cvsup-index:::mirrors.xml.cvsup.index.inc \ - eresources:::eresources.xml.www.inc \ - eresources-index:::eresources.xml.www.index.inc + mirrors-cvsup:::mirrors.xml.cvsup.inc \ + eresources-index:::eresources.xml.www.index.inc \ + eresources:::eresources.xml.www.inc DEPENDSET.DEFAULT= transtable mirror XSLT.DEFAULT= ${XSL_MIRRORS} XML.DEFAULT= ${XML_MIRRORS} Modified: head/el_GR.ISO8859-7/books/handbook/book.xml ============================================================================== --- head/el_GR.ISO8859-7/books/handbook/book.xml Fri Jan 24 17:03:57 2014 (r43639) +++ head/el_GR.ISO8859-7/books/handbook/book.xml Fri Jan 24 18:11:24 2014 (r43640) @@ -5,9 +5,8 @@ %chapters; %txtfiles; - - ]> + + Εγχειρίδιο του FreeBSD - Ομάδα Τεκμηρίωσης του FreeBSD @@ -49,6 +48,8 @@ 2010 2011 2012 + 2013 + 2014 Ομάδα Τεκμηρίωσης του FreeBSD @@ -62,7 +63,6 @@ &tm-attrib.adaptec; &tm-attrib.adobe; &tm-attrib.apple; - &tm-attrib.corel; &tm-attrib.creative; &tm-attrib.cvsup; &tm-attrib.heidelberger; @@ -73,18 +73,12 @@ &tm-attrib.linux; &tm-attrib.lsilogic; &tm-attrib.m-systems; - &tm-attrib.macromedia; &tm-attrib.microsoft; - &tm-attrib.netscape; - &tm-attrib.nexthop; &tm-attrib.opengroup; &tm-attrib.oracle; - &tm-attrib.powerquest; &tm-attrib.realnetworks; &tm-attrib.redhat; - &tm-attrib.sap; &tm-attrib.sun; - &tm-attrib.symantec; &tm-attrib.themathworks; &tm-attrib.thomson; &tm-attrib.usrobotics; @@ -113,8 +107,9 @@ http://docs.FreeBSD.org/doc/). Μπορείτε επίσης να μεταφορτώσετε στον υπολογιστή σας το ίδιο βιβλίο σε άλλες μορφές αρχείου και με διάφορες μορφές συμπίεσης από - τον εξυπηρετητή - FTP του &os; ή ένα από τα + τον εξυπηρετητή + FTP του &os; ή ένα από τα πολλά mirror sites. Αν προτιμάτε ένα τυπωμένο αντίτυπο, μπορείτε να αγοράσετε ένα αντίγραφο του Εγχειριδίου, από το @@ -171,8 +166,8 @@ &chap.introduction; - &chap.install; &chap.bsdinstall; + &chap.install; &chap.basics; &chap.ports; &chap.x11; @@ -252,6 +247,8 @@ &chap.config; &chap.boot; + &chap.users; &chap.security; &chap.jails; @@ -260,7 +257,6 @@ &chap.disks; &chap.geom; &chap.filesystems; - &chap.vinum; &chap.virtualization; &chap.l10n; &chap.cutting-edge; Modified: head/el_GR.ISO8859-7/books/handbook/chapters.ent ============================================================================== --- head/el_GR.ISO8859-7/books/handbook/chapters.ent Fri Jan 24 17:03:57 2014 (r43639) +++ head/el_GR.ISO8859-7/books/handbook/chapters.ent Fri Jan 24 18:11:24 2014 (r43640) @@ -13,7 +13,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/chapters.ent - %SRCID% 1.40 + %SRCID% 43126 --> @@ -38,6 +38,7 @@ + @@ -46,7 +47,6 @@ - Modified: head/el_GR.ISO8859-7/books/handbook/disks/chapter.xml ============================================================================== --- head/el_GR.ISO8859-7/books/handbook/disks/chapter.xml Fri Jan 24 17:03:57 2014 (r43639) +++ head/el_GR.ISO8859-7/books/handbook/disks/chapter.xml Fri Jan 24 18:11:24 2014 (r43640) @@ -8,7 +8,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/disks/chapter.xml - %SRCID% 1.1 + %SRCID% 43449 --> @@ -52,17 +52,10 @@ στο &os;. - Τα διάφορα διαθέσιμα μέσα αποθήκευσης για αντίγραφα - ασφαλείας. - - Πως να χρησιμοποιήσετε προγράμματα λήψης αντιγράφων ασφαλείας στο &os;. - Πως να πάρετε αντίγραφα ασφαλείας σε δισκέττες. - - Τι είναι οι εικόνες (snapshots) σε ένα σύστημα αρχείων και πως να τις χρησιμοποιήσετε αποδοτικά. @@ -72,19 +65,17 @@ - Να ξέρετε πως θα ρυθμίσετε και θα εγκαταστήσετε ένα νέο πυρήνα - του &os; (). + Να ξέρετε πως να ρυθμίσετε και + να εγκαταστήσετε ένα νέο πυρήνα του &os;. - Device Names The following is a list of physical storage devices - supported in FreeBSD, and the device names associated with - them. + supported in &os; and their associated device names. Physical Disk Naming Conventions @@ -96,45 +87,70 @@ Drive device name + IDE hard drives - ad + ad or + ada + + + + IDE CD-ROM drives + acd or + cd + + + + SATA hard drives + ad or + ada + - IDE CDROM drives - acd + SATA CD-ROM drives + acd or + cd + - SCSI hard drives and USB Mass storage devices + SCSI hard drives and USB Mass storage + devices da + - SCSI CDROM drives + SCSI CD-ROM drives cd + - Assorted non-standard CDROM drives + Assorted non-standard CD-ROM drives mcd for Mitsumi CD-ROM and - scd for Sony CD-ROM devices - + scd for Sony CD-ROM devices + Floppy drives fd + SCSI tape drives sa - + + IDE tape drives ast + Flash drives - fla for &diskonchip; Flash device + fla for &diskonchip; Flash + device + RAID drives aacd for &adaptec; AdvancedRAID, @@ -150,618 +166,142 @@ - Adding Disks + + Adding Disks + - DavidO'BrienOriginally contributed by + + + David + O'Brien + + Originally contributed by + - - - disks adding - Lets say we want to add a new SCSI disk to a machine that - currently only has a single drive. First turn off the computer - and install the drive in the computer following the instructions - of the computer, controller, and drive manufacturer. Due to the - wide variations of procedures to do this, the details are beyond - the scope of this document. - - Login as user root. After you have installed the - drive, inspect /var/run/dmesg.boot to ensure the new - disk was found. Continuing with our example, the newly added drive will - be da1 and we want to mount it on - /1 (if you are adding an IDE drive, the device name - will be ad1). + This section describes how to add a new + SATA disk to a machine that currently only + has a single drive. First, turn off the computer and install + the drive in the computer following the instructions of the + computer, controller, and drive manufacturers. Reboot the + system and become + root. + + Inspect /var/run/dmesg.boot to ensure + the new disk was found. In this example, the newly added + SATA drive will appear as + ada1. partitions - slices - fdisk + gpart - FreeBSD runs on IBM-PC compatible computers, therefore it must - take into account the PC BIOS partitions. These are different - from the traditional BSD partitions. A PC disk has up to four - BIOS partition entries. If the disk is going to be truly - dedicated to FreeBSD, you can use the - dedicated mode. Otherwise, FreeBSD will - have to live within one of the PC BIOS partitions. FreeBSD - calls the PC BIOS partitions slices so as - not to confuse them with traditional BSD partitions. You may - also use slices on a disk that is dedicated to FreeBSD, but used - in a computer that also has another operating system installed. - This is a good way to avoid confusing the fdisk utility of - other, non-FreeBSD operating systems. - - In the slice case the drive will be added as - /dev/da1s1e. This is read as: SCSI disk, - unit number 1 (second SCSI disk), slice 1 (PC BIOS partition 1), - and e BSD partition. In the dedicated - case, the drive will be added simply as - /dev/da1e. - - Due to the use of 32-bit integers to store the number of sectors, - &man.bsdlabel.8; is - limited to 2^32-1 sectors per disk or 2TB in most cases. The - &man.fdisk.8; format allows a starting sector of no more than - 2^32-1 and a length of no more than 2^32-1, limiting partitions to - 2TB and disks to 4TB in most cases. The &man.sunlabel.8; format - is limited to 2^32-1 sectors per partition and 8 partitions for - a total of 16TB. For larger disks, &man.gpt.8; partitions may be - used. - - - Using &man.sysinstall.8; - - sysinstall - adding disks - - - su - - - - Navigating <application>Sysinstall</application> - - You may use sysinstall to - partition and label a new disk using its easy to use menus. - Either login as user root or use the - su command. Run - sysinstall and enter the - Configure menu. Within the - FreeBSD Configuration Menu, scroll down and - select the Fdisk option. - - - - <application>fdisk</application> Partition Editor - Once inside fdisk, typing A will - use the entire disk for FreeBSD. When asked if you want to - remain cooperative with any future possible operating - systems, answer YES. Write the - changes to the disk using W. Now exit the - FDISK editor by typing q. Next you will be - asked about the Master Boot Record. Since you are adding a - disk to an already running system, choose - None. - - - - Disk Label Editor - BSD partitions - - Next, you need to exit sysinstall - and start it again. Follow the directions above, although this - time choose the Label option. This will - enter the Disk Label Editor. This - is where you will create the traditional BSD partitions. A - disk can have up to eight partitions, labeled - a-h. - A few of the partition labels have special uses. The - a partition is used for the root partition - (/). Thus only your system disk (e.g, - the disk you boot from) should have an a - partition. The b partition is used for - swap partitions, and you may have many disks with swap - partitions. The c partition addresses the - entire disk in dedicated mode, or the entire FreeBSD slice in - slice mode. The other partitions are for general use. - - sysinstall's Label editor - favors the e - partition for non-root, non-swap partitions. Within the - Label editor, create a single file system by typing - C. When prompted if this will be a FS - (file system) or swap, choose FS and type in a - mount point (e.g, /mnt). When adding a - disk in post-install mode, sysinstall - will not create entries - in /etc/fstab for you, so the mount point - you specify is not important. - - You are now ready to write the new label to the disk and - create a file system on it. Do this by typing - W. Ignore any errors from - sysinstall that - it could not mount the new partition. Exit the Label Editor - and sysinstall completely. - - - - Finish - - The last step is to edit /etc/fstab - to add an entry for your new disk. - - - - - - Using Command Line Utilities - - - Using Slices - - This setup will allow your disk to work correctly with - other operating systems that might be installed on your - computer and will not confuse other operating systems' - fdisk utilities. It is recommended - to use this method for new disk installs. Only use - dedicated mode if you have a good reason - to do so! - - &prompt.root; dd if=/dev/zero of=/dev/da1 bs=1k count=1 -&prompt.root; fdisk -BI da1 #Initialize your new disk -&prompt.root; bsdlabel -B -w -r da1s1 auto #Label it. -&prompt.root; bsdlabel -e da1s1 # Edit the bsdlabel just created and add any partitions. -&prompt.root; mkdir -p /1 -&prompt.root; newfs /dev/da1s1e # Repeat this for every partition you created. -&prompt.root; mount /dev/da1s1e /1 # Mount the partition(s) -&prompt.root; vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. - - If you have an IDE disk, substitute ad - for da. - - - - Dedicated - OS/2 - - If you will not be sharing the new drive with another operating - system, you may use the dedicated mode. Remember - this mode can confuse Microsoft operating systems; however, no damage - will be done by them. IBM's &os2; however, will - appropriate any partition it finds which it does not - understand. - - &prompt.root; dd if=/dev/zero of=/dev/da1 bs=1k count=1 -&prompt.root; bsdlabel -Brw da1 auto -&prompt.root; bsdlabel -e da1 # create the `e' partition -&prompt.root; newfs -d0 /dev/da1e -&prompt.root; mkdir -p /1 -&prompt.root; vi /etc/fstab # add an entry for /dev/da1e -&prompt.root; mount /1 - - An alternate method is: - - &prompt.root; dd if=/dev/zero of=/dev/da1 count=2 -&prompt.root; bsdlabel /dev/da1 | bsdlabel -BrR da1 /dev/stdin -&prompt.root; newfs /dev/da1e -&prompt.root; mkdir -p /1 -&prompt.root; vi /etc/fstab # add an entry for /dev/da1e -&prompt.root; mount /1 - - - - - - - RAID - - - Software RAID - - - Concatenated Disk Driver (CCD) Configuration - - ChristopherShumwayOriginal work by - - - JimBrownRevised by - - - - - -RAIDsoftware - - RAIDCCD - - - When choosing a mass storage solution the most important - factors to consider are speed, reliability, and cost. It is - rare to have all three in balance; normally a fast, reliable mass - storage device is expensive, and to cut back on cost either speed - or reliability must be sacrificed. - - In designing the system described below, cost was chosen - as the most important factor, followed by speed, then reliability. - Data transfer speed for this system is ultimately - constrained by the network. And while reliability is very important, - the CCD drive described below serves online data that is already - fully backed up on CD-R's and can easily be replaced. - - Defining your own requirements is the first step - in choosing a mass storage solution. If your requirements prefer - speed or reliability over cost, your solution will differ from - the system described in this section. - - - - Installing the Hardware - - In addition to the IDE system disk, three Western - Digital 30GB, 5400 RPM IDE disks form the core - of the CCD disk described below providing approximately - 90GB of online storage. Ideally, - each IDE disk would have its own IDE controller - and cable, but to minimize cost, additional - IDE controllers were not used. Instead the disks were - configured with jumpers so that each IDE controller has - one master, and one slave. - - Upon reboot, the system BIOS was configured to - automatically detect the disks attached. More importantly, - FreeBSD detected them on reboot: - - ad0: 19574MB <WDC WD205BA> [39770/16/63] at ata0-master UDMA33 -ad1: 29333MB <WDC WD307AA> [59598/16/63] at ata0-slave UDMA33 -ad2: 29333MB <WDC WD307AA> [59598/16/63] at ata1-master UDMA33 -ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33 - - If FreeBSD does not detect all the disks, ensure - that you have jumpered them correctly. Most IDE drives - also have a Cable Select jumper. This is - not the jumper for the master/slave - relationship. Consult the drive documentation for help in - identifying the correct jumper. - - Next, consider how to attach them as part of the file - system. You should research both &man.vinum.8; () and &man.ccd.4;. In this - particular configuration, &man.ccd.4; was chosen. - - - - Setting Up the CCD - - The &man.ccd.4; driver allows you to take - several identical disks and concatenate them into one - logical file system. In order to use - &man.ccd.4;, you need a kernel with - &man.ccd.4; support built in. - Add this line to your kernel configuration file, rebuild, and - reinstall the kernel: - - device ccd - - The &man.ccd.4; support can also be - loaded as a kernel loadable module. - - To set up &man.ccd.4;, you must first use - &man.bsdlabel.8; to label the disks: - - bsdlabel -r -w ad1 auto -bsdlabel -r -w ad2 auto -bsdlabel -r -w ad3 auto - - This creates a bsdlabel for ad1c, ad2c and ad3c that - spans the entire disk. - - The next step is to change the disk label type. You - can use &man.bsdlabel.8; to edit the - disks: - - bsdlabel -e ad1 -bsdlabel -e ad2 -bsdlabel -e ad3 - - This opens up the current disk label on each disk with - the editor specified by the EDITOR - environment variable, typically &man.vi.1;. - - An unmodified disk label will look something like - this: - - 8 partitions: -# size offset fstype [fsize bsize bps/cpg] - c: 60074784 0 unused 0 0 0 # (Cyl. 0 - 59597) - - Add a new e partition for &man.ccd.4; to use. This - can usually be copied from the c partition, - but the must - be 4.2BSD. The disk label should - now look something like this: - - 8 partitions: -# size offset fstype [fsize bsize bps/cpg] - c: 60074784 0 unused 0 0 0 # (Cyl. 0 - 59597) - e: 60074784 0 4.2BSD 0 0 0 # (Cyl. 0 - 59597) - - - - - Building the File System - - Now that you have all the disks labeled, you must - build the &man.ccd.4;. To do that, - use &man.ccdconfig.8;, with options similar to the following: - - ccdconfig ccd0 32 0 /dev/ad1e /dev/ad2e /dev/ad3e - - The use and meaning of each option is shown below: - - - - The first argument is the device to configure, in this case, - /dev/ccd0c. The /dev/ - portion is optional. - - - - - The interleave for the file system. The interleave - defines the size of a stripe in disk blocks, each normally 512 bytes. - So, an interleave of 32 would be 16,384 bytes. - - - - Flags for &man.ccdconfig.8;. If you want to enable drive - mirroring, you can specify a flag here. This - configuration does not provide mirroring for - &man.ccd.4;, so it is set at 0 (zero). - - - - The final arguments to &man.ccdconfig.8; - are the devices to place into the array. Use the complete pathname - for each device. - - - - - After running &man.ccdconfig.8; the &man.ccd.4; - is configured. A file system can be installed. Refer to &man.newfs.8; - for options, or simply run: - - newfs /dev/ccd0c - - - - - - Making it All Automatic - - Generally, you will want to mount the - &man.ccd.4; upon each reboot. To do this, you must - configure it first. Write out your current configuration to - /etc/ccd.conf using the following command: - - ccdconfig -g > /etc/ccd.conf - - During reboot, the script /etc/rc - runs ccdconfig -C if /etc/ccd.conf - exists. This automatically configures the - &man.ccd.4; so it can be mounted. - - If you are booting into single user mode, before you can - &man.mount.8; the &man.ccd.4;, you - need to issue the following command to configure the - array: - - ccdconfig -C - - - To automatically mount the &man.ccd.4;, - place an entry for the &man.ccd.4; in - /etc/fstab so it will be mounted at - boot time: - - /dev/ccd0c /media ufs rw 2 2 - - - - - The Vinum Volume Manager - -RAIDsoftware - - RAID - Vinum - - - The Vinum Volume Manager is a block device driver which - implements virtual disk drives. It isolates disk hardware - from the block device interface and maps data in ways which - result in an increase in flexibility, performance and - reliability compared to the traditional slice view of disk - storage. &man.vinum.8; implements the RAID-0, RAID-1 and - RAID-5 models, both individually and in combination. - - See for more - information about &man.vinum.8;. - - - - - Hardware RAID - - - RAID - hardware - - - FreeBSD also supports a variety of hardware RAID - controllers. These devices control a RAID subsystem - without the need for FreeBSD specific software to manage the - array. - - Using an on-card BIOS, the card controls most of the disk operations - itself. The following is a brief setup description using a Promise IDE RAID - controller. When this card is installed and the system is started up, it - displays a prompt requesting information. Follow the instructions - to enter the card's setup screen. From here, you have the ability to - combine all the attached drives. After doing so, the disk(s) will look like - a single drive to FreeBSD. Other RAID levels can be set up - accordingly. - - - - - Rebuilding ATA RAID1 Arrays - - FreeBSD allows you to hot-replace a failed disk in an array. This requires - that you catch it before you reboot. - - You will probably see something like the following in /var/log/messages or in the &man.dmesg.8; - output: + For this example, a single large partition will be created + on the new disk. The + GPT partitioning scheme will be + used in preference to the older and less versatile + MBR scheme. - ad6 on monster1 suffered a hard error. -ad6: READ command timeout tag=0 serv=0 - resetting -ad6: trying fallback to PIO mode -ata3: resetting devices .. done -ad6: hard error reading fsbn 1116119 of 0-7 (ad6 bn 1116119; cn 1107 tn 4 sn 11)\\ -status=59 error=40 -ar0: WARNING - mirror lost - - Using &man.atacontrol.8;, check for further information: - - &prompt.root; atacontrol list -ATA channel 0: - Master: no device present - Slave: acd0 <HL-DT-ST CD-ROM GCR-8520B/1.00> ATA/ATAPI rev 0 - -ATA channel 1: - Master: no device present - Slave: no device present - -ATA channel 2: - Master: ad4 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI rev 5 - Slave: no device present - -ATA channel 3: - Master: ad6 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI rev 5 - Slave: no device present - -&prompt.root; atacontrol status ar0 -ar0: ATA RAID1 subdisks: ad4 ad6 status: DEGRADED - - - - You will first need to detach the ata channel with the failed - disk so you can safely remove it: - - &prompt.root; atacontrol detach ata3 - + + If the disk to be added is not blank, old partition + information can be removed with + gpart delete. See &man.gpart.8; for + details. + - - Replace the disk. - + The partition scheme is created, and then a single partition + is added: - - Reattach the ata channel: + &prompt.root; gpart create -s GPT ada1 +&prompt.root; gpart add -t freebsd-ufs ada1 - &prompt.root; atacontrol attach ata3 -Master: ad6 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI rev 5 -Slave: no device present - + Depending on use, several smaller partitions may be desired. + See &man.gpart.8; for options to create partitions smaller than + a whole disk. - - Add the new disk to the array as a spare: + A file system is created on the new blank disk: - &prompt.root; atacontrol addspare ar0 ad6 - + &prompt.root; newfs -U /dev/ada1p1 - - Rebuild the array: + An empty directory is created as a + mountpoint, a location for mounting the new + disk in the original disk's file system: - &prompt.root; atacontrol rebuild ar0 - + &prompt.root; mkdir /newdisk - - It is possible to check on the progress by issuing the - following command: + Finally, an entry is added to + /etc/fstab so the new disk will be mounted + automatically at startup: - &prompt.root; dmesg | tail -10 -[output removed] -ad6: removed from configuration -ad6: deleted from ar0 disk1 -ad6: inserted into ar0 disk1 as spare + /dev/ada1p1 /newdisk ufs rw 2 2 -&prompt.root; atacontrol status ar0 -ar0: ATA RAID1 subdisks: ad4 ad6 status: REBUILDING 0% completed - + The new disk can be mounted manually, without restarting the + system: - - Wait until this operation completes. - - - + &prompt.root; mount /newdisk - USB Storage Devices + + USB Storage Devices + - MarcFonvieilleContributed by + + + Marc + Fonvieille + + Contributed by + - - USB disks - A lot of external storage solutions, nowadays, use the - Universal Serial Bus (USB): hard drives, USB thumbdrives, CD-R - burners, etc. &os; provides support for these devices. + Many external storage solutions, such as hard drives, USB + thumbdrives, and CD/DVD burners, use the Universal Serial Bus + (USB). &os; provides support for these devices. Configuration - The USB mass storage devices driver, &man.umass.4;, - provides the support for USB storage devices. If you use the - GENERIC kernel, you do not have to change - anything in your configuration. If you use a custom kernel, - be sure that the following lines are present in your kernel - configuration file: + The USB mass storage devices driver, &man.umass.4;, is + built into the GENERIC kernel and + provides support for USB storage devices. For a custom + kernel, be sure that the following lines are present in the + kernel configuration file: device scbus device da device pass device uhci device ohci +device ehci device usb device umass *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***